[Talk-ca] Canvec.osm Product - Last Call !!!

[Bégin, Daniel]

Bonjour Adam - and all,
 
Needs to fix something?  So far...
 
Toponymy  - too many spaces along with cardinal direction: 
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.
 
Toponymy - Derived from NHN data:
When toponyms becomes available in NHN data, they are included in the next Canvec release - usually within less than 6 months
 
Reefs - duplicate way tagged natural=water:
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...
 
Coastline - changing natural=water for natural=coastline for coastal water:
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.
 
Cheers,
 
Daniel

________________________________

From: Adam Dunn [mailto:dunnadam at gmail.com] 
Sent: 30 juin 2010 14:47
To: Bégin, Daniel
Cc: Talk-CA OpenStreetMap
Subject: Re: [Talk-ca] Canvec.osm Product - Last Call !!!


@Daniel: Not fixing the triple space thing that goes along with cardinal directions?

@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.

A while ago, Sam asked about having natural=water changed to natural=coastline for coastal waters, but I see it isn't fixed yet.

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?

Adam


On Tue, Jun 29, 2010 at 1:27 PM, Bégin, Daniel <Daniel.Begin at rncan-nrcan.gc.ca> wrote:


	Bonjour à tous,
	 
	The Canvec.osm Product engine is ready to launch.  I have used it to create a new version of the sample files.  http://wiki.openstreetmap.org/wiki/CanVec
	 
	Have a look at them and check if everything is as expected.  If there is no problem detected until next week, it should be turned ON on monday morning (10-07-05).
	 
	Cheers,
	 
	
	Daniel

	_______________________________________________
	Talk-ca mailing list
	Talk-ca at openstreetmap.org
	http://lists.openstreetmap.org/listinfo/talk-ca
	
	


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-ca/attachments/20100702/b4a32b4a/attachment.html>