[Talk-ca] Cleaning up after the GeoBase import

[Michael Barabanov]

Another way of incorporating the updates (without using UUIDs) would
be to re-run roadmatcher. Given that we'll like will want to do it
anyway (geobase will have new roads), maybe preserving UUIDs isn't a
big deal after all. Another reason we'd likely use another roadmatcher
run for things like addresses is because existing osm ways don't
replaced with geobase and so don't get UUIDs.

Michael.



On 6/10/09, Richard Degelder <rtdegelder at gmail.com> wrote:
> Simon,
>
> Combining the ways will defeat the possibilities of further use of the
> GeoBase data for the area.  Unfortunately the GeoBase NID is unique for the
> single segment only and combining multiple segments will make adding
> additional data based on those unique NIDs, such as address data, impossible
> as will further updates to the data in future GeoBase updates.
>
> The only practical method to deal with the data is, as Richard Weait
> suggested, to use relationships for the data that is common for the ways.
> This is unlike the American model for the TIGER import but it also allows us
> to modify and update the data much better based on future GeoBase updates
> and to later incorporate additional data that we did not use in the intitial
> GeoBase import.  Of course this does not prevent individual mappers from
> adding aditional details or even new ways onto the map at the same time or
> for correcting the map where there are errors or changes prior to a GeoBase
> update being rolled out over an area.
>
> Rchard Degelder
>

-- 
Sent from my mobile device