1. Nov 2018 16:30 by [email protected] <mailto:[email protected]>:
> In both use cases, the major purpose of the foreign key is to avoid manual > review in the case where OSM will not be updated. If an object (retrieved by > key) is unchanged since the last import, in both OSM and the external > database, then there is no work to be done. Is there some reason why storing "object with id in database XYZ was uploaded as OSM object with id 717373737" should be stored in OSM? This data is useful only to whoever made the import and keeps updating data. Others, even when working with the same data must anyway verify whatever OSM objects really match objects in the external database. I have no experience with big external databases, I am keeping up to date dataset much smaller (around 1000 bicycle parkings in Kraków, Poland - https://overpass-turbo.eu/s/Dl7 <https://overpass-turbo.eu/s/Dl7> ) so maybe I am missing something. > This process is impossible without some tag that follows the imported > object, because without one there's no handle by which it can be grasped. What is wrong with remembering object ID and latest update date? > it won't trigger any cascade of bad data, cause changes made by human mappers > to be overwritten, or any of the disasters that some posters appear to > envision. > Thanks for doing it in a proper way!
_______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
