<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18904"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=729334611-01042010>Bonjour Sam,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=729334611-01042010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=729334611-01042010>Thanks for the coments! </SPAN></FONT><FONT
color=#0000ff size=2 face=Arial><SPAN class=729334611-01042010>Now, how can I
answer briefly to that email? !-) I'll try in the
text</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=729334611-01042010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=729334611-01042010>Cheers,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=729334611-01042010>Daniel</SPAN></FONT></DIV><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> samvekemans@gmail.com
[mailto:samvekemans@gmail.com] <B>On Behalf Of </B>Sam Vekemans<BR><B>Sent:</B>
1 avril 2010 01:25<BR><B>To:</B> Brent Fraser<BR><B>Cc:</B> Bégin, Daniel;
Talk-CA OpenStreetMap<BR><B>Subject:</B> Re: [Talk-ca] Canvec.osm
samples<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi,<BR><BR>Its AWESOME to see that all of the features are available within
the SAME file. This was something that i attempted todo (last year),
but couldn't figure it out. This helps as it makes for easy copying
over. .. when all these features are in the same .osm file.
Thanks.<BR><BR>Regarding natural=reef . ... or sub_sea=reef <BR>what's better
natural=reef <A
href="http://wiki.openstreetmap.org/wiki/Proposed_features/reef">http://wiki.openstreetmap.org/wiki/Proposed_features/reef</A>
or sub_sea=reef? <A
href="http://wiki.openstreetmap.org/wiki/Tag:sub_sea%3Dreef">http://wiki.openstreetmap.org/wiki/Tag:sub_sea%3Dreef</A>
<BR>they are both in the proposed status. .. so im not sure which one is better.
<BR>Adding layer=-1 would indicate that it's below the surface.
Also. I dont think it needs to be a closed way. The way it's drawn
on Toporama is just like a natural=cliff (as a line with short angled lines on
one side)<FONT color=#0000ff><SPAN class=729334611-01042010><FONT size=2
face=Arial> Actually, what you see in Toporama is Canvec data - the
difference wtih .osm file is just a questino of rendering. I'll check
but may be natural=reef should be replaced by its associated water feature using
water=intermittent;
suface=rock tags .</FONT></SPAN><BR></FONT><BR>Regarding water
around the coastline. I would say that it's fine to add to OSM. ..
and just merge the nodes all the way along the coastline. .. .. or remove
it?<BR>I would think the exception would be if the waterbody had a name, then it
should be kept.<SPAN class=729334611-01042010><FONT color=#0000ff size=2
face=Arial> I thing that replacing coastline node with the ones
provided would be the best. By replacing I means move to /copy from /merge
with provided nodes because source=PGS coastline is usually less
accurate.</FONT></SPAN></DIV><FONT color=#0000ff size=2 face=Arial></FONT>
<DIV><BR>And overall, the natural=wood works for me. On Vancouver
Island, we used landuse=wood. But natural=wood probably is more generic,
as the actual ownership of that area is not known. All we know is that "in
this plot of land there are trees", beyond that, you need to check other
sources. Which sounds reasonable.<BR>.. and we cant say that it's
"forest" as that would imply some kind of protection. (which is unknown for this
feature).<SPAN class=729334611-01042010><FONT color=#0000ff size=2
face=Arial> </FONT></SPAN>the tag natural=land for the nodes (where i once
put 'place=island'), natural=land is better, as it might not always be rocks
that the map feature is showing. it's just "something in the water
sticking out permanently"<BR><BR>For waterway=steam. Yes, the
geobase waterway=stream is higher<SPAN class=729334611-01042010><FONT
color=#0000ff size=2 face=Arial> </FONT></SPAN>quality,<FONT
face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=729334611-01042010> </SPAN><SPAN class=729334611-01042010>[please,
send me an example where GeoBase is of higher quality than CanVec for the same
area] </SPAN><SPAN
class=729334611-01042010> </SPAN></FONT></FONT></FONT>so if people want to
load that instead, there is nothing stopping them. From the data
it's hard to know if it's a 'creek' 'stream' or 'river' so that needs to be
physically verified. I would think that the person loading the data
is local, so the would know best. .. but that might not be always the
case. I dont think it's too much troubble to connect these rivers
around the edges. .. and they may not even need to be connected. ... unless
these rivers are for navigating? (i also like to add the 'oneway=yes' by
looking at the contours. Makes for good navigating. IMO. But what
canvec has is just great :)<BR><BR>..... ah ha! there is something. Some
of the rivers dont have names, but the name is available from Toporama. .. this
can just be added in :-)<SPAN class=729334611-01042010><FONT color=#0000ff
size=2 face=Arial> When corresponding GeoBase rivers have the
name attached to it, CanVec data will.</FONT></SPAN><BR><BR>For
highway=turning_circle the fixme is 'Feature may not exist'. I
would say it's fine, because it would help people to know that they can still do
a 3-point-turn. (and that the road probably does actually end. <BR><BR>ok
the big ones<BR><BR>highway=tertiary is used for the 'orange' lines with
toporama<BR>highway=tertiary is also used for the 'reg' lines in toporama<BR>and
it looks like 'unpaved is orange' and 'red is paved'<SPAN
class=729334611-01042010><FONT color=#0000ff size=2 face=Arial>
</FONT></SPAN></DIV>
<DIV><SPAN class=729334611-01042010><FONT color=#0000ff size=2
face=Arial>Actually it is the contrary! Toporama is derived from CanVec - it
shows differences between paved and unpaved tertiary roads by using different
color :-).</FONT></SPAN></DIV>
<DIV><SPAN class=729334611-01042010></SPAN><SPAN class=729334611-01042010><FONT
color=#0000ff size=2 face=Arial> </FONT></SPAN></DIV>
<DIV><FONT color=#0000ff size=2 face=Arial></FONT><BR>There are no duplicate
intersecting nodes! Way to go team! :-)<SPAN
class=729334611-01042010><FONT color=#0000ff size=2 face=Arial>
Yes! </FONT></SPAN><BR><BR>The 'red lines' that are visably fatter than the
tertiary lines. as 'motorways' (for the ones that have more than 2 lanes)
these would have a number reference. (would be a provincial road)<SPAN
class=729334611-01042010><FONT color=#0000ff size=2 face=Arial>
</FONT></SPAN>otherwise it's a 'secondary' <SPAN
class=729334611-01042010><FONT color=#0000ff size=2 face=Arial> They are
supposed to. If some dont, let me know where they
are. </FONT></SPAN><BR><BR>'primary_link' does exist, that's awesome!<SPAN
class=729334611-01042010><FONT color=#0000ff size=2 face=Arial> The
CanVec "Ramp" processing is cleaver. </FONT></SPAN><BR><BR>What i dont
see is a "source date" tag. I guess the assumption is that it all
still exists, unless it's known that it doesnt? by local knowledge which would
know better?<SPAN class=729334611-01042010><FONT color=#0000ff size=2
face=Arial> The only thing that tag says is that the feature was
there at that time. Only local knowledge can confirm that it is still there wich
is the case 95%</FONT></SPAN><BR><BR>...<BR>Yup. From digging through the
Quebec sample, i cant find anything wrong. <BR>Can anyone
else?<BR><BR>Cheers,<BR>Sam<BR><BR><BR><BR></DIV>
<DIV class=gmail_quote>On Wed, Mar 31, 2010 at 9:02 AM, Brent Fraser <SPAN
dir=ltr><<A href="mailto:bfraser@geoanalytic.com"
target=_blank>bfraser@geoanalytic.com</A>></SPAN> wrote:<BR>
<BLOCKQUOTE
style="BORDER-LEFT: rgb(204,204,204) 1px solid; MARGIN: 0pt 0pt 0pt 0.8ex; PADDING-LEFT: 1ex"
class=gmail_quote>My personal favorite, Waterton Park (82H04)in Alberta,
specifically the townsite:<BR><BR>49.0 to 49.1<BR>-113.9 to -114.0<BR><BR>Best
Regards,<BR>Brent Fraser<BR>
<DIV>
<DIV></DIV>
<DIV><BR>Bégin wrote:<BR>> Bonjour!<BR>><BR>> I'm ready to release
some samples to get your feedback on the Canvec.osm<BR>> product. I
wont be able to release complete NTS datasets because tiling<BR>> procedure
is not completed yet.<BR>><BR>> So, if you send me the bounding box of
the area you wish to look at<BR>> (max 0.1 X 0.1 degrees lat/lon -
all include in the same map sheet), I<BR>> should be able to create the
sample an provide it to you and to the<BR>> community. I will
identify all created sample in the wiki (Canvec page)<BR>> and they will be
made available from NRCan ftp site.<BR>><BR>> I might produce a dozen of
datasets, so, first in - first out!<BR>><BR>> Cheers,<BR>><BR>>
Daniel<BR>><BR>><BR>><BR>><BR>><BR></DIV></DIV>>
------------------------------------------------------------------------<BR>><BR>>
_______________________________________________<BR>> Talk-ca mailing
list<BR>> <A href="mailto:Talk-ca@openstreetmap.org"
target=_blank>Talk-ca@openstreetmap.org</A><BR>> <A
href="http://lists.openstreetmap.org/listinfo/talk-ca"
target=_blank>http://lists.openstreetmap.org/listinfo/talk-ca</A><BR><BR><BR>_______________________________________________<BR>Talk-ca
mailing list<BR><A href="mailto:Talk-ca@openstreetmap.org"
target=_blank>Talk-ca@openstreetmap.org</A><BR><A
href="http://lists.openstreetmap.org/listinfo/talk-ca"
target=_blank>http://lists.openstreetmap.org/listinfo/talk-ca</A><BR></BLOCKQUOTE></DIV><BR>
<DIV style="DISPLAY: inline"></DIV><INPUT type=hidden><INPUT type=hidden>
<DIV></DIV>
<DIV style="DISPLAY: inline"></DIV><INPUT type=hidden><INPUT type=hidden>
<DIV></DIV>
<DIV style="DISPLAY: inline; VISIBILITY: hidden" id=avg_ls_inline_popup></DIV>
<STYLE type=text/css>#avg_ls_inline_popup {
Z-INDEX: 9999; POSITION: absolute; TEXT-ALIGN: left; PADDING-BOTTOM: 0px; LINE-HEIGHT: 13px; MARGIN-TOP: 0px; PADDING-LEFT: 0px; WIDTH: 240px; PADDING-RIGHT: 0px; WORD-WRAP: break-word; COLOR: black; MARGIN-LEFT: 0px; FONT-SIZE: 10px; OVERFLOW: hidden; PADDING-TOP: 0px
}
</STYLE>
<INPUT id=gwProxy type=hidden><INPUT id=jsProxy onclick=jsCall(); type=hidden>
<DIV id=refHTML></DIV></BODY></HTML>