Comments on LoudHush Blog: Using pgRouting on an OSM database imported by osm...

Yep, this flag is -s (--slim)

2012-01-17T09:47:43.818+02:00

Yep, this flag is -s (--slim)

1/ If I remember correctly there's a flag to o...

2012-01-17T09:02:16.224+02:00

1/ If I remember correctly there's a flag to osm2pgsql that tells it to create the planet_osm_ways table.

2/ I think using OSM node ids should work but

a/ I've never tried retrieving the nodes that belong to a given street. I do remember there's a precision difference in between lat/long values in planet_osm_point vs. planet_osm_line so you can't select by geometry.

b/ assign_vertex_id also includes logic for tolerance - i.e. it will connect nodes that are within a given distance.

2012-01-17T09:01:37.657+02:00

This comment has been removed by the author.

Is it neccessary to use assign_vertex_id if we alr...

2012-01-17T07:41:29.727+02:00

Is it neccessary to use assign_vertex_id if we already have target and source IDs filled from OSM node IDs?

Thanks for this so useful article! But I've fa...

2012-01-16T20:38:34.007+02:00

Thanks for this so useful article! But I've faced with the following problem. After import osm data into database - table planet_osm_ways doesn't exist (PostGIS 2.0 + Postgresql 9.1.2 + osm2pgsql SVN version 0.80.0). I've tried to modify your original function for my case. You can find it here: http://pastie.org/3196541