On Thu, Jan 28, 2010 at 1:37 PM, Greg Troxel <[email protected]> wrote:
> > I've been thinking about how to handle maintenance of imports; so far > osm has tended to import once and then just edit. My suggestion is to > put whatever database primary key you use on the node, and to be able to > look at the node and tell which import was done, which really means the > internal date or whatever identifier of your database extract. > > But what happens if someone replaces your imported node with a new one or the node is deleted or someone just changes your primary key for fun ? I think it would be better to keep the node_id or way_id (building) in your own database and check regularly if your element is still at the right location (with some tolerance) with the right tags (with some tolerance) . Then if the POI has been removed, check if the same one has not been recreated around. If yes, just refresh the node_id in your db. If not, recreate the POI or revert the deletion. The link between your db and OSM is the lat/lon, not an id which is not guaranteed in time. Pieren
_______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
