You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[info] Using script /home/osrm/5.11/profiles/foot_distance.lua
[info] Input file: bayern-latest.osm.pbf
[info] Profile: foot_distance.lua
[info] Threads: 8
[info] Parsing in progress..
[info] Using profile api version 2
[info] input file generated by osmium/1.5.1
[info] timestamp: 2017-08-30T20:43:02Z
[info] Using profile api version 2
[info] Using profile api version 2
[info] Using profile api version 2
[info] Using profile api version 2
[info] Using profile api version 2
[info] Using profile api version 2
[info] Using profile api version 2
terminate called after throwing an instance of 'osrm::util::exception'
[info] Parsing finished after 34.008 seconds
[info] Raw input contains 49249849 nodes, 7190400 ways, and 0 relations
what(): There are no edges remaining after parsing.src/extractor/extractor.cpp:335
Aborted
Exactly the same (data, osrm-extract-call) with original foot.lua works fine as well as the same change for car profile.
Looks like the same bug for car profile described at #3638 - unfortunately i have no clue what to do to resolve my problem. What i have to change where to get shortest routes for foot?
Kindly regards.
The text was updated successfully, but these errors were encountered:
@dooley the problem is in missing WayHandlers.weights handler. It will be fixed in 5.13 release via #4514 or you can cherry-pick c3eee08 into your local 5.11 branch.
I tried to change foot.lua to use shortest ways. Changes:
osrm-extract with that new profile aborted with:
Exactly the same (data, osrm-extract-call) with original foot.lua works fine as well as the same change for car profile.
Looks like the same bug for car profile described at #3638 - unfortunately i have no clue what to do to resolve my problem. What i have to change where to get shortest routes for foot?
Kindly regards.
The text was updated successfully, but these errors were encountered: