Attn: [email protected] Hi there,
As you might already know, I have the chart edited to include the canvec map features as they line up with all of the OSM tags, and marked with notes accordingly, as to what features to include/not include. http://spreadsheets.google.com/pub?key=rP0soJiyFhapKZbRLYZ74zA&output=html A PDF is also available in real-time.(6 meg file). http://spreadsheets.google.com/pub?key=rP0soJiyFhapKZbRLYZ74zA&output=pdf The features of TO_1580009_012_Named_feature contain a set of concise codes, however to my surprise each code should really be it's own code, as with the standards of the rest of the data. Since there are about [-1,5,7,10,20,30,40,45,50,60,80,90,100,110,115,120,130,140,150,160,170,180,190,200,210,220, 230,240,250,260,270,280,290,300,310,320,330,340,350,370,380,390,400,410,420,430,440,450,460] Codes listed in the CanVec_feature_catalogue_v1_0_2_en. I would think that each should have its own number. .. ie. 280 MTN Mountain should really be code “1582800” which follows suite to the canvec standards. However, since it isn't done this way, my best solution is to have it listed in the database as “canvec:CODE=1580010:280” Since I dont want to add an extra line. This way, I wont have the reduncency in the database. Please let me know if this is going to be fixed for the next version, or if not then i'll use my own idea, and then add in a few lines on the GoogleDocs Chart to show these extra tags. Thanks, Sam Vekemans Across Canada Trails Twitter: @Acrosscanada Facebook: http://www.facebook.com/sam.vekemans
_______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
