A Dijkstra based route solver daemon for lifomapserver GeoJson data.
Go to file
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.
2021-03-13 13:02:19 +01:00
misc Add systemd service file 2020-05-08 11:54:04 +02:00
sample-geojson Add example GeoJson for testing 2021-02-26 19:18:10 +01:00
src Do not use z-coordinate for speed on TRAINLINE or ACCESS 2021-03-13 13:02:19 +01:00
.gitignore Create project 2020-05-01 16:33:48 +02:00
CMakeLists.txt Add libm to CMakeLists 2020-05-02 17:13:06 +02:00
README.MD Remove pre-alpha warning 2020-05-05 20:49:33 +02:00

README.MD

lifo-dijkstraserv

A Dijkstra based route solver daemon for lifomapserver GeoJson data.