<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>...</div>
<div>> For pgRouting Qucikstart I have to either download a smaller<br>
> bbox of Denver area for pgRouting, or we could make the area<br>
> smaller in general, and it will also decrease the size of<br>
> pgRouting.<br>
<br>
</div>can the pgRouting postgis db population step be done specifying<br>
a limiting bounding box?<br></blockquote><div><br></div><div>Well, pgRouting takes the downloaded sample data of OSM and calculates network topology and then loads it into a database.</div><div>There is possibility to specify a bounding box, so the easiest would be to just download a smaller extent of OSM.</div>
<div>I actually would like to avoid this, because now it's more convenient: if the OSM extent changes for the whole LiveDVD this also changes the sample data of pgRouting.</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
should we extract a smaller bbox just for use by the pgRouting<br>
install script? A sluggish demo is probably not what you wish<br>
to show off :)<br></blockquote><div><br></div><div>It's not sluggish even with a smaller extent. I find it rather hard to use for example with QGIS, when you want to load the whole OSM data. It is a bit too big for a LiveDVD in my opinion.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
here is a visual version of the city-wide bbox I used:<br>
<br>
<a href="http://www.openstreetmap.org/?box=yes&bbox=-105.2147,39.5506,-104.594,39.9139&mlat=39.74251&mlon=-104.9891" target="_blank">http://www.openstreetmap.org/?box=yes&bbox=-105.2147,39.5506,-104.594,39.9139&mlat=39.74251&mlon=-104.9891</a><br>
<br>
(zoom out one step to see the orange box easier; marker is the<br>
FOSS4G venue)<br>
<br></blockquote><div><br></div><div>Yes, I already made it smaller for the workshop, using just Denver downtown. Because it takes too long on weak notebooks to run the topology function.</div><div><br></div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
you can see from there that I've chopped off the northern and<br>
southern suburbs a bit already, and extended eastwards to get<br>
all of the airport covered.<br>
<br>
(I would at least like to cover the route from the airport to<br>
the conference hall)<br>
<br>
Suggestions welcome, especially from Denver locals.<br></blockquote><div><br></div><div>Yes, that's a good question. I was surprised that the data was so huge. </div><div>OSM data in Denver seems to contain a lot of features aside roads. </div>
<div><br></div><div>Well, I'm OK with either way: download a smaller extent for pgRouting only or decrease the size of the bbox in general.</div><div><br></div><div>Who else is using OSM data on the LiveDVD? Is the data used for some map rendering?</div>
<div>If it's only pgRouting making use of it, I'm not sure it's worth to have such a large extent. Probably the majority of users will not notice then.</div><div><br></div><div>Daniel</div></div><br clear="all">
<br>-- <br><span style="font-family:arial, sans-serif;font-size:13px;border-collapse:collapse">Georepublic UG & Georepublic Japan<br>
eMail: <a href="mailto:daniel.kastl@georepublic.de" style="color:rgb(66, 99, 171)" target="_blank">daniel.kastl@georepublic.de</a><br>Web: <a href="http://georepublic.de/" style="color:rgb(66, 99, 171)" target="_blank">http://georepublic.de</a></span><br>