Re: [Talk-ca] NTS Canada- OSM Import Progress Chart was edited recently
Hi all, I get a regular notification of each change on the spreadsheet. I'm just monitoring it to see that no super big changes happen, that make others loose their place :) At some point, users will get an error of 'too many cells', please let me know if that is encountered, then I can fix it :) Great to see lots of people are updating the chart ... I know it's a slow and steady import process, so the idea is to make sure that the more active users all know who is working where :) ... Let me know if their are any issues with the chart, and i can see what i can do. Although i'm not actualy editing with this API, i'm still active with all the other projects :) cheers, sam On 2/13/11, Google Docs not...@google.com wrote: See the changes in your Google Document NTS Canada- OSM Import Progress Chart: http://spreadsheets.google.com/ver?key=tDERPhtQfnbbGpA0tx32C3Qt=1297614169224000pt=1297614140382000diffWidget=trues=AJVazbWJ7STrzftFq9cwbjTnEnIfXJUStQ A user made changes from 2/13/11 8:22 AM to 8:22 AM Values changed Copy/Paste Open the current version of your Google Document NTS Canada- OSM Import Progress Chart: http://spreadsheets.google.com/ccc?key=tDERPhtQfnbbGpA0tx32C3Q Powered by Google Docs --- Want to stop receiving this email? http://spreadsheets.google.com/nt?key=tDERPhtQfnbbGpA0tx32C3Qr=-6095872962184607126 -- 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] Simplifying CanVec imports
Does simplifying like this cause issues where one feature joins up with another feature? I'm assuming that JOSM won't move end nodes of ways during simplification, so rivers connecting to lakes should be okay, but what about places where there is a common node in the middle of a way? Are there instances of this in Canvec, or does the Canvec conversion process always split ways where there are nodes common to more than one object? If you simplify ways today, how will that affect imports in the future, when the next version of Canvec comes out? Adam On Sun, Feb 13, 2011 at 8:45 AM, Daniel Begin jfd...@hotmail.com wrote: Hi Samuel, It might be a good idea to simplify some features before importing. It is not necessary for all features, and the feature's node density usually varies by provinces/theme. In BC, hydro network is really dense as you already figured out. In Quebec, the new road network often needs to by simplified. I would say just do it if it is required for the tile/theme you are importing Daniel From: Samuel Longiaru [mailto:longi...@shaw.ca] Sent: February-11-11 10:38 To: talk-ca@openstreetmap.org Subject: [Talk-ca] Simplifying CanVec imports Good Morning Everyone, For the past couple of weeks I have been importing CanVec data into an area southwest of Kamloops. There was very little (if any) existing OSM data in the area. I've gotten into a bit of a rhythm, merging and stitching all of 92I07 and about half of 92I10 but started becoming concerned about the high data density, particularly associated with streams in the area. Most import files at the level of 92 I 07.0.0 for example, are runnning 10-15k nodes. At that rate, that is somewhat near 200,000 nodes for an area at the level of 92I07. Yikes! I guess the question in my mind is just how many data do we want to import at this level and what are the practical implications for server processing and overload. I expect that this level would be fairly consistent across most of Western Canada. Even now, I haven't been able to call up a complete map in the openstreet.org view tab for the past 4 or 5 days... 25-50% of the map being covered with ... more OSM coming soon tiles. I looked at the Simplify Way function in JOSM and applying it to just the water data, have been able to eliminate 5-8k nodes from each file, thereby cutting the data in nearly half. I really don't see any significant degradation in the map quality as a result. Without simplifying, the data nodes in some places are incredibly (and undeservedly ) dense. The only discussion I've been able to find on the simplify tool is some rather old discussion that took place during development. So just wondering if simplifying these data is a reasonable approach. Right now, I am going back to the imported areas, calling them up from OSM, simplifying the water, and re-uploading the simplified data. In the future, I will just simplify in JOSM before uploading the file in the first place. Anyway, does anyone have any issues with my approach here? Is it worth simplifying or am I being overly concerned about data density and its longer term implications? Thanks, Sam Longiaru Kamloops, BC ___ 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] Simplifying CanVec imports
Yes, the import seems to be quite a selective process! Very tedious at times. And now that I am getting into areas where there actually is some existing OSM data and I have spent so much time hand editing in the past, I'm pretty careful to select the better data on a way-by-way basis. Sometimes the CanVec data wins out, sometimes not. In regards to simplifying, however, I am quite pleased to note that I have not seen displacement or removal of a node that sits at the edge of a tile. I'm sure they are just taken as end points. Simplifying a feature that will ultimately run from one tile to the next still yields duplicate nodes at the boundary when the next file is brought in. The stitching procedure is the exactly the same. Merge nodes and combine ways where appropriate. I just think it is a great tool that admittedly may only have limited applications. But I think that this situation is definitely one of them. Sam -Original Message- From: john whelan jwhelan0...@gmail.com To: Talk-CA OpenStreetMap talk-ca@openstreetmap.org Cc: Samuel Longiaru longi...@shaw.ca Subject: Re: [Talk-ca] Simplifying CanVec imports Date: Sun, 13 Feb 2011 18:41:21 -0500 There are always issues when you want to replace one set of data with another. People may have added labels such as the name in French, replace the import and you lose the French. Where the CANVEC tiles meet ways are connected by overlapping points. Any simplification at this point that moves a point on a way means the way doesn't get joined where the tiles meet. This is why it''s so tempting to start over from CANVEC 7 then add in the detail, amenities, shops etc. At least you can have confidence that the road names are correct. Cheerio John ___ Talk-ca mailing list Talk-ca@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-ca
