Hi all,<br><br><div class="gmail_quote">2008/11/26 Dave Hansen <span dir="ltr"><<a href="mailto:dave@sr71.net">dave@sr71.net</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="Ih2E3d">On Wed, 2008-11-26 at 01:40 -0800, Sam Vekemans wrote:<br>
><br>
><br>
><br>
> I do think it was important to have things broken up<br>
> geographically. It<br>
> makes it much easier if something goes bad to find the data,<br>
> remove it,<br>
> an retry.<br>
><br>
><br>
> Since the data is broken up into Geobase tiles, perhaps importing by<br>
> tile area to get more specific. The provinces are rather large, so<br>
> going at it, by 1 degree x 2 degree would be better??<br>
<br>
</div>Yes, it probably would be better. However, there is also the problem of<br>
stitching things back together in the end. I never dealt with that<br>
part.<br>
<br>
Also 1x2 degrees probably isn't bad for, say, the Yukon Territories.<br>
But, I would imagine that Toronto is going to fit almost entirely into<br>
one of those. That might pose a few problems. I think the largest .osm<br>
file that I uploaded was Kern county in California. It was 165MB.</blockquote><div><br> <meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.0 (Win32)"><style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<p style="margin-bottom: 0cm;" lang="en-CA"><font color="#000080"><font face="Arial"><font size="2">A
regular tile size looks fine to me but will introduce duplicates
along the edges. How do we handle polygons that cross the bounding
box ? From my experience, uploading data with josm has a limitation
number. Beyond that limitation josm stops, therefore leaves a mess in
the database. May be there are others ways to upload large amount of
data.</font></font></font></p>
<br><br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div class="Ih2E3d"><br>
> One thing I never considered, but did come back to bite me a<br>
> few times<br>
> was concurrency. I'd upload a node, make a way use it, then<br>
> come back a<br>
> few hours later to have another way use the node. But,<br>
> somebody got to<br>
> the node before I did. There were three or four of these and<br>
> I fixed<br>
> them up by hand. It sucked. :)<br>
><br>
><br>
> Well, remember (last week i think it was) when OpenStreetMap was shut<br>
> down for maintenance?<br>
> Well, what about convincing the foundation to shut down the server so<br>
> then all the data can be uploaded at once?<br>
> That would fix the problem that you had. :)<br>
<br>
</div>Sure, if you can pull this off, go for it. Otherwise, it isn't *that*<br>
difficult of a thing to plan for and fix.<br>
<br>
Basically, if you notice that some node that you need is gone, you just<br>
re-upload a new copy of the original node and make a note of it. It's<br>
that simple.<br>
<div><div></div><div class="Wj3C7c"><br>
> Keep a record of everything that you do. Keep good logs and<br>
> make sure<br>
> that whatever programs you use to upload the data can be<br>
> stopped and<br>
> restarted at any time with no ill effects. This generally<br>
> means keeping<br>
> a table of which objects have been uploaded and their id<br>
> mappings.<br>
<br>
><br>
> I think we already discovered that the natural features shapefiles<br>
> data, shouldnt post any conflect... not a major one that is. ... Every<br>
> city does have some kind of water feature, and it's probably labeled,<br>
> but thats about it.<br>
> and for the other features .... ya pausing OpenStreetMap to make the<br>
> import happen. would guarentee no point conflicts.<br>
><br>
><br>
> I<br>
> think bulk-upload.pl<br>
> <a href="http://wiki.openstreetmap.org/wiki/Bulk_import.pl" target="_blank">http://wiki.openstreetmap.org/wiki/Bulk_import.pl</a><br>
> does this pretty well, although I did have to<br>
> customize it a bit.<br>
> Ya, as as far as i can see, the way that GeoBase keeps the data is a<br>
> bit different.<br>
> each province does have a different way of classing roads. .. so when<br>
> your literally traveling between provinces.. the pavement is<br>
> identical.. yet the signs on the roads indicate a different road<br>
> class. (thats because provincial roads are funded provincially, there<br>
> is very little discussion between provinces. So each provincial<br>
> upload would be different. (talk-ca talked about it back in the<br>
> summer)<br>
<br>
</div></div>Yeah, one of the first steps is to come up with a conversion scheme to<br>
convert your features into OSM features.<br>
<font color="#888888"><br>
-- Dave<br>
</font></blockquote><div><br><meta http-equiv="CONTENT-TYPE" content="text/html; charset=utf-8"><title></title><meta name="GENERATOR" content="OpenOffice.org 3.0 (Win32)"><style type="text/css">
<!--
@page { margin: 2cm }
P { margin-bottom: 0.21cm }
-->
</style>
<p style="margin-bottom: 0cm;"><font color="#000080"><font face="Arial"><font size="2"><span lang="en-CA">Geobase
has a uniformed road classification. The matching between osm
and geobase road classes should be applicable globally. I suspect
that local contexts may be necessary in some cases (ramp
classification form example). We can start Geobase NRN - OSM Map Feature. I can start this.</span></font></font></font></p><p style="margin-bottom: 0cm;"><br><font color="#000080"><font face="Arial"><font size="2"><span lang="en-CA"></span></font></font></font></p>
<p style="margin-bottom: 0cm;"><font color="#000080"><font face="Arial"><font size="2"><span lang="en-CA">Cheers,</span></font></font></font></p><p style="margin-bottom: 0cm;"><font color="#000080"><font face="Arial"><font size="2"><span lang="en-CA">Michel<br>
</span></font></font></font></p><p style="margin-bottom: 0cm;"><br><font color="#000080"><font face="Arial"><font size="2"><span lang="en-CA"></span></font></font></font></p><p style="margin-bottom: 0cm;"><font color="#000080"><font face="Arial"><font size="2"><span lang="en-CA"><br>
</span></font></font></font>
</p>
</div></div><br>