[Imports] [talk-au] Public Barbeques in the ACT

[Mike N]

On 10/10/2018 3:37 PM, Kevin Kenny wrote:
> In the couple of imports that I curate, I leave external ID's in OSM, to 
> give me a quick search for the object that I previously imported. (I can 
> then check that the user that last modified the object was the import.)  
> If the object has been changed in the external database, and is 
> unmodified since the last import, I can skip a manual conflation step, 
> and simply apply any changes and present the modified object for review.
> 
> The ID's would be useless in a 'one time only' import, but I attempt to 
> keep the import up to date as new versions of the external data appear.

    As the OSM community grows in the region containing a curated 
dataset, use cases must be managed:
    OSM user adds a new object they observe.
    OSM user adds a duplicate object without first checking for an 
existing object.
    OSM user removes an object they observe is no longer there.

   It all requires complete conflation, just as if there had been no 
external IDs in the database.