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.

Sign up for GitHub

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

Jump to bottom

Geobuf Format: IDs #33

Closed
joto opened this issue Jan 19, 2015 · 4 comments
Closed

Geobuf Format: IDs #33

joto opened this issue Jan 19, 2015 · 4 comments

Comments

@joto
Copy link

joto commented Jan 19, 2015

IDs can be of type string or sint32. Whats the rational behind this? Can we support 64bit IDs? I think in this day and age, 32 bit its are too limiting and OSM data would need 64bit IDs.
@mourner
Copy link
Member

mourner commented Jan 19, 2015

Sure, sint64 sounds fine.

@artemp
Copy link

artemp commented Jan 20, 2015

+1 64-bit integers

@mourner - do we need to support both numeric and string IDs? It's not clear from the spec.

@mourner
Copy link
Member

mourner commented Jan 20, 2015

@artemp integer id's are pretty common and it's done for better compression in such cases. So we either encode integer or string id.

@brendan-ward
Copy link

@artemp some of this is covered in comments from @sgillies in #27

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@mourner @artemp @joto @brendan-ward