When editing #OpenStreetMap on the go, @everydoor is my hands-down favorite, but I'd hesitate recommending it for more new mappers.
When editing #OpenStreetMap on the go, @everydoor is my hands-down favorite, but I'd hesitate recommending it for more new mappers.
I've been playing with #OsmGo just now, and really like how easy it is, maybe even for new contributors.
Plus, it's a progressive web app that runs in a browser, or installable in your device: https://osmgo.com , so this also seems to be a great candidate tool to introduce as a friendly editor for @openstreetmap mapping parties for new users.
@MapAmore
I use @openstreetmap a lot, via #OSMAnd+, and I'd love to give back to the map commons. The biggest problems I see are not with the basic data (streets etc), since the NZ govt's own map data is released under CC license, and updates to it are quickly imported into #OSM.
Rather what I see is outdated info about what can be found at a given address. Any advice of helping to update that kind of data? Is it part of OSM or other data commons used by OSMAnd+?
POIs in general are hard to maintain. Even Big G is struggling with that on their maps.
Theme-specific POIs are probably slightly better, when there are interested parties who are keen to maintain them, or keep them up-to-date.
If you don't like to map them directly yourself, when you're on site, then you're next bet is to use fresh (and compatible) ground imagery, to map them when you can.
@MapAmore
> If you don't like to map them directly yourself, when you're on site
I have ADHD. If I can't do it right away when I notice the problem, I'm unlikely to remember. So what I need is an Android app that makes it quick and easy to submit an update (with appropriate license) whenever I notice a discrepancy.
The only problem I have with OSMGo is that when adding a crossing the software doesn't merge it with a nearby way (as opposed to EveryDoor). Otherwise it's a great app.