We are a social advocacy project that organises geo/map-py events; designs & implements training workshops, generates #tech4good awareness, actively pledges open data sets, as we vivify diverse volunteers to vitalize map-py local communities across the Philippines.
#OpenStreetMap is @OSM!
I agree. It’s typical in OSM to use a generic “yes” when a mapper isn’t sure about the “right” value just yet, and get back to it later, or maybe the next mapper can figure out a better value.
That’s a specific case when I find the image=*, or mapillary=* tags and the like, very helpful. Usually, these are used to tell other mappers what the previous mapper saw from the photo.
In JOSM these are turned into links you can view, but not sure how it works in iD.
Well, unfortunately, what we see on the ground (and try to map in #OpenStreetMap ) is not necessarily always what we (or the locals) wanted, or hope to ever see.
Hopefully, it’s a work in progress, and they get around to fixing more essential things. 🤞
I agree that it could be used for initial mapping, and interpolation makes it “work” in some fashion – at the very least, one gets close enough to the area you want to.
That’s slightly better than having no mapped addresses, or mapping individual address POIs, without interpolation.
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.
@Doudouosm
The https://digitalpublicgoods.net/registry/ showcase software, apps, projects, content, systems and standards that are just as awesome as @OSM, to help attain #SDG|s.
@openstreetmap@a.gup.pe is in good company. 🎉
@openstreetmap@lemmy.ml