Markus Koch
e01245cb98
Do not use z-coordinate for speed on TRAINLINE or ACCESS
Using the z-coordinate as is is a bad idea. When intersecting, a new node will be generated. What z-coord should it be? This node can now be part of two distinct types with different meanings for it. So we need to implement weight as a path argument. This commit hardcodes the speed for trains and access pathways as a temporary workaround.
lifo-dijkstraserv
A Dijkstra based route solver daemon for lifomapserver GeoJson data.
Description
Languages
C
98%
CMake
2%