[pgrouting-dev] Free as in Freedom OSM converter

[Daniel Kastl]

Hi Steve,

Today I have created a new "develop" branch [1] for osm2pgrouting, merged
some pull requests, fixed conflicts and did some small changes.
If nothing went wrong, then the "develop" branch should now support 32bit
ID's and pgRouting 2.0 function names.

[1]  https://github.com/pgRouting/osm2pgrouting/tree/develop

I just made one simple test with Bangladesh data and got 2 suspicious
messages:

Classes table created
Adding tag types and classes to database...
ERROR:  duplicate key value violates unique constraint "classes_pkey"
DETAIL:  Key (id)=(100) already exists.
CONTEXT:  COPY classes, line 28: "100 1 unclassified 1 50"

There is a new PRIMARY KEY added for the "id" attribute, so it will just
fail to insert the same class id twice.
Not sure why this happens, but it seems no big issue. Before there was no
unique constraint at all.

And in the end it reported

NOTICE:  0 out of 27919 edges processed
NOTICE:  10000 out of 27919 edges processed
NOTICE:  20000 out of 27919 edges processed
Create Topology failed:
#########################
size of streets: 13123
size of splitted ways : 27919

But the network table actually looked OK, so maybe it's just the error
message that is wrong.
I need to look at this some time later.

If you have a time to test and make sure that it works with 32bit ID's,
that would be great.

Daniel



On Tue, Jun 11, 2013 at 12:10 PM, Stephen Mather
<stephen at smathermather.com>wrote:

>  Hi Daniel,
>
> I noticed the bigint issue-- I suppose this only became a problem a few
> months back... .
>
> Re: 2.0, any sense of what API changes would affect osm2pgrouting?  I
> might poke under the hood to procrastinate from other work... .
>
> 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
> > 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
> Web: http://georepublic.de
>
>
> _______________________________________________
> pgrouting-dev mailing listpgrouting-dev at lists.osgeo.orghttp://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>
>
> _______________________________________________
> pgrouting-dev mailing list
> pgrouting-dev at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/pgrouting-dev
>
>


-- 
Georepublic UG & Georepublic Japan
eMail: daniel.kastl at georepublic.de
Web: http://georepublic.de
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/pgrouting-dev/attachments/20130613/7640dc51/attachment.html>