[pgrouting-dev] Free as in Freedom OSM converter

[Stephen Woodbridge]

Daniel,

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

We should probably open a ticket for this and assign it to 2.1.

-Steve

On 6/10/2013 11:24 PM, Daniel Kastl wrote:
>
>
>
> On Tue, Jun 11, 2013 at 12:10 PM, Stephen Mather
> <stephen at smathermather.com <mailto:stephen at smathermather.com>> wrote:
>
>     Hi Daniel,
>
>     I noticed the bigint issue-- I suppose this only became a problem a
>     few months back... .
>
>
> There is an issue for this:
> https://github.com/pgRouting/osm2pgrouting/issues/16
>
>
>     Re: 2.0, any sense of what API changes would affect osm2pgrouting?
>     I might poke under the hood to procrastinate from other work... .
>
>
> It should only affect function names, mainly pgr_createTopology:
> I think this file:
> https://github.com/pgRouting/osm2pgrouting/blob/master/src/Export2DB.cpp
>
> Daniel
>
>
>
>
>     Best,
>     Steve
>
>
>
>     On 06/10/2013 11:01 PM, Daniel Kastl wrote:
>>
>>
>>
>>     On Tue, Jun 11, 2013 at 11:11 AM, Stephen Mather
>>     <mather.stephen at gmail.com <mailto:mather.stephen at gmail.com>> wrote:
>>
>>         Hi All,
>>
>>         Is (for the moment) OSM2pgrouting a zombie project, or has
>>         there been work to port this for 2.0?  I'm using OSM2po at the
>>         moment, but thought I'd check in on status of free as in
>>         freedom alternatives.
>>
>>         Thanks,
>>         Best,
>>         Steve
>>
>>
>>
>>     Hi Steve,
>>
>>     osm2pgrouting needs some work, because
>>
>>      1. Not compatible with PostGIS 2.0 and the new pgRouting 2.0
>>      2. Cannot handle the new OSM bigint ID's
>>
>>     It was some years ago written by Daniel Wendt and then hosted
>>     together with pgRouting and like this found its way to Github.
>>     There is not much activity except some modifications over the
>>     years. But it has so far worked and just recently we have the
>>     issues as described before.
>>
>>     Currently pgRouting has priority. If someone wants to fix the
>>     issues with osm2pgrouting, then that's very welcome.
>>     There is a good alternative to process OSM data, named "osm2po".
>>     But it's not released under Open Source license, if that's OK for you.
>>
>>     Daniel
>>
>>
>>     --
>>     Georepublic UG & Georepublic Japan
>>     eMail: daniel.kastl at georepublic.de
>>     <mailto:daniel.kastl at georepublic.de>
>>     Web: http://georepublic.de <http://georepublic.de/>
>>
>>
>>     _______________________________________________
>>     pgrouting-dev mailing list
>>     pgrouting-dev at lists.osgeo.org  <mailto:pgrouting-dev at lists.osgeo.org>
>>     http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
>     _______________________________________________
>     pgrouting-dev mailing list
>     pgrouting-dev at lists.osgeo.org <mailto:pgrouting-dev at lists.osgeo.org>
>     http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
>
>
> --
> Georepublic UG & Georepublic Japan
> eMail: daniel.kastl at georepublic.de <mailto:daniel.kastl at georepublic.de>
> Web: http://georepublic.de <http://georepublic.de/>
>
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>