[Imports] RoadMatcher
Andre Schoonbee
andresch at iway.na
Fri Sep 11 08:53:11 BST 2009
Dear List
I also find this information very usefull. We are faced with the same
problem with regards to the road network in Namibia. Al lot of road data doe
exist in OSM, of which some is 100% but some is not. I have received the
latest must up to date dataset, but now trying to apply the full dataset
will not be practical. I will also try-out this solution and would like to
continue discussion this possible solution and specifically steps of
processes to follow and also possible pitfalls.
Regards
Andre Schoonbee
-----Original Message-----
From: imports-bounces at openstreetmap.org
[mailto:imports-bounces at openstreetmap.org] On Behalf Of Richard Weait
Sent: 11 September 2009 04:19 AM
To: imports at openstreetmap.org
Subject: [Imports] RoadMatcher
Dear Import team,
During the call today, SteveC suggested that I outline what the
Canadian community has been doing with RoadMatcher.[1]
The RoadMatcher code[2] is a plug-in for OpenJUMP[3]. The OpenJUMP
code[4] is a Java GIS desktop program licensed under Gnu GPL.
The RoadMatcher adds conflation options for road networks. It finds
similar road sections in multiple data sets and allows conflation
operations on these data sets. One of the Canadian contributors,
Steve Singer[5], has experimented with and patched RoadMatcher to work
with the Canadian road network data sets.
Background
The Canadian road network data is non-uniform. High quality topology
is available in the National Road Network[6], a few provinces also
include street names and block face addressing. Another older road
network file[7] data set from Statistics Canada has street name data,
but the topology is poor. An un-named Canadian government source has
advised me to never use the topology data in the Statcan file.
The Canadian community also agreed that it is more difficult, but
preferable, to add road data without wiping out existing community
contributions. RoadMatcher made that possible.
Benefits
RoadMatcher and OpenJUMP takes road names from the StatCan data and
adds them to the NRN data, when they match closely enough.
RoadMatcher also compares NRN geometry to existing OSM highway
geometry and creates output files for:
All NRN roads, with StatCan names added.
NRN roads plus StatCan names that match roads found in OSM as roads
not to upload.
NRN roads plus StatCan names not found in OSM as roads to upload to OSM.
Drawbacks
The RoadMatcher matches between NRN an StatCan data are imperfect.
The RoadMatcher matches between NRN and OSM are imperfect.
When uploaded to OSM, the NRN road network does not connect
topologically with the existing OSM network. Nodes must be created
where they join.
Best regards,
Richard.
[1]
http://wiki.openstreetmap.org/wiki/Geobase_NRN_-_OSM_Map_Feature#RoadMatcher
[2] http://www.jump-project.org/project.php?PID=RM&SID=OVER
[3] http://wiki.openstreetmap.org/wiki/OpenJUMP
[4]
https://sourceforge.net/project/showfiles.php?group_id=118054&package_id=320
958
[5] http://wiki.openstreetmap.org/wiki/User:Stevens
[6] http://www.geobase.ca/geobase/en/data/nrn/description.html
[7] http://geodepot.statcan.ca/Diss/2006Dissemination/Data/FRR_RNF_e.cfm
_______________________________________________
Imports mailing list
Imports at openstreetmap.org
http://lists.openstreetmap.org/listinfo/imports
More information about the Imports
mailing list