Skip to content
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

Increase PackedOSMIDs size to 34 bits #6020

Merged
merged 1 commit into from
Apr 24, 2021

Conversation

mjjbell
Copy link
Member

@mjjbell mjjbell commented Apr 24, 2021

Issue

OSM node 2^33 was created in early April 2021. This and all subsequently created IDs will be overflowing OSRM node storage which only supports 33 bit IDs.
Bump the number of bits to 34 to double node ID capacity. This is a breaking change to the data format as it alters the layout of .osrm.nbg_nodes.

Impact

Increases size of file .osrm.nbg_nodes and its in-memory representation by ~1%
E.g. germany-latest.osrm.nbg_nodes increases from 379,732,480 to 383,647,232 bytes.

Tasklist

Requirements / Relations

Fixes #6016

OSM node 2^33 was created in early April 2021. This and all
subsequently created IDs will be overflowing OSRM node storage
which only support 33 bit IDs.
Bump the number of bits to 34 to double node ID capacity. This
is a breaking change to the data format as it alters the layout
of .osrm.nbg_nodes.
@mjjbell mjjbell force-pushed the mbell/packed_34_bit branch from 2a0d6f5 to 7f7f8c9 Compare April 24, 2021 20:27
@mjjbell mjjbell merged commit 50f5a75 into Project-OSRM:master Apr 24, 2021
@mjjbell mjjbell deleted the mbell/packed_34_bit branch April 24, 2021 22:41
@Lv200
Copy link

Lv200 commented May 7, 2021

I also met the problem several days ago, and I changed the bit parameter in my branch.
And I thought 34 is just enough for now, maybe the bit parameter should be set larger for future, 45 can be used for a long time.

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

Successfully merging this pull request may close these issues.

wrong node number in route
3 participants