Hi Sam, I agree with this approach. In the test area I imported I followed the procedure you described. There were a few larger river mouths, but they were clearly indicated. Right now I'm getting myself moved back to the Netherlands, so I haven't made a lot of progress since.
By the way, there are (at least) two different water areas at the coast. I believe one of them includes tidal flats / mudflats. Should they be imported differently? If so, how? I looked at the Map features page on the wiki a while back, but couldn't find something which was really appropriate. Frank Quoting Sam Vekemans <[email protected]>: > Hi all, > > It looks like on the chart i had it listed as natural=water. From a quick > discussion on the IRC, it looks like the natural=coastline does this job. > As we do NOT put polygons of water out in the ocean. > Apparently, it's in the typ file for when Garmin MapSource is able to > convert the osm files. ... and it COULD get shown up so then all the coastal > areas is blue. (as if it was 1 hudge polygon). > > I have not confirmed this myself, as it still shows up as white space... but > it might be because my typ files is set to openmtbmap styles. > > In the Ibycus topo, Dale added this feature in. (but put it as 'small lake' > .. however, the 'sea/ocean typ is available, as code 0x28 (0x0028 with > gpsmapedit) > > I propose that these .osm files DO get made available. So then custom maps > can be generated, were the user can go to the NRCan site and download that > .osm file. So then it can be added in, when creating a map. ... ie. > converting the .osm file using mapgen or mkgmap. > > Also note that there IS a polygon in the canvec dataset that is the same > (but more detailed) than the currennt coastlines that are availalable in OSM > right now. One option is that the .osm file can be loaded into osm, then > you cut the polygon so that only the coastline edge is shown and remove the > rest. then change the polyline to natural=coastline and swap it for what > currently exists. > > That other polygon is actually from GeoBase NHN data, where it is filed > under 'island', where (for example) all of Vancouver Island is available as > a single large polygon. thats why you see alot of points around that say > 'place=island name=Vancouver Island' > > ... so in sum, i recommend NOT importing it... BUT still making the Oceab > polygon .osm files available for use. > > Cheers, > Sam > > P.S. im working on the canvec conversion chart a but more. Here is the link > to edit directly > https://spreadsheets.google.com/ccc?key=0Am70fsptsPF2clAwc29KaXlGaGFwS1piUkxZWjc0ekE&hl=en > > I created a new sheet and added in columns for the canvec descriptions (just > like how on the wiki it is listed) i also added in the french version of it > too. > > Over on the origional char, i also am adding in what the garmin typ file > standard is, as this excercies is the 1st step in trying to internationalize > all of the OSM tags so then they can be understood. In another chart, i'll > be adding in what the other map editors & tools use, to create the same > thing. Garmin MapSource is a great place to start, as the device only has > a strict set of features that it allows to be shown. ... but thats > another story :-) > > Twitter: @Acrosscanada > Blog: http://Acrosscanadatrails.blogspot.com > Facebook: http://www.facebook.com/sam.vekemans > Skype: samvekemans > OpenStreetMap IRC: http://irc.openstreetmap.org > @Acrosscanadatrails > _______________________________________________ Talk-ca mailing list [email protected] http://lists.openstreetmap.org/listinfo/talk-ca
