<!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.18928"></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>Bonjour Adam - and all,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>Needs to fix something? So
far...</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010><EM>Toponymy - too many spaces along with
cardinal direction: </EM></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>It seems to be a problem with some of the original
BC data. I will log it to appropriate authorities to have the source
corrected. No program fixes needed. It will have to be done by
local mappers when necessary.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010><EM>Toponymy - Derived from NHN
data:</EM></SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>When toponyms becomes available in NHN data, they
are included in the next Canvec release - usually within less than 6
months</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT><EM>Reefs - duplicate way tagged
natural=water:</EM></SPAN></FONT></DIV></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>In Canvec Product, a reef creates a hole in the
surrounding water area. I did not changed the Canvec data model, except for
addressing schema. If you use the duplicate way tagged natural=water, it should
be to define an inner polygon in a Multipolygon relation. I would suggest
to check the rendering for each scenario - even if we are not supposed to
map for the rendering...</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010><EM>Coastline - changing natural=water for
natural=coastline for coastal water:<BR></EM>It all depends on the definition of
coastal water! The Canvec data is derived from GeoBase NHN. If
something is identified as a coastal water body in NHN product, it will be
tagged natural=coastline in Canvec.osm. If not, it will tagged as natural=water.
No fixes need.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>Cheers,</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2 face=Arial><SPAN
class=840135614-02072010>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> Adam Dunn [mailto:dunnadam@gmail.com]
<BR><B>Sent:</B> 30 juin 2010 14:47<BR><B>To:</B> Bégin, Daniel<BR><B>Cc:</B>
Talk-CA OpenStreetMap<BR><B>Subject:</B> Re: [Talk-ca] Canvec.osm Product - Last
Call !!!<BR></FONT><BR></DIV>
<DIV></DIV>@Daniel: Not fixing the triple space thing that goes along with
cardinal directions?<BR><BR>@All: Reefs are currently being made with a
duplicate way marked as natural=water. Is this necessary? I'm not experienced
with tagging maritime objects.<BR><BR>A while ago, Sam asked about having
natural=water changed to natural=coastline for coastal waters, but I see it
isn't fixed yet.<BR><BR>When Yan did the NHN nl_flow conversion, he decided to
put the name data into name:1, his reasoning being that NHN sl_water and NHN
waterbody also have the name tags, and those would eventually be imported, and
the name tags could come from those (and just double checked against the nl_flow
name:1). Now there's talk of not doing NHN since it's all included in CanVec.
The current samples from Daniel don't have names on the hydrological features
(at least the Vancouver 092G06 area), however. Is more NHN data going to be
included in future CanVec data, or should names be copied over from
nl_flow?<BR><BR>Adam<BR><BR>
<DIV class=gmail_quote>On Tue, Jun 29, 2010 at 1:27 PM, Bégin, Daniel <SPAN
dir=ltr><<A
href="mailto:Daniel.Begin@rncan-nrcan.gc.ca">Daniel.Begin@rncan-nrcan.gc.ca</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>
<DIV>
<DIV><FONT size=2 face=Arial>Bonjour à tous,</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>The Canvec.osm Product engine is ready to
launch. I have used it to create a new version of the sample
files. <A href="http://wiki.openstreetmap.org/wiki/CanVec"
target=_blank>http://wiki.openstreetmap.org/wiki/CanVec</A></FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>Have a look at them and check if everything is as
expected. If there is no problem detected until
next <SPAN>week</SPAN>, it <SPAN>should </SPAN>be turned ON<SPAN> on
monday morning (10-07-05)</SPAN>.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=2 face=Arial>Cheers,</FONT></DIV>
<DIV> </DIV><FONT color=#888888>
<DIV><FONT size=2
face=Arial>Daniel</FONT></DIV></FONT></DIV><BR>_______________________________________________<BR>Talk-ca
mailing list<BR><A
href="mailto:Talk-ca@openstreetmap.org">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></BLOCKQUOTE></DIV><BR></BODY></HTML>