Technically, you could store OSM ID-s during initial import to your own database. Then when you will do update, check if the updated object in OSM database is not changed, i.e. it has still version=1. If community has changed it (version>1), skip this. OSM IDs are more or less persistent AFAIK. External keys are always bad idea, unless they are wellknown values like official public IDs.
Anyway, I agree that it would be much better to leave any OSM updates to the community. Do not import something community cannot handle. If someone needs up-to-date ENC (e.g. openseamap), they can and should go and do download it from the NOAA as often as needed, no need to replicate the data. Jaak On 16.01.2013, at 9:28, Malcolm Herring wrote: > Jerry, > > I agree with most of Serge's points. My view is that imports should be a > one-time process in order to populate an empty map, but from then on, leave > it to local mappers to re-survey & update. I would also advise against trying > to make automated updates, particularly if you are relying on your private > tags remaining intact. > > Regards, > Malcolm > > > _______________________________________________ > Imports mailing list > [email protected] > http://lists.openstreetmap.org/listinfo/imports _______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
