Martin Raifer

An additional complication can arise when people would forget to upload their changes after editing a few features, potentially resulting in a loss of data. This effect can perhaps be...

> […] See for example this changeset https://overpass-api.de/achavi/?changeset=76262966. > I cannot know whether the healthsites user in the mentioned changeset intended to remove the phone number, but this seems like...

the source of the coordinates of ~~some~~ most (all?) of the entries might be problematic: * _Google Earth_: is likely using google satellite imagery, which doesn't allow data to be...

I believe the mapping the name of features in OSM with a `name:` without also adding a matching `name` tag can be considered a mapping error in the existing data....

There are quite a few more of these alternative name tags, not just `alt_name` and `official_name`. See https://wiki.openstreetmap.org/wiki/Name

Maybe it would help if we limit this to administrative boundaries, but that's still much too much [data](http://taginfo.openstreetmap.org/keys/admin_level#values) to be simply preloaded like the hot projects list…

[osmnames](https://osmnames.org/) could be an option, although I think they don't directly provide the geometries like [nominatim does](https://wiki.openstreetmap.org/wiki/Nominatim#Parameters).

thanks for the hint, but as far as I can see, it also doesn't return the full geometry of the search results, does it?

after digging around a bit, I found https://whosonfirst.org/browse/ which seems to be still operational and offer the kind of stuff we would need, for example https://data.whosonfirst.org/101/751/119/101751119.geojson

> run the error tool in JOSM this might be a bit hard to implement in practice since I wouldn't know a way to run JOSM's internal validator on global...