re: Q-tips... Q-tips have nodes at each end. .. which is like how the some ways get imported.<div><br></div><div>So it's great you caught that, and will fix it so it can be better :-)</div><div><br></div><div>Obviously, the roads that are cut at the edges of the import square will need to be manually connected. ... this can be done the time of when manually importing the canvec data, - slow and steady wins the race :-) (so no need to write a script if it is too hard IMO)</div>
<div> </div><div>Dout... the geobase2osm script doesn't deal with address range... yet. ... and yes your right, both canvecRoads & geobaseNRN roads are the same....</div><div><br></div><div>So in the mean time, i'll be working on how to deal with using the <span class="Apple-style-span" style="border-collapse: collapse; ">Karlsruhe address scheme, and see what kind of thing i can come up with, using the data that we have available to us.</span><br>
</div><div><br></div><div><div>Well, thanks Richard for pointing out the fixes, i'll have those shown by the time im ready to release the wiki chart for all of it.<br></div><div><br></div><div>Here's the low down..</div>
<div><br></div></div><div>re: <span class="Apple-style-span" style="border-collapse: collapse; ">- junction connectivity is broken.</span></div><span class="Apple-style-span" style="border-collapse: collapse; "><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
For example, on the roads_segment layer, is a four-way junction but the<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
junction is broken. (49.4900, -113.9432) has four nodes, one for each<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
road segment from the N, E, W, and S. Merging the four nodes seems like<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
the right thing to do before we consider importing.</blockquote><div><br></div><div>Here's were the manual, mapper on the ground fixing, as well as when the 'canvec2osm' script roles through the area.</div><div>
Here's were we can indicate if there is a 4/way stop, or a stop/light, or if its a larger intersection with islands. </div><div>(so having 4 nodes is not necessarily a bad thing)</div><div>But anyway, Steve is dealing with that, so hopefully that will be handled.</div>
<div><br></div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
re:- a junction and a dead end?<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
On the dead_end layer is a node at the same point. That surprises me.<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
How can this be a junction and a dead end? The "dead end nodes" appear<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
at most road junctions.</blockquote><div><br></div><div>On the street i live on, right at the end before it gets to the main road.. it's actually blocked off to traffic. so there is a little gap along the way.</div>
<div>
<br></div><div>Along the some farm roads, the road does not connect to the main road... it did at one time, but now is only used for the farmers.. I have seen that when cycling along the crowsnest highway. ... where the highway paved though, but didnt want to connect to those side roads, due to the not wanted traffic. In some cases it's a ditch with a barbed wire fence.</div>
<div><br></div><div>However, i could just list them (dead-ends) all as a 'turning circle' would that be better?</div><div><br></div><div>re:</div><div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
- road names are broken.<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Both roads (all four segments) have defined values for canvec:L_STNAME,<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
canvec:R_STNAME but name="-" We'll get more from the import if we<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
populate name. Ideally we can populate name when L_STNAME = R_STNAME,<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
and use the two names when they differ.<br></blockquote></div><div> </div><div>That would be called 'SmartMatching" something that the OpenJUMP software could 'probably' do. </div><div>running an IF / THEN script would handle it.</div>
<div>This is something that can be done after the import happens, as a 'bot' (fortunately it would be user "geobase:Acrosscanadatrails" and not my regular user name for when that would happen)</div><div>
<br></div><div>I'll have to ponder that one for a bit :)</div><div><br></div><div>re:</div><div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
- "-" for null<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Several properties are set to "-" when they should be unset / null / not<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
used.</blockquote><div><br></div><div>"-" is actually the numerical value that is showing in the database file, but i'll have to ponder that one too :)</div><div><br></div><div>re:</div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
- contours are broken and not in OSM<br></blockquote><div><blockquote>The contour_imperial layer is 7MB and the largest layer in the Pincher<br></blockquote><blockquote>Creek data. You should get broad support for importing this data from<br>
</blockquote><blockquote>talk before you consider including contours in the import. Even if you<br></blockquote><blockquote>find that support, this contour layer is of very little use. There is<br></blockquote><blockquote>
no elevation data in the contour vectors.<br></blockquote></div><div><br></div><div>I dealt with that one already, but will further explain it on the wiki :)</div><div>In short, i have it included in the script, and in the 'extra' folder, as they will be helpful for creating custom Garmin Maps.</div>
<div>... i could just not include it in the script, and then run the script on my own, when im ready to make the garmin map. (Contour-only Garmin Map of Canada, to be used as an overlay when viewing ComputerTeddy's garmin IMG files) </div>
<div>... Would it be better to not include it in the script??</div><div><br></div><div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
- duplicate data in islands and water bodies<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Waterbody layer includes internal and external boundaries. Island layer<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
duplicates those internal boundaries.<br></blockquote></div><div><br></div><div>Having these duplicates should be fine. It clearly indicates what is land and what is water.</div><div>For those cases that islands are not listed, they might be just a 'sand Island', where a high-tide would make it invisable. .. for those areas that are listed as an 'unknown' sand island. .. sometimes is better just to leave it as it is, and when it can be physically varified, the truth will be known.</div>
<div>Omiting the 'inner' part of the waterbody would not be showing the data acuratly. BTW, sometimes, using the topo map, could answer that :-)</div><div><br></div><div>but yup, i'll have to ponder that one too :)</div>
<div><br></div><div><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
- named features missing name:en<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
Scotts Coulee, for example, has name and name:fr set, but not name:en<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
They should probably all be the same unless language specific names are<br></blockquote><blockquote class="gmail_quote" style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-color: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
provided.<br></blockquote></div><div><br></div><div>I dont want to have the label shown twice as it would be a duplicate node and hard to read. The people who imputed the data to make the canvec/geobase set, sometimes mixed up the french and english translations and didnt leave the field blank where they didnt know, but instead placed the english name in the french field.</div>
<div>... were all human ;) (and nothing todo with <span class="Apple-style-span" style="border-collapse: separate; font-family: Verdana; ">Outlaw (Scotts Coulee), a satiric, independent newspaper issued briefly before the federal election of 1896. <span class="Apple-style-span" style="border-collapse: collapse; font-family: arial; ">)</span></span></div>
<div><a href="http://www.biographi.ca/009004-119.01-e.php?&id_nbr=7490&&PHPSESSID=isvmljbjaggf8qtkd2rk0r4ej2">http://www.biographi.ca/009004-119.01-e.php?&id_nbr=7490&&PHPSESSID=isvmljbjaggf8qtkd2rk0r4ej2</a></div>
<div><br></div><div>(you gotta know some history about the areas were mapping... we are modern day explorers marking territory and charting the (literally) unknown after-all :-)</div><div> </div><div>So the solution is that these get manually fixed.... but more pondering.</div>
<div><br></div><div>(As a reminder) the canvec2osm 'train' runs much much slower than geobase2osm, it stops and is manually looked at all the way along. ... about the pace of a bicycle :)</div><div><br></div><div>
Cheers, </div><div>Sam Vekemans</div><div>Across Canada Tails ..erm Trails.</div></div></span>