Permanent ID - Versionsgeschichte

Stefan: Weiterleitung nach Permanent ID for OSM erstellt

2019-06-19T20:04:04Z

Weiterleitung nach Permanent ID for OSM erstellt

← Nächstältere Version		Version vom 19. Juni 2019, 20:04 Uhr
Zeile 1:		Zeile 1:
	~~This is an '''unofficial proposal for a "permanent ID" (osm_pid) for OpenStreetMap ([[OSM]])'''.~~		#REDIRECT [[Permanent_ID_for_OSM]]

	~~See https://wiki.openstreetmap.org/wiki/Permanent_ID for a more official state of discussions.~~

	~~The goal is to get an opaque fixed length ASCII string. And that are the design considerations:~~

	* The OSM id alone is not stable enough (as probably most agree); and it can represent many concepts (and that's by design in OSM).
	* The version no. of the object is needed which makes clear which tags are (or have been) referred to.
	* Coordinates are needed, because a change of the way and area geometries does not increment the version number.

	~~So a stable Permanent ID could have the following form (variable length to a maximum of currently 35 chars):~~

	~~[N\|W\|R]<osm_id>~~#~~<version>~~[~~+\|-]<lon>~~[~~+\|-~~]~~<lat>~~

	~~where:~~
	* N,W,R stands for Node, Way, or Relation.
	* osm_id an unsigned big integer ("digits").
	* version is an unsigned integer with a hash in front.
	* coordinates (lat/lon) are signed floats (always showing the +/- sign), with a maximum of 6 digits. In case of a line (linestring) or an area/relation (polygon) geometries the coordinates taken into account are the lat/lon minimum of the geometry.

	~~Example: "Schloss Kyburg" (Castle Kyburg) has relation 1169711, version #5 at coordinates 47.4584, 8.74343 which becomes following Permanent ID:~~

	~~osm_pid = R1169711#5+47.4584+8.74343~~

	~~Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if an object has been changed (thus having another Permanent ID).~~

	NOTE: Encoding OSM id with type (Node, Way, Relation) as integer (64 bit): osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]~~). Example: "Schloss Kyburg" is a relation with id 1169711, so it becomes 11697114.~~

Stefan am 19. Juni 2019 um 20:02 Uhr

2019-06-19T20:02:16Z

← Nächstältere Version		Version vom 19. Juni 2019, 20:02 Uhr
Zeile 1:		Zeile 1:
	This is an '''unofficial proposal for a "permanent ID" (osm_pid) for OpenStreetMap ([[OSM]])'''.		This is an '''unofficial proposal for a "permanent ID" (osm_pid) for OpenStreetMap ([[OSM]])'''.

	See https://wiki.openstreetmap.org/wiki/Permanent_ID for a more official state of discussions.		See https://wiki.openstreetmap.org/wiki/Permanent_ID for a more official state of discussions.

Stefan am 1. Mai 2019 um 22:55 Uhr

2019-05-01T22:55:23Z

← Nächstältere Version		Version vom 1. Mai 2019, 22:55 Uhr
Zeile 9:		Zeile 9:
	* Coordinates are needed, because a change of the way and area geometries does not increment the version number.		* Coordinates are needed, because a change of the way and area geometries does not increment the version number.

	So a stable Permanent ID could have the following form (~~which leads~~ to a ~~fixed length string~~ of 35 chars ~~in total~~):		So a stable Permanent ID could have the following form (variable length to a maximum of currently 35 chars):

	[N\|W\|R]<osm_id>#<version>[+\|-]<lon>[+\|-]<lat>		[N\|W\|R]<osm_id>#<version>[+\|-]<lon>[+\|-]<lat>
Zeile 15:		Zeile 15:
	where:		where:
	* N,W,R stands for Node, Way, or Relation.		* N,W,R stands for Node, Way, or Relation.
	* osm_id ~~ann~~ unsigned big integer ("digits").		* osm_id an unsigned big integer ("digits").
	* version is an unsigned integer with a hash in front.		* version is an unsigned integer with a hash in front.
	* coordinates (lat/lon) are signed floats (always showing the +/- sign), with a maximum of 6 digits. In case of a line (linestring) or an area/relation (polygon) geometries the coordinates taken into account are the lat/lon minimum of the geometry.		* coordinates (lat/lon) are signed floats (always showing the +/- sign), with a maximum of 6 digits. In case of a line (linestring) or an area/relation (polygon) geometries the coordinates taken into account are the lat/lon minimum of the geometry.

Stefan am 1. Mai 2019 um 22:53 Uhr

2019-05-01T22:53:23Z

← Nächstältere Version		Version vom 1. Mai 2019, 22:53 Uhr
Zeile 25:		Zeile 25:
	Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if an object has been changed (thus having another Permanent ID).		Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if an object has been changed (thus having another Permanent ID).

	~~== Alternative Encodings ==~~		NOTE: Encoding OSM id with type (Node, Way, Relation) as integer (64 bit): osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]). Example: "Schloss Kyburg" is a relation with id 1169711, so it becomes 11697114.

	~~Same "triple" values as above (osm type/id, version and coordinates) but with different encodings~~:

	~~Use~~ OSM ~~ID number (big integer 64 bit) together~~ with ~~OSM~~ type (Node, Way, Relation)
	* either with preceeding N,W,R as string.
	* or as integer (32 bit) ~~with following formula~~: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).

	~~Additionally use these values for validation, separated e.g. by a "#":~~
	* version (small integer 16 bit)
	* Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.

	Example: "Schloss Kyburg" ~~having~~ relation id 1169711 ~~with version 5 at coordinates 47.4584~~, ~~8.74343 (see also above)~~ becomes ~~following Instant ID:~~

	~~osm_pid2 =~~ 11697114~~#5#474584000#87434300 => 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300~~

Stefan am 30. April 2019 um 18:24 Uhr

2019-04-30T18:24:37Z

← Nächstältere Version		Version vom 30. April 2019, 18:24 Uhr
Zeile 15:		Zeile 15:
	where:		where:
	* N,W,R stands for Node, Way, or Relation.		* N,W,R stands for Node, Way, or Relation.
	* osm_id ~~is left-padded with zeros to get 10 chars~~ ("digits").		* osm_id ann unsigned big integer ("digits").
	* version is ~~4 digits left padded~~ with ~~zeros~~.		* version is an unsigned integer with a hash in front.
	* coordinates ~~have 5 fixed decimal places~~ (lat ~~is 2 and~~ lon ~~is 3 digits wide, both~~ are signed ~~and left~~-~~padded~~ with ~~zeros~~).		* coordinates (lat/lon) are signed floats (always showing the +/- sign), with a maximum of 6 digits. In case of a line (linestring) or an area/relation (polygon) geometries the coordinates taken into account are the lat/lon minimum of the geometry.

	Example: "Schloss Kyburg" (Castle Kyburg) has relation 1169711, version #5 at coordinates 47.4584, 8.74343 which becomes following Permanent ID:		Example: "Schloss Kyburg" (Castle Kyburg) has relation 1169711, version #5 at coordinates 47.4584, 8.74343 which becomes following Permanent ID:

	osm_pid = ~~R0001169711~~#~~0005~~+47.~~45840~~+~~008~~.74343		osm_pid = R1169711#5+47.4584+8.74343

	Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if a an object has been changed (thus having another Permanent ID).		Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if an object has been changed (thus having another Permanent ID).

	== Alternative Encodings ==		== Alternative Encodings ==

Stefan: /* Alternative Encodings */

2019-04-11T20:46:09Z

Alternative Encodings

← Nächstältere Version		Version vom 11. April 2019, 20:46 Uhr
Zeile 33:		Zeile 33:
	* or as integer (32 bit) with following formula: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).		* or as integer (32 bit) with following formula: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).

	Additionally ~~(optionally)~~ for validation, separated e.g. by a "#":		Additionally use these values for validation, separated e.g. by a "#":
	* ~~use and store~~ version (small integer 16 bit)		* version (small integer 16 bit)
	* ~~use and store~~ Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.		* Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.

	Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:		Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:

	osm_pid2 = 11697114#5#474584000#87434300 => 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300		osm_pid2 = 11697114#5#474584000#87434300 => 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300

Stefan: /* Alternative Encodings */

2019-04-11T20:32:49Z

Alternative Encodings

← Nächstältere Version		Version vom 11. April 2019, 20:32 Uhr
Zeile 33:		Zeile 33:
	* or as integer (32 bit) with following formula: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).		* or as integer (32 bit) with following formula: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).

	Additionally (optionally) for validation, separated e.g. by a ~~dash~~ "-":		Additionally (optionally) for validation, separated e.g. by a "#":
	* use and store version (small integer 16 bit)		* use and store version (small integer 16 bit)
	* use and store Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.		* use and store Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.
Zeile 39:		Zeile 39:
	Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:		Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:

	osm_pid2 = 11697114-5-474584000-87434300 => 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300		osm_pid2 = 11697114#5#474584000#87434300 => 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300

Stefan: /* Alternative Encodings */

2019-04-11T20:31:40Z

Alternative Encodings

← Nächstältere Version		Version vom 11. April 2019, 20:31 Uhr
Zeile 33:		Zeile 33:
	* or as integer (32 bit) with following formula: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).		* or as integer (32 bit) with following formula: osm_id = <node id> × 10 (eg. 123 → 1230), osm_id = (<way id> × 10) + 1 (eg. 123 → 1231), osm_id (<relation id> × 10) + 4 (eg. 123 → 1234). (Source: Mapbox, see [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v8/#openstreetmap-ids]).

	Additionally (optionally) for validation:		Additionally (optionally) for validation, separated e.g. by a dash "-":
	* use and store version (small integer 16 bit)		* use and store version (small integer 16 bit)
	* use and store Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.		* use and store Latitude and Longitude (as centroid from line and polygons) as signed integers (32 bit) with a scale factor of 1e7, so an integer Latitude of -412870685 equates to -41.2870685 (as the original OSM database schema in "Rails port"), in order to retain a stable reference.
Zeile 39:		Zeile 39:
	Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:		Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:

	osm_pid2 = 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300		osm_pid2 = 11697114-5-474584000-87434300 => 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300

Stefan am 11. April 2019 um 20:29 Uhr

2019-04-11T20:29:49Z

← Nächstältere Version		Version vom 11. April 2019, 20:29 Uhr
Zeile 24:		Zeile 24:

	Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if a an object has been changed (thus having another Permanent ID).		Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if a an object has been changed (thus having another Permanent ID).


	== Alternative Encodings ==		== Alternative Encodings ==

Stefan am 11. April 2019 um 20:29 Uhr

2019-04-11T20:29:31Z

← Nächstältere Version		Version vom 11. April 2019, 20:29 Uhr
Zeile 25:		Zeile 25:
	Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if a an object has been changed (thus having another Permanent ID).		Service: In order to be really useful, a service should be implemented, which returns most recent Permanent ID even if a an object has been changed (thus having another Permanent ID).

	~~== Instant ID ==~~

	~~For all those services which can't wait until a Permanent ID solution has been adopted by the OpenStreetMap software stack~~ and ~~community, following '''Instant ID (osm_iid)''' (an integer triple~~) ~~is being proposed~~:		== Alternative Encodings ==

			Same "triple" values as above (osm type/id, version and coordinates) but with different encodings:

	Use OSM ID number (big integer 64 bit) together with OSM type (Node, Way, Relation)		Use OSM ID number (big integer 64 bit) together with OSM type (Node, Way, Relation)
Zeile 39:		Zeile 40:
	Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:		Example: "Schloss Kyburg" having relation id 1169711 with version 5 at coordinates 47.4584, 8.74343 (see also above) becomes following Instant ID:

	~~osm_iid~~ = 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300		osm_pid2 = 11697114 plus osm_version = 5, osm_lat = 474584000, osm_lon = 87434300