I've had decent results using roadmatcher in a somewhat road-populated area (Port Stanley Ontario 040I11) The results were decent because I chopped up the existing osm roads at every intersection before running roadmatcher I then make a list of "Standalones" that should have been matched by overlaying the existing osm map with my new alone osm file in Mercaartor and manually selecting all the duplicate roads (there were about 35 in this region). That leaves me with a pretty good alone file. I have a script that finds all the intersection nodes and splits the ways at those points, but it's not in any condition to upload right now. John Peterson > Thanks,I hope Steve Singer would be able to help answer the question. > I'll just give my notes:
Cheers, Sam On Wed, Feb 4, 2009 at 1:01 PM, Moreau, Jean-Sébastien < Jean-Sebastien.Moreau at rncan-nrcan.gc.ca> wrote: > Hi all, > > > > I did some test with the roadmatcher and wanted to give you some feedback. > Although the tool has advanced features for the conflation of roads > networks, the automatic matching function doesn't behave as expected when > the two datasets have significant differences in terms of segmentation > rules. As some of you might have realised, the geobase network has a lot > more junction than the osm network. The roadmatcher tool seems to have > trouble to find the different pieces of geobase segment that correspond to > an OSM element. Fixing the resulting layer was a tedious task. > > It might be possible though to tweak on the different tolerance values in > order to improve the result. > > > > Have some of you got good result with this tool? If so, what values did you > use for the tolerances? > > > > Right now, I'm working on a simpler solution using fme. > > > > *Jean-Sebastien Moreau* _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
