Thanks, i will create a couple sample areas (niagra falls & crowsnest) although the data is in "words" rather than "numbers" its still sortable.
I understand what your saying, and the logical conclusion is to only take what is needed and useful -no duplicates :-) i havent yet figured out how to deal with the areas that overlap the coast lines that have already been imported from the coastal data base. Fortunatly its only 3 or 4 people. So i can/will chat with them. (as it would inter with their work) Concensus is achieved when; 1- the wiki charts contain no question marks 2 -I (sam vekemans) as 1 mapper can draw any lines/points/areas i like, if it doesnt interfear with other edits/conventions, i dont need aproval to import. 3 -it's considered "wikiediquet" to 'vote' on the wiki page. Although a vote isnt need (because it doesnt interfear with local data, NRN was aproved with logical concencious) -if an error is found, please speak up :) > - How are we going to work/update/render duplicate feature? the method of updating is clear; the osm file & the shp file is compared directly looking at the "uuid" tags. (see geobase2osm using OpenJUMP AutoMatch) > Why duplicate features? NHN/geobase product has for (4) packages and > geometries may be duplicated between packages Hopefully we wont need to :) I will make a chart (modify what is already there) http://wiki.openstreetmap.org/wiki/Geobase_NHN_-_OSM_Map_Feature I'll add in the spots where it's duplicated in CanVec, and decide what dataset contains the 'best' information. Omitting features from the canvec2osm script is pritty easy :) > > > > For example, a lake is described in Hydrographic and Hydro Network packages > by at least two overlapped features . > > Bank (Hydro Network) - A feature delimiting all or part of a Waterbody Hope that helps, Sorry for the delay in reply. Cheers, Sam _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
