Thanks, the canvec roads think & act like Q-tips. And unfortunatly, i cannot run AutoMatch, so it would be best for geobase2osm to be run 1st. Then use the canvec roads as an overlay. (to help users as a guide to know where to Stretch/move the intersecting nodes too.)
Does the geobase script account for the AdressRangeFirst/last/left/right data fields? If it doesnt, then that needs to be handled. Cheers, Sam On 4/1/09, Steve Singer <[email protected]> wrote: > On Wed, 1 Apr 2009, Sam Vekemans wrote: > >> >> And Steve, my plan is still to wait till you run the geobase2osm script >> (unfortunatly i dont know how too),,, before loading any of the canvec >> data >> on top. If you have a chance, please let me know if it would be fine to >> be >> importing the data for .. those areas of >> very very little to know OSM data.?? . >> >> And everyone,.. since the geobase2osm script would detect that canvecROADS >> were already imported, it would look at them the same way as user created >> OSM Roads.??? > > > I'm somewhat confused by the above two paragraphs, they seem to contradict > each other. Is it the case that: > > 1. Your not going to import the road layer from canvec. In this case it > doesn't matter if you import the canvec data before or after the geobase > roads are imported. Campgrounds, power lines, buildings etc... won't > conflict with roads (I won't exclude roads based on a power line running > next to it). > > 2. Your going to import the canvec roads, if so then any roads you import > before I run roadmatcher should just result in that road being excluded from > the geobase import (it will be treated just like any other OSM road). If I > do the geobase import first then you'll need to find a way to detect > conflicts. > > Which one is it? > >> >> Thought on that anyone? >> >> Cheers, >> Sam Vekemans >> Across Canada Trails >> > > _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
