<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br>
><br>
>> pgrouting 181 MB<br>
><br>
> a little ouch, but if it compresses well, probably not a big<br>
> worry.<br>
><br></blockquote><div><br></div><div>Sorry, I have missed this in this thread.</div><div>Astrid told me about your discussion in IRC.</div><div><br></div><div>I think it's not pgRouting library but either the workshop sample data and/or the pgRouting Quickstart sample data.</div>
<div>With Barcelona it was no issue, so I guess that it's because the Denver OSM data bounding box contains so much more data than Barcelona. I already experienced, that it takes so long to load the network in QGIS. It's just because it's so huge.</div>
<div><br></div><div>I will review the workshop until Saturday and see if I can free some more space there. </div><div><br></div><div>For pgRouting Qucikstart I have to either download a smaller bbox of Denver area for pgRouting, or we could make the area smaller in general, and it will also decrease the size of pgRouting.</div>
<div><br></div><div>Daniel</div><div><br></div><div><br></div><div><br></div><div> </div></div>-- <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>