Hi
> many imports have gone to the trouble of> preserving ids with the idea that
> they'll help with conflation of updated data
> sets years down the line. there are no known examples of this actually
> happening
Actually, there's at least one.
http://www.openstreetmap.org/user/mikelmaron/diary/19912
-Mikel
* Mikel Maron * +14152835207 @mikel s:mikelmaron
On Wednesday, October 22, 2014 10:11 AM, Richard Welty <[email protected]>
wrote:
>
>
>On 10/22/14 10:03 AM, Eric Ladner wrote:
>
>
>
>I agree with Jason's comments on the ID, though. Post-import, it's pretty
>useless. I think the idea is that it would be useful several years down the
>road when a new data dump is taking from an upstream source to match changed
>buildings, but there's no guarantee that the ID's from the external source
>would even be consistent (i.e. the building on the corner of Dauphine and
>Contie with ID=1234 may not have the same ID 2 years from now after the
>upstream system goes through upgrades, software changes, etc.)
+1. as serge is fond of pointing out, many imports have gone to the trouble of
>preserving ids with the idea that they'll help with conflation of
updated data
>sets years down the line. there are no known examples of this
actually happening.
>
>richard
>
>-- [email protected] Averill Park Networking - GIS & IT Consulting
>OpenStreetMap - PostgreSQL - Linux Java - Web Applications - Search
>
>_______________________________________________
>Imports mailing list
>[email protected]
>https://lists.openstreetmap.org/listinfo/imports
>
>
>_______________________________________________
Imports mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/imports
