[Talk-ca] Conflicts between GeoBase and OSM attributes

[James Ewen]

On Fri, Jan 2, 2009 at 5:23 PM, Richard Degelder <rtdegelder at gmail.com> wrote:

> So if a user adjusts the way slightly or changes some of the attributes
> for that way we are going to leave it alone as long as it has an NID.
>
> An update will only worry about the ways within OSM that do not have an
> NID and those that GeoBase says have changed in some way as well as new
> streets within the GeoBase update.  These will have to go through a
> system very similar to the initial import and, if matched to a new road
> within GeoBase, will receive an NID as a result.
>
> If we want to add new data, such as street names and/or addresses, we
> are going to look at all of the NIDs and add new attributes as
> determined from the GeoBase data based on the NID that is already there.

Is this new data, such as street names going to be from a GeoBase
update? So, you would simply match the NID, ignore the existing
attributes, and add new attributes from GeoBase? I'm wondering what
happens if an OSM user makes a significant change to the way, enough
that it might become unique enough that it doesn't represent the
original way.

Hmm, I can't even figure out what I'm trying to say... I think the
concept you're describing is a decent way to go, but there are going
to be issues with that too... things to solve well down the road
though.

James
VE6SRV