"lines are not connected" i think i know what you mean. :) FYI My note kind of melds it's way to the addr: discussion
& FYI on the next version of canvec2osm i omitted the contours & contour imperial, and the roads. so they simply dont get checked with running the script. I made a new script canvecEXTRA2osm.bat which covers for it. ... Also the boundry NTS polygon is omited too, as it's not intended to be imported. I'm now going over both scripts to see what Hydro features are duplicated, and figuring how to deal with them. Anyway, The shp-to-osm-v3.0.jar (canvec2osm) looks at the .shx, .shp, .prj & .dbf files and based on what each field says, thats what gets produced. rules.txt does the 'magic' When i select the path, it translates these segments but doesnt eliminate the intersecting nodes. geobase2osm.py has the ability to remove that duplicate node. I don't know python nor java so (for me) it's not possible for the canvec2osm script. If this feature can be made to a .jar file, then it can be added to the shp-to-osm lib folder, then i can use it ;-) The program is designed to be simple (so its easy to edit & work with) The benefit(keeping it basic) is that more people can run the script, and modify it to their liking. Ie. Making it add more/less tags that would be local specific. Ie an area of trails all are known to have the same name - the import script can be changed. The end result is that it renders the same. If OSMF is in need of a larger storage space, a call can be made out to the community. Right? ... i think it was 27gigs CanVec and 59.3 gigs for the NHN . ... thats alot of nodes. .. but if our plan is to build the worlds greatest map. .. then that's what it will take. ... Don't we plan on showing official property outlines and where ditches are? So having it as separate might be good thing. ... .but that still doesn't solve the quagmire :-( imo - the entry skill level bar should not be set so high that only a couple people (those who can write in python) can understand. Basic DOS commands are easy enough to understand. So it DOES still render. :-) even if trails cant be navigated. (fix the routing software?) However, to contradict my self :) -before i learned: basic HTML; how to make an .img map file; how to edit OSM; how to make a .BAT file, how to convert .shp files... I thought it must be "sorcery - magic - wizardry & only things that free masons are aloud to conder up... ... So yes, i learn .py then it would be as easy as 'pie' to edit it. BUT it is generally understood that with clear step-by-step instructions on how to edit it. Most people should be able to figure it out. And BTW, the LX_2420009_1trail.osm file is rather funny, that's why i taged it as "highway=path" as most of the time is not accurate. Trails can be changed WAY faster than roads... and doesn't need to get all that permission to change. .. A trail going through a park, and go anyway that the park maintainers want. .. and besides, if the people don't like it.. they walk/bike and forge their own path. So this feature might as well just be traced, as they ALL need to be fixed up with more defining tags anyway. So in conclusion. ... if someone is able to help me out and make the canvec2osm script handle the removal of the duplicate nodes that gets created for all ways that gets created. That would be really helpful. (adding a .jar file) Or perhaps make canvec2osm a python script, and teaching me how to run the script, so anyone can run it & modify it easily. That would help. Re: Addr: interpolation OK, so the .dbf source shape file lists on 1 single, not connected way the 1st/last left/right house number. ... that just-so-happens-to-be-adjacent-at-the-ends. What if these fields could be shown at the node ends rather than on the way it's self? ... what if the 'left-side number' and the right-side number can be shown from the same node, just written on the other side of the dot. ie. .righthousenumber lefthousenumber. So the way would not actualy be visable.... Could this WAY be part of the big set of connected ways, that we list as 'addr:street' and 'name'.??? What if more properties the the 'highway=', tags get made. .. like have it 'act' like a route relation. So then each section of the 'highway=*' can have it's own 'addr:street' tag, and 'addr:housenumber' What if the .python script could place the ' .firsthousenumberRight' and 'firsthousnumberLeft.' at eithor side of the 1st node... and '.lasthousenumberRight' and 'lasthousenumberLeft.' on eithor side of the last node. having it off set like; .rightUP UPleft. <--------------------------------> pointing inwards at an angle. .rightDown DOWNleft. / \ < ------------- > \ / Hope that makes sense. .. brainstorming. :) Cheers, Sam Vekemans Across Canada Trails On 4/6/09, Michel Gilbert <[email protected]> wrote: > Hi Sam, > > Your canvec2osm app does not fix the problem I mentionned last week > regarding the node duplication at intersections. For example, in your > Niagara data sample the lines in LX_2420009_1trail.osm are not connected. > Same thing with GeoBaseNHN2osm, the NHN Bank features are not connected. > > Do you plan to modify your application ? In my view, it is not acceptable > in > the OSM model. > > cheers, > > Michel > > 2009/4/6 Sam Vekemans <[email protected]> > >> Hi all, >> canvec2osm v0.14 is now available! >> >> http://sites.google.com/a/acrosscanadatrails.com/www/Home/canvec2osm0_15.zip >> >> >> Highlights: >> >> *the 'extra' folder which contains contours and road segments has been >> updated. >> >> *I havent figured how to fix the "-" value tags, but still working on >> that. >> >> * i think its better to have all the fields available shown, as the >> data can be used. >> >> *for the "first/last & left/right" address number, my guess is >> "addr:housenumber:first:left" as that would make sence. I'll post it >> on the wiki, hopefully i'll get feedback >> >> *one option is to omit the tags that have been used with the >> geobase2osm script, and just show the addr:housenumber tags. Having it >> directly ontop of the road, might be good. Since these ways only >> extend between intersections; an ideal situation for this way. >> Perhaps listing it as 'name:first:left' would be good, so then it >> would get rendered. >> >> What is the tag to have the text shown on the oposite side of where it >> normally goes? >> >> Look forward to hearing the feedback. >> >> Oh ya, i have the sample are of Niagara Falls >> >> http://sites.google.com/a/acrosscanadatrails.com/www/Home/extracanvec_030m03_shpniagarafalls.zip >> >> >> http://sites.google.com/a/acrosscanadatrails.com/www/Home/osmcanvec_030m03_shpniagarafalls.zip >> >> Then also the GeoBaseNHN2osm latest >> >> http://sites.google.com/a/acrosscanadatrails.com/www/Home/geobaseNHN2osm0_04.zip >> >> http://sites.google.com/a/acrosscanadatrails.com/www/Home/NHNnhn_rhn_02ha000_shp_enniagarafalls.zip >> >> Where it all shows up very good. I think the best way is to view it >> all in JOSM and then check the tags to see if they make sence :-) >> >> Cheers, >> Sam Vekemans >> Across Canada Trails >> >> _______________________________________________ >> Talk-ca mailing list >> [email protected] >> http://lists.openstreetmap.org/listinfo/talk-ca >> > > > > -- > Michel Gilbert > _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
