I haven't been able to find any other issues with the Vancouver area data, and the solutions to these problems seem reasonable. So I guess it's okay to go ahead with what we have.<br><br>On the topic of reefs: from what I've seen in comparing Canvec reefs with aerial photography, it looks like reefs will have to be handled on a case-by-case basis anyways. Thus, changing the tag mapping schema for this conversion process probably wouldn't help anyways.<br>
<br><div class="gmail_quote">On Fri, Jul 2, 2010 at 9:07 AM, 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 class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>Bonjour Adam - and all,</span></font></div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>Needs to fix something? So
far...</span></font></div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span><i>Toponymy - too many spaces along with
cardinal direction: </i></span></font></div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>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 face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span><i>Toponymy - Derived from NHN
data:</i></span></font></div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>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 face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span></span></font><i>Reefs - duplicate way tagged
natural=water:</i></div></span></font></div></div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>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 face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span><i>Coastline - changing natural=water for
natural=coastline for coastal water:<br></i>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 face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>Cheers,</span></font></div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span></span></font> </div>
<div dir="ltr" align="left"><font face="Arial" color="#0000ff" size="2"><span>Daniel</span></font></div><br>
<div dir="ltr" lang="en-us" align="left">
<hr>
<font face="Tahoma" size="2"><b>From:</b> Adam Dunn [mailto:<a href="mailto:dunnadam@gmail.com" target="_blank">dunnadam@gmail.com</a>]
<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></div><div class="h5">
<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></div></blockquote></div><br>