<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jun 11, 2013 at 1:13 PM, Stephen Woodbridge <span dir="ltr"><<a href="mailto:woodbri@swoodbridge.com" target="_blank">woodbri@swoodbridge.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Daniel,<br>
<br>
I'm not sure all of the pgrouting code supports bigint, in fact, I'm pretty sure most of it does not. We would need to change all id variables to be declared "long int" in the C code and<br>
<br>
We should probably open a ticket for this and assign it to 2.1.<br></blockquote><div><br></div><div><br></div><div style>Hi Steve,</div><div style><br></div><div style>I think the problem is not so much pgRouting as parsing OSM data, and the current implementation cannot handle 32bit ID's.</div>
<div style>There is lot of OSM data we don't want to use and which gets filtered by osm2pgrouting (ie. POI's polygons, etc), but in OSM it has an ID.</div><div style><br></div><div style>It makes no sense to use original OSM ID's, but it's good to keep them as a reference.</div>
<div style>OSM network data also needs to be noded, so it's anyhow necessary to create own ID's and I doubt we need bigint for that ... at least not for the near future, I hope ;-)</div><div style><br></div><div style>
Daniel</div><div><br></div><div><br></div><div><br></div><div><br></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>
-Steve<div class="im"><br>
<br>
On 6/10/2013 11:24 PM, Daniel Kastl wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<br>
<br>
On Tue, Jun 11, 2013 at 12:10 PM, Stephen Mather<br></div><div class="im">
<<a href="mailto:stephen@smathermather.com" target="_blank">stephen@smathermather.com</a> <mailto:<a href="mailto:stephen@smathermather.com" target="_blank">stephen@smathermather.<u></u>com</a>>> wrote:<br>
<br>
Hi Daniel,<br>
<br>
I noticed the bigint issue-- I suppose this only became a problem a<br>
few months back... .<br>
<br>
<br>
There is an issue for this:<br>
<a href="https://github.com/pgRouting/osm2pgrouting/issues/16" target="_blank">https://github.com/pgRouting/<u></u>osm2pgrouting/issues/16</a><br>
<br>
<br>
Re: 2.0, any sense of what API changes would affect osm2pgrouting?<br>
I might poke under the hood to procrastinate from other work... .<br>
<br>
<br>
It should only affect function names, mainly pgr_createTopology:<br>
I think this file:<br>
<a href="https://github.com/pgRouting/osm2pgrouting/blob/master/src/Export2DB.cpp" target="_blank">https://github.com/pgRouting/<u></u>osm2pgrouting/blob/master/src/<u></u>Export2DB.cpp</a><br>
<br>
Daniel<br>
<br>
<br>
<br>
<br>
Best,<br>
Steve<br>
<br>
<br>
<br>
On 06/10/2013 11:01 PM, Daniel Kastl wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">
<br>
<br>
<br>
On Tue, Jun 11, 2013 at 11:11 AM, Stephen Mather<br></div><div class="im">
<<a href="mailto:mather.stephen@gmail.com" target="_blank">mather.stephen@gmail.com</a> <mailto:<a href="mailto:mather.stephen@gmail.com" target="_blank">mather.stephen@gmail.<u></u>com</a>>> wrote:<br>
<br>
Hi All,<br>
<br>
Is (for the moment) OSM2pgrouting a zombie project, or has<br>
there been work to port this for 2.0? I'm using OSM2po at the<br>
moment, but thought I'd check in on status of free as in<br>
freedom alternatives.<br>
<br>
Thanks,<br>
Best,<br>
Steve<br>
<br>
<br>
<br>
Hi Steve,<br>
<br>
osm2pgrouting needs some work, because<br>
<br></div>
1. Not compatible with PostGIS 2.0 and the new pgRouting 2.0<br>
2. Cannot handle the new OSM bigint ID's<div class="im"><br>
<br>
It was some years ago written by Daniel Wendt and then hosted<br>
together with pgRouting and like this found its way to Github.<br>
There is not much activity except some modifications over the<br>
years. But it has so far worked and just recently we have the<br>
issues as described before.<br>
<br>
Currently pgRouting has priority. If someone wants to fix the<br>
issues with osm2pgrouting, then that's very welcome.<br>
There is a good alternative to process OSM data, named "osm2po".<br>
But it's not released under Open Source license, if that's OK for you.<br>
<br>
Daniel<br>
<br>
<br>
--<br>
Georepublic UG & Georepublic Japan<br>
eMail: <a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@georepublic.de</a><br></div>
<mailto:<a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@<u></u>georepublic.de</a>><br>
Web: <a href="http://georepublic.de" target="_blank">http://georepublic.de</a> <<a href="http://georepublic.de/" target="_blank">http://georepublic.de/</a>><br>
<br>
<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a> <mailto:<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.<u></u>osgeo.org</a>><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</blockquote>
<br>
<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a> <mailto:<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.<u></u>osgeo.org</a>><div class="im">
<br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
<br>
<br>
<br>
<br>
--<br>
Georepublic UG & Georepublic Japan<br></div>
eMail: <a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@georepublic.de</a> <mailto:<a href="mailto:daniel.kastl@georepublic.de" target="_blank">daniel.kastl@<u></u>georepublic.de</a>><br>
Web: <a href="http://georepublic.de" target="_blank">http://georepublic.de</a> <<a href="http://georepublic.de/" target="_blank">http://georepublic.de/</a>><div class="im"><br>
<br>
<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
<br>
</div></blockquote><div class="HOEnZb"><div class="h5">
<br>
______________________________<u></u>_________________<br>
pgrouting-dev mailing list<br>
<a href="mailto:pgrouting-dev@lists.osgeo.org" target="_blank">pgrouting-dev@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/pgrouting-dev" target="_blank">http://lists.osgeo.org/<u></u>mailman/listinfo/pgrouting-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></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>
</div></div>