Xvtn
(Xvtn)
29
Perhaps this has already been suggested. But it sounds like there is a need for an application of some sort that would do the following:
- Accept tabular data for a given feature (eg walmart stores) and translate that into OSM tags
- Work around the well-known “there are no static ids for POIs in OSM” problem, by reading and writing ref tags, by geocoding addresses and searching nearby, by using other approaches, or a combination of these.
- Provide an easy way for data providers to manually review edge cases and follow established “automated edit” guidelines. Without wasting the provider’s time.
- Reject data that is not up to OSM’s quality standard.
These requirements sound to me like they would satisfy both btilly’s gripes and OSM’s import requirements.
I know this is a tall order. I don’t have time right now to spearhead this, so I’m just throwing out ideas for a possible technical solution.