Floris, thanks for feedback!<div><br></div><div>We have to fix & ;) then - we can't deal with autocorrection on phone, but we can reduce them by simplyfying tagging process (still thinking on HOW). Location fix - unfortunately we don't have any chances to automate it, guess adding a layer to MapDust can help with it - if any ideas here - would be cool to hear.</div>
<div><br></div><div>--</div><div>RO<br><br><div class="gmail_quote">2011/7/8 Floris Looijesteijn <span dir="ltr"><<a href="mailto:osm@floris.nu">osm@floris.nu</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I've added 5 POI's in Haarlem today. It's a fun way but it doesn't<br>
really work for me.<br>
Maybe it's my phone, a 2 year old HTC Magic...<br>
<br>
The 5 POI's I added were next to each other, about the same distance<br>
between them.<br>
The first POI was uploaded right on the location I added it.<br>
The next 2 were both on the same spot, about 50m wrong.<br>
The fourth was hundreds of meters off, in a different part of the city.<br>
The fifth wasn't recognized because I started my tweet with #osmit<br>
instead of ending with that.<br>
<br>
Some other remarks:<br>
- & turns into &<br>
- My phone's gps sucks :)<br>
- #damnyouautocorrection<br>
- Still a cool app but not for me<br>
<br>
Greetings,<br>
<font color="#888888">Floris Looijesteijn<br>
</font><div><div></div><div class="h5"><br>
On Wed, Jul 6, 2011 at 12:58 PM, Oleg <<a href="mailto:gelosi@gmail.com">gelosi@gmail.com</a>> wrote:<br>
> By the way, we'v reduced permissions for twitter - just like it should be!<br>
> Thanks for mentioning that!<br>
> --<br>
> RO<br>
><br>
> 2011/7/6 Oleg <<a href="mailto:gelosi@gmail.com">gelosi@gmail.com</a>><br>
>><br>
>> Cool thing around pictures, as most of twitter clients can upload them<br>
>> themselves and make a short links in the posts, so, we can try to use that<br>
>> links and put them into nodes as well!<br>
>> Also @mentioning - we're adding both ways now - so, you'll be able to use<br>
>> @osm_it - to hide your mappings from your followers, or #osmit - as it works<br>
>> now...<br>
>> Next, a MapDust - have to get in more with service, as it makes sense to<br>
>> use it with osmitter.<br>
>> For now, when you're adding a POI, you'll get a @reply from osmitter with<br>
>> link to the node on the OSM, like<br>
>> this: <a href="http://twitter.com/#!/osm_it/status/87777704488865792" target="_blank">http://twitter.com/#!/osm_it/status/87777704488865792</a> - so, you can<br>
>> check it on the go.<br>
>> btw, cool to have this kind of feedback!<br>
>> --<br>
>> RO<br>
>><br>
>> 2011/7/5 Martijn van Exel <<a href="mailto:m@rtijn.org">m@rtijn.org</a>><br>
>>><br>
>>> Hi Oleg,<br>
>>><br>
>>> Well you beat me to it :) This is in fact almost exactly what I had in<br>
>>> mind and what I discussed at WhereCampEU.<br>
>>> Apart from the comments Martin made, we also discussed using a mention<br>
>>> instead of a hashtag. This helps to keep the user's followers twitter<br>
>>> streams free of the osmitter tweets that do not make sense to most anyway.<br>
>>> The rationale here is that a tweet starting with a @mention will - I believe<br>
>>> - only show up in your follower's stream if they also follow that account.<br>
>>> Also, I've been thinking about feedback to the user. Because GPS is<br>
>>> generally inaccurate in dense urban areas this way of adding things to OSM<br>
>>> will result in quite a number of those things ending up on the next block or<br>
>>> on the wrong side of the street. It would be good if there were some way for<br>
>>> the user to easily review his submissions. This could be done in a number of<br>
>>> ways. Firstly there is the intermediate layer that Martin mentioned. I was<br>
>>> talking to Oliver (Skobbler) about using MapDust for that and that makes a<br>
>>> lot of sense to me. If you choose to go the route you chose and add directly<br>
>>> there should be either something like a queue of twitter submissions on the<br>
>>> osmitter web site that you could pull up to review your submissions, or<br>
>>> possibly a twitter reply with a link to a mobile site allowing you to do<br>
>>> that. As it is, this system will generate a lot of inaccurately located POIs<br>
>>> – or does your experience show otherwise?<br>
>>> A last thing that I've been thinking about implementing is a way to add<br>
>>> links to photos to the POI. Twitter clients on smartphones generally have<br>
>>> tight integration with photo sharing services - take a picture, twitter<br>
>>> client uploads and inserts link to image page on sharing service. That link<br>
>>> could be added as a tag (url:photo or something?) to the poi.<br>
>>><br>
>>> Best<br>
>>> Martijn<br>
>>><br>
>>> On Tue, Jul 5, 2011 at 8:06 PM, Oleg <<a href="mailto:gelosi@gmail.com">gelosi@gmail.com</a>> wrote:<br>
>>>><br>
>>>> Hi Martin,<br>
>>>> Yes, I've talk to Shaun McDonald - he told me about this discussion. The<br>
>>>> sad thing - I was planning to visit wherecamp this summer as well, but no<br>
>>>> luck there ;)<br>
>>>> Think, correcting posted data is a useful tool, we can do that - as we<br>
>>>> can keep all the data, we'v parsed.<br>
>>>> First we want to add is a human-readable tagging - so, you can add "fast<br>
>>>> food italian pizzeria Ololo #osmit", but, still thinking on formatting and<br>
>>>> parsing rules on this case. A good example is another place, named "French<br>
>>>> Fries", for instance...<br>
>>>> If there's any idea on parsing both of the cases correctly... and yes =<br>
>>>> we'll update that example!<br>
>>>> --<br>
>>>> RO<br>
>>>> 2011/7/5 M∡rtin Koppenhoefer <<a href="mailto:dieterdreist@gmail.com">dieterdreist@gmail.com</a>><br>
>>>>><br>
>>>>> While I think that this is generally not a bad idea, I'd still expect<br>
>>>>> that the data has not the average positional quality OSM usually has.<br>
>>>>> Martijn van Exel gave a talk at Wherecamp-EU in Berlin about the same<br>
>>>>> topic (twitter to osm) and in the following discussion the consensus<br>
>>>>> was towards a intermediate layer where those tweets would be stored,<br>
>>>>> so that you can do reasonable verification at home with the comfort of<br>
>>>>> a map and probably some nice aerial fotos in the background to<br>
>>>>> validate the "raw" data.<br>
>>>>><br>
>>>>> I also stumbled upon the first tagging examples on your page:<br>
>>>>> Italian pizzeria<br>
>>>>> amenity=cafe name=Pizza Ololo cuisine=italian #osmit<br>
>>>>><br>
>>>>> Is this really consensus to tag a pizzeria as cafe? There is also<br>
>>>>> restaurant and fast_food in the amenity value-set.<br>
>>>>><br>
>>>>> Cheers,<br>
>>>>> Martin<br>
>>>>><br>
>>>>> _______________________________________________<br>
>>>>> talk mailing list<br>
>>>>> <a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
>>>>> <a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
>>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> talk mailing list<br>
>>>> <a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
>>>> <a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
>>>><br>
>>><br>
>>><br>
>>><br>
>>> --<br>
>>> martijn van exel<br>
>>> <a href="http://schaaltreinen.nl" target="_blank">schaaltreinen.nl</a><br>
>><br>
><br>
><br>
> _______________________________________________<br>
> talk mailing list<br>
> <a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
> <a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
><br>
><br>
<br>
_______________________________________________<br>
talk mailing list<br>
<a href="mailto:talk@openstreetmap.org">talk@openstreetmap.org</a><br>
<a href="http://lists.openstreetmap.org/listinfo/talk" target="_blank">http://lists.openstreetmap.org/listinfo/talk</a><br>
</div></div></blockquote></div><br></div>