I like the idea, but these tasks seem incomprehensible. I looked at some near me, and one is about traffic lights at an intersection that doesn't have traffic lights, and the others just say "Highway not on ground and no tunnel, bridge or covered tags" under "Instructions" but they're not highways or roads at all (though I guess they are on the ground).
I agree, I looked around my area and found a task on top of a parking lot that says: "These elements have rare (<20 uses) parking=* values." What does this mean? Does it mean that the parking log is marked to have a "<20" value when the value should be a number instead of a string? Obviously I'm not going to go inside the car park and count all the park slots, there could be hundreds!
MapRoulette: the micro-tasking tool for OpenStreetMap
11–20 of 30 posts
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#12(At some point they made some change that left my class of SU behind, but since the original purpose of 4sq died long ago there wouldn't be a point to donate my time to it now.)
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#13Earlier quoted context omitted.
I agree, I looked around my area and found a task on top of a parking lot that says: "These elements have rare (<20 uses) parking=* values." What does this mean? Does it mean that the parking log is marked to have a "<20" value when the value should be a number instead of a string? Obviously I'm not going to go inside the car park and count all the park slots, there could be hundreds!
I tried items with rare values for 'surface.' I found and fixed a footpath through a pasture (the docs seemed to imply that "dirt" is sufficient for a path through a pasture). But my next item was in China and the surface was "木" which apparently means Wood. But the rest of the fields of this pier were also in Chinese, and I was too shy to update it. I hope that localization is handled separately and that it would ha…
In this case, the spec allows for "commonly used" user defined values, which is unusual (how does a user defined value become commonly used enough in the first place?), measured per this site: https://taginfo.openstreetmap.org/keys/surface#values
You can find a few non English entries in there, but the vast majority and all of the most common ones are in English. "木“ has 2 entries, "wood" has >200k. I think it's pretty clear that even in cases when the specification is open, the intention is for values to be English whenever practical.
The alternative is so outrageous that they made it into an April fools joke: https://weeklyosm.eu/osm-tags-soon-in-german-and-french-and-...
Here's someone attempting to translate the tags/values (for display): https://github.com/osmlab/osm-planning/issues/20
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#14I see two clusters with "2", maybe that means that there are 4 tasks on the map segment which need fixing.
Clicking on any of the two clusters does nothing. The sidebar has just an odd "Global: [amenity=doctors] and [healtcare:speciality=*] missing [healthcare]", which, when I click it, reloads the page and shows me a world view with problematic doctors.
When I deselect "Cluster", then nothing is shown, instead of those 4 clustered tasks that apparently need fixing. I expected to see 4 individual tasks, instead of the two clustered ones.
At the same time a label tells me "23 tasks found", yet I see none. I assume those two pairs of clusters of two should represent 4 tasks, but I can't interact with them in any way.
I also can't easily navigate to a place of interest because there is no location searchbox.
I was expecting something like StreetComplete.
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#15What does this accomplish that StreetComplete does not?
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#16The problem with maproulette is the same thing that makes it fun: the gamification. Some people value imaginary internet points so highly, they edit OSM willy-nilly to make it conform to maproulette, disregarding ground truth, not checking if the tasks analysis is complete and mapping slightly wrong around the world. This is mad MUCH worse by the fact that the default setting in maproulette is that when you finish a…
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#17The problem with maproulette is the same thing that makes it fun: the gamification. Some people value imaginary internet points so highly, they edit OSM willy-nilly to make it conform to maproulette, disregarding ground truth, not checking if the tasks analysis is complete and mapping slightly wrong around the world. This is mad MUCH worse by the fact that the default setting in maproulette is that when you finish a…
I used to do a lot of OSM editing. In my experience, it really helps to have edited a lot in one area to better understand local context, make better sense of imagery etc etc.
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#18Earlier quoted context omitted.
I tried items with rare values for 'surface.' I found and fixed a footpath through a pasture (the docs seemed to imply that "dirt" is sufficient for a path through a pasture). But my next item was in China and the surface was "木" which apparently means Wood. But the rest of the fields of this pier were also in Chinese, and I was too shy to update it. I hope that localization is handled separately and that it would ha…
The tags are specified in the wiki: https://wiki.openstreetmap.org/wiki/Key:surface In this case, the spec allows for "commonly used" user defined values, which is unusual (how does a user defined value become commonly used enough in the first place?), measured per this site: https://taginfo.openstreetmap.org/keys/surface#values You can find a few non English entries in there, but the vast majority and all of the mos…
So that table there lists all common values covering 99% of the use cases, and finally links to TagInfo for all values in use. That 'all commonly used values' bit is slightly misleading, because TagInfo lists all uncommon values, but it true in the sense that any common value missing from that table will be listed in TagInfo (being derived from the actual database).
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#19Earlier quoted context omitted.
I agree, I looked around my area and found a task on top of a parking lot that says: "These elements have rare (<20 uses) parking=* values." What does this mean? Does it mean that the parking log is marked to have a "<20" value when the value should be a number instead of a string? Obviously I'm not going to go inside the car park and count all the park slots, there could be hundreds!
I tried items with rare values for 'surface.' I found and fixed a footpath through a pasture (the docs seemed to imply that "dirt" is sufficient for a path through a pasture). But my next item was in China and the surface was "木" which apparently means Wood. But the rest of the fields of this pier were also in Chinese, and I was too shy to update it. I hope that localization is handled separately and that it would ha…
So yes, surface=木 is wrong, but to replace it you would have to know if the path uses wood-chips (`woodchip`) or boards (`wood`).
Re: MapRoulette: the micro-tasking tool for OpenStreetMap
#20I think it could be a really good use of AI to let me, for example, snap a photo of the menu and then have it automatically generate the OSM tags. Then someone just has to review if it all is appropriate.
Just bring able to walk down the street, snap a bunch of menu or sign pics, then go home and drop pins and confirm tags from photos would be great.
Heck it could even scrape their website to verify the information too!
Does anyone know if there is a project like this? Or have any thoughts on if this is a reasonable approach? I think as long as there's a human in the loop checking things it should be fine by OSM.