Skip to content

node id is strange from annotation of route response #6594

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
aibear-huang opened this issue Apr 4, 2023 · 1 comment
Closed

node id is strange from annotation of route response #6594

aibear-huang opened this issue Apr 4, 2023 · 1 comment

Comments

@aibear-huang
Copy link

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

Copy link

This issue seems to be stale. It will be closed in 30 days if no further activity occurs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant