[Talk-ca] GeoBase import woes...
acrosscanadatrails at gmail.com
Mon Jan 26 23:02:33 GMT 2009
just looking at your map, it looks like the west part of Tower Road is
listed as 'unclassified'
Just wondering, was it the same steps as i described before??. ... you just
added in the step to break up the OSM road WAYS? ... so it was copy from
geobase.osm file, and paste to data.osm layer, then move to the right spot?
When grabbing the big OSM file, (make a copy of it) and then just extract
the 'highway=unclassified, hightway=secondary, highway=tertiary,
highway=residnential. .. tags (including the rest of the NRN representative
tags). ... then splitting the OSM ways to the same length of GeoBase ways.
and MERGING it, so then both sets are shown. ... you think this is possable?
... (instead or in addition to the RoadMatcher tool??) so then the GeoBase
NID would be added on to the OSM Node/way??
Craig mentioned the word 'conflation'
as thats a better word than MERGE
On Mon, Jan 26, 2009 at 3:02 AM, Craig Leat <craig.leat at gmail.com> wrote:
> Sam wrote:
> > Correction:
> > for step 8, the correct word is MERGE (not purge).
> <snip> </snip>
> > -unfortunatly, the only program that can do this is ArchGIS (i think)
> > -is there any opensource equivelant that can do this?
> uDig has a light weight conflation tool:
> The Jump Project has the Java Conflation Suite (JCS):
Because it is possible to merge or (conflate) address book entries. ..
where the hotmail address ID number is listed, along with the palm
addressbook item ID number, so both are listed. Why can't we have the same
with OSM nodes and ways?
I'm looking up the folks who are working on osm2shp program, i think there
... perhaps it is out of my league of understanding. As i still am
struggling to learn this JUMP program. ;-)
Note: I hope that my explanation; the method to extract the OSM data, then
play with it outside osm. ... by 'conflating' or 'merging' both datasets.
Having a backup copy of the origional OSM file, and the original geobase.osm
file. so then these will get used afterwords for the fine-tuning.
So once the new osm file is ready with it's origional osm nodes and ways
that now have the geobase tags & nid's, the extracted osm data, can now be
removed from the osm database and replaced with the new.
Does this concept make sence?? (just the concept, the 'conflating' or
'merging' scripting needs to be explained further)
Across Canada Trails
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Talk-ca