2,106 reputation
136
bio website osm2po.de
location Hamburg, Germany
age
visits member for 2 years, 8 months
seen Mar 20 at 18:10

Mar
20
answered osm2po network access
Mar
11
comment Getting all possible directions from a geo point in osm2po
Then it's a misunderstanding. I asked if it is sufficient to find crossings (see above). To find the closest edge, your first approach was already correct. node.snap(...) returns the needed information, namely exactly one edge (forward). To find the reverse edge (if exists) call graph.findReverseEdge(...) as you did. In some rare cases a vertex is closer than an edge. Therefore call node.isOnVertex() and/or node.isOnEdge() before and fallback to graph.findOutgoingEdges(node.getId()) if necessary.
Mar
5
comment osm2po cycle routes
No, not interesting ... it's daily OSM-nuisance. Would like to know which tags are missing or even new ... or self invented or beta or whatever.
Mar
3
comment osm2po cycle routes
Relations cannot be handled as easy as ways. They totally differ in how to interpret them. Think of restrictions, routes or even boundaries. The only thing you can do is to overwrite some standard behavior in the osm2po-API to transport your special interpretation into the routing. The validate()-Method is the meeting point where all the things get to together. Here you can influence osm2po's default behavior.
Mar
3
comment osm2po cycle routes
Which version do you use? Try 5.0.0. Did you pass the params on the commandline? If so, remove blanks.
Mar
2
answered osm2po cycle routes
Feb
26
answered Getting all possible directions from a geo point in osm2po
Feb
25
comment Getting all possible directions from a geo point in osm2po
are you looking for outgoing edges of real crossings only or rather random, even virtual locations somewhere on arbitrary edges?
Feb
24
comment Routing with osm2po - starting from middle of the street
In order to get the id call tp.getId()
Feb
24
comment Routing with osm2po - starting from middle of the street
Ok. Here is quick diff: first call OverlayNode tp = new OverlayNode(lat, lon); and then tp.snap(graph, null)). This replaces TouchPoint.create(...) . Finally insert the snapped point into the graph with overlayGraph.insertNode(tp); which returns an id you can pass to the router.
Feb
24
comment Routing with osm2po - starting from middle of the street
Please open a new thread, so I can give an official answer instead of a hidden comment.
Jan
30
revised Use osm2po to extract additional tags
edited body
Jan
30
comment Use osm2po to extract additional tags
Either modify the osm2po.config (hopefully not that one inside the jar) or overwrite parameters on the commandline. For more complex deviations you can indeed use a parameter to point to another config. config=path/to/special.config You can also hold different configs in one by using wayTogResolver.prefix
Jan
30
revised Use osm2po to extract additional tags
deleted 1 character in body
Jan
30
answered Use osm2po to extract additional tags
Jan
30
answered osm2po street IDs
Jan
7
comment Removing pseudo nodes from PostGIS database using ST_ModEdgeHeal()?
By the way, my eu_2po.log reports more than 25 Million vertices. This will produce about 40x25M = 1 Billion Routes.
Jan
7
comment Removing pseudo nodes from PostGIS database using ST_ModEdgeHeal()?
As I understood you correctly you are looking for a Many-To-One query. Is this correct? Is it sufficient for you to omit intermediate vertices and only take real crossings into account? If so, you are looking for a Dijkstra which is able to route over reversed edges and that keeps results after one full traversal.
Dec
5
comment Split OSM highways at vertice
Are you familiar with Java? If not, try to convert the created road segments with PostGIS means.
Dec
3
answered Split OSM highways at vertice