New answers tagged osm2pgrouting
The function used in UpdateGeometrySRID is st_setsrid instead of st_transform. st_setsrid just sets the srid value without changing the coordinates. Since there is no function for looping tables to transform projection in PostGIS according to updateGeometrySRID function. I suggest you to write a script in python to execute it: Firstly execute to get the ...
You can check this application, it might be useful too: osm2po. It can create a routable network on OSM.
suppose that in your edge_table you have a column state_id SELECT * from pgr_dijkstra(' SELECT id, source, target, cost, reverse_cost from edge_table WHERE state_id = 16' <rest of you parameters>);
osm2pgrouting converts the osm data "as is". In osm segments are defined using sequence of node_ids so for example: (node_id, x, y) (1234, 2, 3.9999999) (5678, 2, 4) if a segment A, ends with 1234 and a segment B starts with 5678 there will be a gap 0.0000001 wide Validity of gaps: maybe if you are routing pedestrians you don't want that gap. maybe ...
For osm2pgrouting V2.1: length is length of the segment in degree units cost and reverse_cost is the length in degree units. (include the negative values for wrong way) length_m is in meters (there is no cost_m or reverse_cost_m) cost_s and reverse_cost_s is in time: seconds units (using the maxspeed value that is in km/hr transforming it to meters/second ...
Yes, pgRouting can do TSP: http://pgrouting.org/docs/1.x/tsp.html Yes, pgRouting uses OSM data - import an OSM extract using osm2pgrouting: http://pgrouting.org/docs/tools/osm2pgrouting.html As for turns - I haven't gotten into this specifically but there is the Turn Restriction Shortest Path that you should be able to incorporate: http://docs.pgrouting....
Top 50 recent answers are included