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

By year by demand, reusing ID #1

Open
ppKrauss opened this issue Oct 26, 2018 · 0 comments
Open

By year by demand, reusing ID #1

ppKrauss opened this issue Oct 26, 2018 · 0 comments

Comments

@ppKrauss
Copy link
Contributor

Final decision? ... And change lookup.csv first suggestion...

It is "by demand" because only will be registered when in use by a curated stable dump.

It is "reused" because we can reuse the usual element's ID (osm_id)... So, the perma_id is an alphanumeric string with the syntax:

Perma_ID ::= Year OsmType OsmID
Year     ::= [0-9]+           /* year of the "standard */
OsmType  ::= 'r' | 'w' | 'n'  /* relation or way or node */
OsmID    ::= [0-9]+           /* full positive integer in use at that year */

Notes: Year not changes, only when OSM changes all infrastructure, so perhaps each 5 or 10 years... Can be a counter of "perma_id version", and changes only for newer geometries (thereare are a track-of-original mechanism based on hashes or other attributes). OsmID can be translated to base36 lower (to be compressed), and OsmType to upper case.

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

No branches or pull requests

1 participant