Hi, On 10/28/18 18:46, Pieter Vander Vennet wrote: > By having the integrationprocess in place, we can make sure that the > data is properly integrated, properly attributed and backreferenced for > future updates.
I am always skeptical of imports trying to uphold links to an external database, and would recommend *not* keeping any IDs from the source object in OSM. Keeping a link to the source signals to the mapper "don't touch this, it's official data" or "your edits can be overwritten by a future import". More often than not, importers keep an external ID because they think "it might be useful later". If you want to keep an ID then you ought to determine *now* if and how you want to use that, and give guidance to mappers: If you split a building that has such an ID what should you do - delete the ID from both, keep on both, or...? If you delete a building that has such an ID, how will you ensure it isn't brought in again through a later "update import"? Etc. I think taht because any later attempt to update OSM data from the government data source will have to analyse existing OSM data *anyway* and will not be able to rely on the external IDs, it's not worth importing them in the first place. Bye Frederik -- Frederik Ramm ## eMail [email protected] ## N49°00'09" E008°23'33" _______________________________________________ Imports mailing list [email protected] https://lists.openstreetmap.org/listinfo/imports
