Tag Info

New answers tagged

1

Putting extra nodes to the static graph is no good idea. One reason is that the graph may be shared by parallel routing request. Another is that the graph will grow with each request. One solution is to overlay the graph with virtual edges and nodes and to write a router which is able to distiguish between them. This is the technique used by osm2po. ...


3

I had the same problem few weeks ago and solved it by manually drawing lines from nearest node. I don't know if it's one and only resolution, it's quite hard and tricky but its working quite good. Firstly I'm selecting start edge, stop edge and result (path from routing) into record variables, then doing some post-procesing: Cut the result road if it's ...


1

After analyzing my dataset more with QGIS I think I've found most of the differences. Using osm2pgrouting with mapconfig_for_cars.xml still includes vertices related to pedestrian interaction, whereas osm2po with wtr.finalMask = car does not. Here is a view of OSM of an intersection with crosswalks... Here is a view of my dataset (which is roads ...


2

In case you haven't tried it yet, the pgRouting Workshop is always a good place to get started. When you used osm2po to convert your OSM data, then source and target attributes are already there and ready to use. Sometimes the vertices table, that contains all source and target ID's, is useful to find the nearest vertex from a geographic point. The osm2po ...



Top 50 recent answers are included