[Live-demo] [OSGeo] #1234: pgRouting: PostGIS database ways table bad import os OSM data

[OSGeo]

#1234: pgRouting: PostGIS database ways table bad import os OSM data
----------------------+-----------------------------------------------------
 Reporter:  hamish    |       Owner:  dkastl      
     Type:  defect    |      Status:  assigned    
 Priority:  critical  |   Milestone:  OSGeoLive7.0
Component:  LiveDVD   |    Keywords:  pgRouting   
----------------------+-----------------------------------------------------

Comment(by hamish):

 Hi,

 just an update on the situation -- Daniel suggested that it might be a
 32bit problem as it seems to test ok on 64bit ubuntu. OSM passed the 32bit
 integer limit for feature ID a couple months ago so that may be the
 culprit. The best thing would be to solve the bug in osm2pgrouting (if in
 fact that's where the bug is :), but for the live disc on a deadline or
 for a workshop with the 7.0 disc, perhaps some magic Postgres command to
 delete lines connected to the one problematic node could help, or have
 someone run the import on a 64bit ubuntu, dump the resulting DB to a file,
 then reimport the DB on the live disc as part of the build process.

 ?

 thanks,
 Hamish

-- 
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/1234#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.