Re: [Talk-ca] Canvec.osm Product almost...
Hi all, Does everyone agree with Adam's position? It is still time to change that kind of things... Daniel From: Adam Dunn [mailto:dunna...@gmail.com] Sent: 21 juin 2010 17:00 To: Bégin, Daniel Cc: talk-ca@openstreetmap.org Subject: Re: [Talk-ca] Canvec.osm Product almost... On Mon, Jun 21, 2010 at 9:54 AM, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Problems solved... - Misspelled highway=unclasified: Corrected for the release; OSM also prefers the British way of spelling centre (American way is center, usually). Current demo data for Vancouver is using k=amenity v=community_center k=leisure v=sports_center and these should be changed to use re Is there a final date for getting in problems? Should people be doing full dry-run imports to make sure all bugs are ironed out before then? Adam ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
On 22 June 2010 12:57, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Hi all, Does everyone agree with Adam's position? It is still time to change that kind of things... It would truly be more consistent indeed. Can't get tagwatch to confirm though. Emilie Laffray ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
On Tue, Jun 22, 2010 at 8:04 AM, Emilie Laffray emilie.laff...@gmail.com wrote: On 22 June 2010 12:57, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: [Adam said, OSM uses centre rather than center for most tags. ] Hi all, Does everyone agree with Adam's position? It is still time to change that kind of things... It would truly be more consistent indeed. Can't get tagwatch to confirm though. Map Features confirms this and lists sports_centre, arts_centre, community_centre, garden_centre and social_centre. I hope that I haven't typo'ed these. ;-) http://wiki.openstreetmap.org/wiki/Map_Features OsmDoc also confirms that _centre is preferred in the wild. The OsmDoc data is from last August, and shows 12,000 instances of sports_centre, but only 16 of sports_center. http://osmdoc.com/en/tag/leisure/#values This applies for leisure and amenity tags, etc. but not for name tags. If the sign says, My Town Community Center in the US, then leisure=community_centre name=My Town Community Center is the way to tag it. ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Cool, and BTW, when creating the map legend (for end user maps), we can write anything we want so that the intended audience will understand. That the icon in the picture means this In any language /varriation. The OSM tags are all international standards (or as close as we can get) And so, 'center' could also get rendered on mapnik with the same icon. ... But centre wins. Sam On 6/22/10, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Cool, I buy it! - tags using *center: Corrected to *centre for the release; Thanks, Daniel -Original Message- From: talk-ca-boun...@openstreetmap.org [mailto:talk-ca-boun...@openstreetmap.org] On Behalf Of Richard Weait Sent: 22 juin 2010 10:29 To: Talk-CA OpenStreetMap Subject: Re: [Talk-ca] Canvec.osm Product almost... On Tue, Jun 22, 2010 at 8:04 AM, Emilie Laffray emilie.laff...@gmail.com wrote: On 22 June 2010 12:57, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: [Adam said, OSM uses centre rather than center for most tags. ] Hi all, Does everyone agree with Adam's position? It is still time to change that kind of things... It would truly be more consistent indeed. Can't get tagwatch to confirm though. Map Features confirms this and lists sports_centre, arts_centre, community_centre, garden_centre and social_centre. I hope that I haven't typo'ed these. ;-) http://wiki.openstreetmap.org/wiki/Map_Features OsmDoc also confirms that _centre is preferred in the wild. The OsmDoc data is from last August, and shows 12,000 instances of sports_centre, but only 16 of sports_center. http://osmdoc.com/en/tag/leisure/#values This applies for leisure and amenity tags, etc. but not for name tags. If the sign says, My Town Community Center in the US, then leisure=community_centre name=My Town Community Center is the way to tag it. ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca -- Twitter: @Acrosscanada Blogs: http://acrosscanadatrails.posterous.com/ http://Acrosscanadatrails.blogspot.com Facebook: http://www.facebook.com/sam.vekemans Skype: samvekemans IRC: irc://irc.oftc.net #osm-ca Canadian OSM channel (an open chat room) @Acrosscanadatrails ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Hi, On Mon, Jun 21, 2010 at 9:54 AM, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Bonjour à tous, It seems that the product triggers some interest over the community! Here are answers to some comments I received last week/weekend. Yup, Over in Vancouver were talking a close look at it also :) Problems solved... - Misspelled highway=unclasified: Corrected for the release; - Duplicated hydrological features: Corrected for the release; Awesome... i have no idea how you managed todo that, but great work :-) - Turning_circle: Will be removed for the release (1); - Bridge layer: Will be set to layer=1 for the release; Model paradigm... The following items are related to the Canvec data model. I will have a look but I cant guaranty anything. However, I will forward your comments to eventually have the model changed. - Duplicated ways between footway and footway bridges; - Duplicate Nodes on bridges crossing over roads; Miscellaneous... - Toponyms: Only local mappers can modify it properly; - Huge forest areas: Should be OK with Quad Tree tiling (2); - Overlapping features: They will show-up as errors in the Validator. This was a choice that have been made to ease the upload of a selected subset of features where there were already corresponding data in Osm. Cheers, Daniel (1): Nays have a good majority Hi, another option that came up in OSM-CA IRC chat was noexit=yes to indicate road stops. Perhaps using it in the fixme notes? http://wiki.openstreetmap.org/wiki/Key:noexit OTOH, local mappers would be able to check and see exactly what type of road-end it is :) (2): Frank Steggink - bonjour Frank - has done a massive upload of forest areas, NE of Quebec city, using small tiles. I used his experiment results to figure out the number of nodes that should trigger tile splitting. The Quad Tree algorithm usually creates tiles smaller than Frank's experiment. It should be OK then. ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca P.S. Ok, so there's no response about the idea for uploading the NTS Tile rectangles and indicating what the status of the data in that area is. So is this not a concern for people? And are we all confident that we are just treating the data like top-quality Yahoo imagery, where it is used to supplement the existing OSM map with more features where it's needed? If so, that's fine. My concern is about overloading the OSM servers, as there will be TONNES of data added into OSM over the next few months / few years as this progresses. So is the consensus that we WONT be overloading the servers, because we do not plan on announcing to the world whats going on, and as more local mappers find out about this, they will be working on their own tiles. Ie. I map my house, you map your house and eventually we'll map the world? Cheers, Sam ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Salut Daniel, Yes, I'm still alive :) but unfortunately I can't find much time to follow what is going on in Canada. (The import of Dutch landuse data is partially to blame ;) ) As you might expect, I've looked a bit at the 021L14 data (Quebec City area). Here are some comments, and hopefully I'm not touching something again which was discussed in the past. * Some ways are duplicated. They are all hydrological features (landuse=basin, landuse=reservoir, natural=water). This is even true for the St. Lawrence river. * I think it would be a good idea to split up each file in 3 files, namely one for roads (what one would typically find in the NRN), one for hydrological features (as in the NHN), and the rest. The reason is that in many areas roads and or hydro features have already been imported (be it originally created or Canvec/Geobase based), but this is not true for the other features. -- A consequence of this is that the same node could be found in different files. I think that this should be taken care of during the import process. As Sam mentions, it is not just 'plopping' the data in OSM, but this kind of processing (and also properly connect features over tile boundaries, etc.) is also part of it. * Can you get rid of the turning circles at the end of the roads? I bet they are more often non-existing than actually existing. * Bridges have no layer tags. Probably the actual layer can't be determined correctly, but usually it will be layer=1, so that is a good default. -- Regarding bridges: I actually don't like the fact that when a bridge crosses a road below it, they both share the same node. This does not occur physically. However, if you leave duplicate nodes in there (which would throw a wrench in the dedup process), then this might be incorrectly be seen as a duplicate node. A workaround could be to give one of the nodes a small offset. * How are you going to deal with the issue I raised in the past about huge forest areas? In the sample areas you didn't split up the forests into multiple shapes (or multipolygons). OTOH, I don't like to have to split up, with the sole purpose to make JOSM more responsive. It might be possible that JOSM has improved in this regard as well. (I'm yet clueless as to how Potlatch would deal with it.) * There is an area overlap between several features, like natural=wood and natural=wetland. This must come from the source data. I think that in this particular case it is justified, namely a wooded marsh/swamp. Anyways, keep up the good work :) Thanks, Frank On 10-06-17 07:00 PM, Bégin, Daniel wrote: Bonjour! Before the Canvec.osm production starts, I have produced complete NTS datasets for samples previously offered - actually I have expanded the samples to cover the entire NTS tile and add 092G06. Each NTS dataset have been tiled using a quadtree algorithm - a nice example of the result is 092G06 ! The .osm subtiles are zipped all together. We are still using WinZip but we might eventually move to gzip or bzip. Have a look! And, by the way, can you make sure everything is still OK with the data? Cheers, Daniel *From:* talk-ca-boun...@openstreetmap.org [mailto:talk-ca-boun...@openstreetmap.org] *On Behalf Of *Bégin, Daniel *Sent:* 15 juin 2010 15:10 *To:* talk-ca@openstreetmap.org *Subject:* [Talk-ca] Canvec.osm Product almost... Bonjour à tous, We are still on schedule for Canvec.osm product. We should be able to start the production later next week. Each NTS will be tiled using a quadtree algorithm. A tile splits when there is more than 25K nodes in it. Each tile is named after the dataset name + tiling subtree. Subtree naming convention is 0=SW, 1=NW, 2=NE, 3=SE. Each subtree level is separates with a . - like in 021E05.3.2.1 Example: http://wiki.openstreetmap.org/wiki/CanVec#Canvec_Product_-_Osm_format Regarding splitting threshold, 50K nodes is Osm xapi maximum. With 25K nodes I make sure you can add all the stuff you have/that is already available over the area before uploading it. Cheers, Daniel ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Cool idea :) (i don't actually use validator) as i know its not all correct 'validations', but i should probably take iniciative and work to fix it :) Anyway, please do describe the 'errors', so we can go through the list and see what Daniel the CanVec product team can possably fix. I don't see it as a 'pain' to fix, since we need local area mappers to help validate the data. But yes, if their is stuff like 'unclaSsified', it all helps remove the need to create a 'CanVec cleanup Bot' sometime down the road. Cheers, Sam On 6/18/10, Michael Barabanov michael.baraba...@gmail.com wrote: I did a simple test of opening a file from 092G02 zip and hit Upload in JOSM (didn't actually upload, of course). There's a bunch of errors from the validator plugin. I think it'd be good to fix those in the converter, otherwise it'll be a pain to resolve manually. On Fri, Jun 18, 2010 at 2:02 AM, Adam Dunn dunna...@gmail.com wrote: Opened up 092G06. highway=unclassified is misspelled. The 092G06 data has highway=unclasified (with one 's'). footway bridges appear to be duplicated on top of the non-bridge footway that they are a part of. In other words, a [highway=footway] will continue the entire length of the path (including the bridge), and there is a second way [highway=footway;bridge=yes] where only the bridge is. cardinal direction modifiers have 3 spaces after them (eg. West 8th Avenue). I'm not sure what the standard is for OSM, since the wiki doesn't seem to talk about it. railway/road intersections don't have a common node. There is also a very long rail tunnel that runs from beside the Ironworkers Memorial Bridge down to near the intersection of Trans-Canada Highway and Willingdon Avenue, but this tunnel appears to be missing from Canvec. (as a side note: Canvec has the bridge for Trans-Canada going over Burrard Inlet called Hwy 1;Second Narrows Bridge;Trans-Canada Highway;TransCanada Highway {note the Second Narrows Bridge part}. It should actually be called Ironworkers Memorial Second Narrows Crossing and the rail bridge beside it is Second Narrows Bridge. See http://en.wikipedia.org/wiki/Ironworkers_Memorial_Second_Narrows_Crossing) Other data that I see in error is the standard old source problems (buildings that have since been constructed/demolished, especially in the rapid construction that happens at Univ. BC), streams/rivers not having names (but that was expected). It's nice to see that highway=*_link is being used. It was a pain trying to figure those out with NRN. Adam On Thu, Jun 17, 2010 at 11:57 AM, Richard Weait rich...@weait.com wrote: On Thu, Jun 17, 2010 at 1:00 PM, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Bonjour! Before the Canvec.osm production starts, I have produced complete NTS datasets for samples previously offered - actually I have expanded the samples to cover the entire NTS tile and add 092G06. Each NTS dataset have been tiled using a quadtree algorithm - a nice example of the result is 092G06 ! The .osm subtiles are zipped all together. We are still using WinZip but we might eventually move to gzip or bzip. Have a look! And, by the way, can you make sure everything is still OK with the data? Wonderful news, Daniel! And congratulations. I'll take a look but am slightly {natural=wetland; wetland=swamp}ed, right now. Is it helpful if I have a look next week? ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca -- Twitter: @Acrosscanada Blogs: http://acrosscanadatrails.posterous.com/ http://Acrosscanadatrails.blogspot.com Facebook: http://www.facebook.com/sam.vekemans Skype: samvekemans IRC: irc://irc.oftc.net #osm-ca Canadian OSM channel (an open chat room) @Acrosscanadatrails ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Bonjour! Before the Canvec.osm production starts, I have produced complete NTS datasets for samples previously offered - actually I have expanded the samples to cover the entire NTS tile and add 092G06. Each NTS dataset have been tiled using a quadtree algorithm - a nice example of the result is 092G06 ! The .osm subtiles are zipped all together. We are still using WinZip but we might eventually move to gzip or bzip. Have a look! And, by the way, can you make sure everything is still OK with the data? Cheers, Daniel From: talk-ca-boun...@openstreetmap.org [mailto:talk-ca-boun...@openstreetmap.org] On Behalf Of Bégin, Daniel Sent: 15 juin 2010 15:10 To: talk-ca@openstreetmap.org Subject: [Talk-ca] Canvec.osm Product almost... Bonjour à tous, We are still on schedule for Canvec.osm product. We should be able to start the production later next week. Each NTS will be tiled using a quadtree algorithm. A tile splits when there is more than 25K nodes in it. Each tile is named after the dataset name + tiling subtree. Subtree naming convention is 0=SW, 1=NW, 2=NE, 3=SE. Each subtree level is separates with a . - like in 021E05.3.2.1 Example: http://wiki.openstreetmap.org/wiki/CanVec#Canvec_Product_-_Osm_format Regarding splitting threshold, 50K nodes is Osm xapi maximum. With 25K nodes I make sure you can add all the stuff you have/that is already available over the area before uploading it. Cheers, Daniel ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
(I cheat) I get an instant notification as soon as the wiki gets edited :-) There are 10 areas as a result, Perhaps an easy way to deal with it is for it to be listed on the wiki? So people can indicate what tile they are working on? As well as host a mapping party for this? I just had a look at the bottom right corner of it see that it will take some careful work and a lot has changed in the Vancouver area since the data was created. Others have also indicated to me (off list) that they are interested in working on certain tiles with varing levels of experience. And my recomendation is to message the talk-ca@ list, and also jump on the #osm-ca IRC while working. (so others know whats going on) I have made the recommendation to upload a box around the area and label it as 'under construction', so mapping in that area it could be temporarly put on hold, as it does take time to work on it. (but i havent heard back). The draw back is that it will draw attention to the area, and ther chance of 'bulk_implopping' (which we dont want) is greater. And it's also worth noting that many mappers are NOT on this mailing list. Since im not local to that area im not importing any of them, :) as there are more than enough mappers. .. but i can make a trip over to the mainland do a demo for whoever wants to meet up? Cheers, Sam On Thu, Jun 17, 2010 at 10:00 AM, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Bonjour! Before the Canvec.osm production starts, I have produced complete NTS datasets for samples previously offered - actually I have expanded the samples to cover the entire NTS tile and add 092G06. Each NTS dataset have been tiled using a quadtree algorithm - a nice example of the result is 092G06 ! The .osm subtiles are zipped all together. We are still using WinZip but we might eventually move to gzip or bzip. Have a look! And, by the way, can you make sure everything is still OK with the data? Cheers, Daniel From: talk-ca-boun...@openstreetmap.org [mailto:talk-ca-boun...@openstreetmap.org] On Behalf Of Bégin, Daniel Sent: 15 juin 2010 15:10 To: talk-ca@openstreetmap.org Subject: [Talk-ca] Canvec.osm Product almost... Bonjour à tous, We are still on schedule for Canvec.osm product. We should be able to start the production later next week. Each NTS will be tiled using a quadtree algorithm. A tile splits when there is more than 25K nodes in it. Each tile is named after the dataset name + tiling subtree. Subtree naming convention is 0=SW, 1=NW, 2=NE, 3=SE. Each subtree level is separates with a . - like in 021E05.3.2.1 Example: http://wiki.openstreetmap.org/wiki/CanVec#Canvec_Product_-_Osm_format Regarding splitting threshold, 50K nodes is Osm xapi maximum. With 25K nodes I make sure you can add all the stuff you have/that is already available over the area before uploading it. Cheers, Daniel ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Opened up 092G06. highway=unclassified is misspelled. The 092G06 data has highway=unclasified (with one 's'). footway bridges appear to be duplicated on top of the non-bridge footway that they are a part of. In other words, a [highway=footway] will continue the entire length of the path (including the bridge), and there is a second way [highway=footway;bridge=yes] where only the bridge is. cardinal direction modifiers have 3 spaces after them (eg. West 8th Avenue). I'm not sure what the standard is for OSM, since the wiki doesn't seem to talk about it. railway/road intersections don't have a common node. There is also a very long rail tunnel that runs from beside the Ironworkers Memorial Bridge down to near the intersection of Trans-Canada Highway and Willingdon Avenue, but this tunnel appears to be missing from Canvec. (as a side note: Canvec has the bridge for Trans-Canada going over Burrard Inlet called Hwy 1;Second Narrows Bridge;Trans-Canada Highway;TransCanada Highway {note the Second Narrows Bridge part}. It should actually be called Ironworkers Memorial Second Narrows Crossing and the rail bridge beside it is Second Narrows Bridge. See http://en.wikipedia.org/wiki/Ironworkers_Memorial_Second_Narrows_Crossing) Other data that I see in error is the standard old source problems (buildings that have since been constructed/demolished, especially in the rapid construction that happens at Univ. BC), streams/rivers not having names (but that was expected). It's nice to see that highway=*_link is being used. It was a pain trying to figure those out with NRN. Adam On Thu, Jun 17, 2010 at 11:57 AM, Richard Weait rich...@weait.com wrote: On Thu, Jun 17, 2010 at 1:00 PM, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Bonjour! Before the Canvec.osm production starts, I have produced complete NTS datasets for samples previously offered - actually I have expanded the samples to cover the entire NTS tile and add 092G06. Each NTS dataset have been tiled using a quadtree algorithm - a nice example of the result is 092G06 ! The .osm subtiles are zipped all together. We are still using WinZip but we might eventually move to gzip or bzip. Have a look! And, by the way, can you make sure everything is still OK with the data? Wonderful news, Daniel! And congratulations. I'll take a look but am slightly {natural=wetland; wetland=swamp}ed, right now. Is it helpful if I have a look next week? ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Hi, Just also cc:ing Daniel for your notes. :) On Thu, Jun 17, 2010 at 3:02 PM, Adam Dunn dunna...@gmail.com wrote: Opened up 092G06. highway=unclassified is misspelled. The 092G06 data has highway=unclasified (with one 's'). Great find! footway bridges appear to be duplicated on top of the non-bridge footway that they are a part of. In other words, a [highway=footway] will continue the entire length of the path (including the bridge), and there is a second way [highway=footway;bridge=yes] where only the bridge is. cardinal direction modifiers have 3 spaces after them (eg. West 8th Avenue). I'm not sure what the standard is for OSM, since the wiki doesn't seem to talk about it. I didn't know that :) railway/road intersections don't have a common node. There is also a very long rail tunnel that runs from beside the Ironworkers Memorial Bridge down to near the intersection of Trans-Canada Highway and Willingdon Avenue, but this tunnel appears to be missing from Canvec. Good thing for OSM Local mappers to fix it, i'd say :) (as a side note: Canvec has the bridge for Trans-Canada going over Burrard Inlet called Hwy 1;Second Narrows Bridge;Trans-Canada Highway;TransCanada Highway {note the Second Narrows Bridge part}. It should actually be called Ironworkers Memorial Second Narrows Crossing and the rail bridge beside it is Second Narrows Bridge. See http://en.wikipedia.org/wiki/Ironworkers_Memorial_Second_Narrows_Crossing) Other data that I see in error is the standard old source problems (buildings that have since been constructed/demolished, especially in the rapid construction that happens at Univ. BC), streams/rivers not having names (but that was expected). Use the GeoBase WMS layer http://wms.cits.rncan.gc.ca/cgi/wms_en.cgi?map=/export/wms/mapfiles/rhn/geobase_rhn.mapversion=1.1.1service=WMSrequest=Getmaplayer=HYDRO_AGGREGATformat=image/pngSTYLE=defaultlayers=GEOBASE_RHN_NHN; and the Toporama WMS layer http://wms.ess-ws.nrcan.gc.ca/wms/toporama_en?LAYERS=limits,vegetation,builtup_areas,designated_areas,hydrography,hypsography,water_saturated_soils,landforms,constructions,water_features,road_network,railway,populated_places,structures,power_network,feature_namesSERVICE=WMSVERSION=1.1.1REQUEST=GetMapSTYLES=EXCEPTIONS=application/vnd.ogc.se_inimageFORMAT=image/png; (im now working on getting CanTopo_geo.pdf maps convtered to WMS via MapWarper. http://warper.geothings.net/ Also, YanMorin has created the linear network flow for all of Canada as .osm files, http://osm.progysm.com/rncan/geobase/nhn_rhn/ and it includes the oneway=yes with proper direction arrows, as well as proper geometry (for BC basin) and river names where available :) It's nice to see that highway=*_link is being used. It was a pain trying to figure those out with NRN. Adam And again, everyone is welcome on the #osm-ca IRC chat irc://irc.oftc.net/#osm-ca to join in while working for help, the more people who know the inns and outs of this stuff the better :-) Sam On Thu, Jun 17, 2010 at 11:57 AM, Richard Weait rich...@weait.com wrote: On Thu, Jun 17, 2010 at 1:00 PM, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Bonjour! Before the Canvec.osm production starts, I have produced complete NTS datasets for samples previously offered - actually I have expanded the samples to cover the entire NTS tile and add 092G06. Each NTS dataset have been tiled using a quadtree algorithm - a nice example of the result is 092G06 ! The .osm subtiles are zipped all together. We are still using WinZip but we might eventually move to gzip or bzip. Have a look! And, by the way, can you make sure everything is still OK with the data? Wonderful news, Daniel! And congratulations. I'll take a look but am slightly {natural=wetland; wetland=swamp}ed, right now. Is it helpful if I have a look next week? ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
Re: [Talk-ca] Canvec.osm Product almost...
Awesome! That makes sence to me. Great work! No complains here. What are the exact degree-grid sizes? Thanks, Sam On 6/15/10, Bégin, Daniel daniel.be...@rncan-nrcan.gc.ca wrote: Bonjour à tous, We are still on schedule for Canvec.osm product. We should be able to start the production later next week. Each NTS will be tiled using a quadtree algorithm. A tile splits when there is more than 25K nodes in it. Each tile is named after the dataset name + tiling subtree. Subtree naming convention is 0=SW, 1=NW, 2=NE, 3=SE. Each subtree level is separates with a . - like in 021E05.3.2.1 Example: http://wiki.openstreetmap.org/wiki/CanVec#Canvec_Product_-_Osm_format Regarding splitting threshold, 50K nodes is Osm xapi maximum. With 25K nodes I make sure you can add all the stuff you have/that is already available over the area before uploading it. Cheers, Daniel -- Twitter: @Acrosscanada Blogs: http://acrosscanadatrails.posterous.com/ http://Acrosscanadatrails.blogspot.com Facebook: http://www.facebook.com/sam.vekemans Skype: samvekemans IRC: irc://irc.oftc.net #osm-ca Canadian OSM channel (an open chat room) @Acrosscanadatrails ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca