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
i have some osm file
and i build one of them and start a osrm-routed service
and i got some nodes from a route request , and the result seems all right.
and then i use osmconvert to combine all osm to pbf, and then i build this pbf and start a osrm-routed service
and i got some strange nodes,
[1.021109170,1.437227874,5243432333480608,9252979683381472,8041568168893585,1.592471774,1.132044417,1.785935019,1.592109612,1187344792961079,687335956611697,1.749107293]
there are float node id in the array. and other ids is very big then my expect id.
i change the osrm-extract code :osrm-backend/include/extractor/packed_osm_ids.hpp i change the osrmid bit from 34 to 40
because my max node id is 4e11
so i want to know why the node id from annotation is so strange?
is something unexpected happened in osmconvert? or osrm-extract?
thanks for your reply~
osrm version is 5.27.1
The text was updated successfully, but these errors were encountered:
i have some osm file
and i build one of them and start a osrm-routed service
and i got some nodes from a route request , and the result seems all right.
and then i use osmconvert to combine all osm to pbf, and then i build this pbf and start a osrm-routed service
and i got some strange nodes,
[1.021109170,1.437227874,5243432333480608,9252979683381472,8041568168893585,1.592471774,1.132044417,1.785935019,1.592109612,1187344792961079,687335956611697,1.749107293]
there are float node id in the array. and other ids is very big then my expect id.
i change the osrm-extract code :osrm-backend/include/extractor/packed_osm_ids.hpp i change the osrmid bit from 34 to 40
because my max node id is 4e11
so i want to know why the node id from annotation is so strange?
is something unexpected happened in osmconvert? or osrm-extract?
thanks for your reply~
osrm version is 5.27.1
The text was updated successfully, but these errors were encountered: