Permanent ID for OSM - Versionsgeschichte

WikiSysop: /* Overpass API Permanent ID */

2021-02-21T20:55:20Z

Overpass API Permanent ID

← Nächstältere Version		Version vom 21. Februar 2021, 20:55 Uhr
Zeile 81:		Zeile 81:

	Castle "Kyburg":		Castle "Kyburg":
	* Coordinates:		* Coordinates: geo:47.45836,8.74345
	* Properties: Wikidata item no. Q573643 ~~(note the minimal output without meta data in this Overpass query)~~.		* Properties: Wikidata item no. Q573643.
	* Overpass Query: <code>[out:custom];rel[wikidata=Q573643];out;</code>		* Overpass Query: <code>[out:custom];rel[wikidata=Q573643];out;</code> (note the minimal output without meta data)
			* Alternate Overpass Query: <code></code> (note the minimal output without meta data)
	* Overpass Permanent ID with JSON output (API): https://overpass-api.de/api/interpreter?data={{urlencode:[out:json];rel[wikidata=Q573643];out;}}		* Overpass Permanent ID with JSON output (API): https://overpass-api.de/api/interpreter?data={{urlencode:[out:json];rel[wikidata=Q573643];out;}}
	* Overpass Permanent ID with browse OSM.org: https://overpass-api.de/api/interpreter?data={{urlencode:[out:custom];rel[wikidata=Q573643];out;}}		* Overpass Permanent ID with browse OSM.org: https://overpass-api.de/api/interpreter?data={{urlencode:[out:custom];rel[wikidata=Q573643];out;}}

WikiSysop: /* Overpass API Permanent ID */

2021-02-21T20:46:36Z

Overpass API Permanent ID

WikiSysop: /* Overpass' Permanent ID */

2021-02-21T20:43:45Z

Overpass' Permanent ID

@@ Zeile 72: / Zeile 72: @@
    Warning: Don't shoehorn all OSM objects to relations just because Wikidata only knows OSM relation id (and no node/way id)!
-== Overpass' Permanent ID ==
+== Overpass API Permanent ID ==
-The Permanent_ID from Overpass is a solution where one expects to see the details (= "Link to Browse Object") and which relies purely on (non-geographic) tags: https://wiki.openstreetmap.org/wiki/Overpass_API/Permanent_ID
+The Permanent_ID from Overpass is a solution where one expects to see the details (= "Link to Browse Object") and which relies purely on (non-geographic) tags: https://wiki.openstreetmap.org/wiki/Overpass_API/Permanent_ID .
-Example for Castle Kyburg: '[out:custom];rel[wikidata=Q573643];out;' => [http://overpass-api.de/api/interpreter?data={{urlencode:[out:custom];rel[wikidata=Q573643];out;}} Q573643]
+Note that the user has to choose at least coordinates and an "around" parameter in Meters plus an identifying property (i.e. a key or a tag). Without this property e.g. OSM objects can't be disambiguated which are on different levels, like shops or rooms (see below).
 == Others ==

Stefan: /* Status of OSM id */

2020-11-03T15:41:42Z

Status of OSM id

← Nächstältere Version		Version vom 3. November 2020, 15:41 Uhr
Zeile 5:		Zeile 5:
	== Status of OSM id ==		== Status of OSM id ==

	One can use OSM id nevertheless (at own risk)! Many variants are known:		One can use OSM id nevertheless (at own risk)! Many variants are known in order to get a single unique identifier value. Some are of type string and others calculate a value of type big integer.

	~~'''As is with~~ OSM ~~id (bigint)''' and~~ a code for Node, Way, Relation e.g. in front (e.g. way/417258377).		String type based - using OSM ID number plus a code for Node, Way, Relation e.g. in front (e.g. way/417258377).
	Currently many applications depend on plain osm_id, eventually preceeded by node,way,relation (or N/W/R), like theses web applications (given example of "Denner Hombrechtikon" https://www.openstreetmap.org/node/6313169265):		Currently many applications depend on plain osm_id, eventually preceeded by node,way,relation (or N/W/R), like theses web applications (given example of "Denner Hombrechtikon" https://www.openstreetmap.org/node/6313169265):
	* Qwant Maps: Example Denner Hombrechtikon https://www.qwant.com/maps/place/osm:node:6313169265@Denner#map=18.00/47.2519793/8.7681836		* "Qwant Maps": Example Denner Hombrechtikon https://www.qwant.com/maps/place/osm:node:6313169265@Denner#map=18.00/47.2519793/8.7681836
	* Castle Map: Example Schloss Rapperswil https://castle-map.infs.ch/#46.805,8.205,8z,W417258377		* "Castle Map": Example Schloss Rapperswil https://castle-map.infs.ch/#46.805,8.205,8z,W417258377
	* Mapbox Vector Tiles: rely also on OSM id plus Node, Way, Relation: see below.

	Another adoption of osm_id with enhanced type space (length) properties is to convert it to a '''single big integer''': It's possible to encode the type (Node, Way, Relation) into the OSM id as a single integer (64 bit). (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.		Integer type based - using shifting on the three elements of OSM ID numbers:
			* "Overpass": Overpass uses an own schema to calculate an id of integer-type : https://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#By_area_.28area.29
			* "Mapbox Streets V7": Another adoption of osm_id with enhanced type space (length) properties is to convert it to a '''single big integer''': It's possible to encode the type (Node, Way, Relation) into the OSM id as a single integer (64 bit). (Source: Mapbox, see older Version V7 of Mapbox Streets [https://docs.mapbox.com/vector-tiles/reference/mapbox-streets-v7/#openstreetmap-ids]). Example: "Schloss Kyburg" is a relation with id 1169711, so it becomes 11697114. See also [https://github.com/openmaptiles/openmaptiles/issues/303#issuecomment-396654079 OpenMaptiles]

	for Nodes: osm_id = <node id> × 10 (eg. 123 → 1230),		for Nodes: osm_id = <node id> × 10 (eg. 123 → 1230),
	for Ways: osm_id = (<way id> × 10) + 1 (eg. 123 → 1231),		for Ways: osm_id = (<way id> × 10) + 1 (eg. 123 → 1231),
	for Relations: osm_id = (<relation id> × 10) + 4 (eg. 123 → 1234).		for Relations: osm_id = (<relation id> × 10) + 4 (eg. 123 → 1234).

			I, Stefan, prefer W417258377 for a string typed id, and Mapbox Streets V7 for number based.

	== Recommendations ==		== Recommendations ==

Stefan: /* OSM Permanent ID with geo URI */

2020-07-22T20:23:05Z

OSM Permanent ID with geo URI

← Nächstältere Version		Version vom 22. Juli 2020, 20:23 Uhr
Zeile 29:		Zeile 29:

	== OSM Permanent ID with geo URI ==		== OSM Permanent ID with geo URI ==

			This proposal is now also on the official OSM Wiki page: https://wiki.openstreetmap.org/wiki/Permanent_ID#OSM_Permanent_ID_with_geo_URI

	The goals and requirements of this new proposal are to get a compact human readable string as an OSM id.		The goals and requirements of this new proposal are to get a compact human readable string as an OSM id.

Stefan: /* OSM Permanent ID with geo URI */

2020-07-22T20:02:14Z

OSM Permanent ID with geo URI

← Nächstältere Version		Version vom 22. Juli 2020, 20:02 Uhr
Zeile 43:		Zeile 43:
	* osm_id an unsigned big integer ("digits").		* osm_id an unsigned big integer ("digits").
	* osm_version is an unsigned integer with a hash in front.		* osm_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 (multipolygon relation) ~~geometries~~, the coordinates taken ~~into account should be near~~ the center of the geometry.		* coordinates (lat/lon) are signed floats (always showing the +/- sign), with no more than 6 digits if possible. In case of a line (linestring) or an area (multipolygon relation) geometry, the coordinates either are taken from any node of the geometry, or calculated e.g. from the center of the geometry.

	The OSM Permanent ID is mainly numeric plus some fixed tokens and it has a variable length of a maximum of 42 chars.		The OSM Permanent ID is mainly numeric plus some fixed tokens and it has a variable length of a maximum of 42 chars.

Stefan: /* Recommendations */

2020-07-22T19:50:27Z

Recommendations

← Nächstältere Version		Version vom 22. Juli 2020, 19:50 Uhr
Zeile 26:		Zeile 26:
	# Wikidata QID with OSM backlink. Example 'Q573643'.		# Wikidata QID with OSM backlink. Example 'Q573643'.
	# Overpass Permanent ID with objekt-group-specific ID. Example '[out:custom];rel[wikidata=Q573643];out;'		# Overpass Permanent ID with objekt-group-specific ID. Example '[out:custom];rel[wikidata=Q573643];out;'
	# OSM Permanent ID with geo URI. Example 'geo:47.45835,8.74375 ?q=relation/1169711#5'.		# OSM Permanent ID with geo URI. Example 'geo:47.45835,8.74375?q=relation/1169711#5'.

	== OSM Permanent ID with geo URI ==		== OSM Permanent ID with geo URI ==

Stefan: /* OSM Permanent ID with geo URI */

2020-07-22T19:48:39Z

OSM Permanent ID with geo URI

← Nächstältere Version		Version vom 22. Juli 2020, 19:48 Uhr
Zeile 43:		Zeile 43:
	* osm_id an unsigned big integer ("digits").		* osm_id an unsigned big integer ("digits").
	* osm_version is an unsigned integer with a hash in front.		* osm_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 (multipolygon relation) 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 (multipolygon relation) geometries, the coordinates taken into account should be near the center of the geometry.

	The OSM Permanent ID is mainly numeric plus some fixed tokens and it has a variable length of a maximum of 42 chars.		The OSM Permanent ID is mainly numeric plus some fixed tokens and it has a variable length of a maximum of 42 chars.

Stefan: /* Recommendations */

2020-07-22T19:47:23Z

Recommendations

← Nächstältere Version		Version vom 22. Juli 2020, 19:47 Uhr
Zeile 26:		Zeile 26:
	# Wikidata QID with OSM backlink. Example 'Q573643'.		# Wikidata QID with OSM backlink. Example 'Q573643'.
	# Overpass Permanent ID with objekt-group-specific ID. Example '[out:custom];rel[wikidata=Q573643];out;'		# Overpass Permanent ID with objekt-group-specific ID. Example '[out:custom];rel[wikidata=Q573643];out;'
	# OSM Permanent ID with geo ~~URL~~. Example 'geo:47.45835,8.74375 ?q=relation/1169711#5'.		# OSM Permanent ID with geo URI. Example 'geo:47.45835,8.74375 ?q=relation/1169711#5'.

	== OSM Permanent ID with geo URI ==		== OSM Permanent ID with geo URI ==

Stefan: /* OSM Permanent ID with geo URL */

2020-07-22T19:47:08Z

OSM Permanent ID with geo URL

← Nächstältere Version		Version vom 22. Juli 2020, 19:47 Uhr
Zeile 28:		Zeile 28:
	# OSM Permanent ID with geo URL. Example 'geo:47.45835,8.74375 ?q=relation/1169711#5'.		# OSM Permanent ID with geo URL. Example 'geo:47.45835,8.74375 ?q=relation/1169711#5'.

	== OSM Permanent ID with geo ~~URL~~ ==		== OSM Permanent ID with geo URI ==

	The goals and requirements of this new proposal are to get a compact human readable string as an OSM id.		The goals and requirements of this new proposal are to get a compact human readable string as an OSM id.

← Nächstältere Version		Version vom 21. Februar 2021, 20:46 Uhr
Zeile 81:		Zeile 81:

	Castle "Kyburg":		Castle "Kyburg":
	* Coordinates:		* Coordinates:
	* Properties: Wikidata item no. Q573643		* Properties: Wikidata item no. Q573643 (note the minimal output without meta data in this Overpass query).
	* Overpass Query: '[out:custom];rel[wikidata=Q573643];out;'		* Overpass Query: <code>[out:custom];rel[wikidata=Q573643];out;</code>
	* Overpass Permanent ID with JSON output (API): https://overpass-api.de/api/interpreter?data={{urlencode:[out:json];rel[wikidata=Q573643];out;}}		* Overpass Permanent ID with JSON output (API): https://overpass-api.de/api/interpreter?data={{urlencode:[out:json];rel[wikidata=Q573643];out;}}
	* Overpass Permanent ID with browse OSM.org: https://overpass-api.de/api/interpreter?data={{urlencode:[out:custom];rel[wikidata=Q573643];out;}}		* Overpass Permanent ID with browse OSM.org: https://overpass-api.de/api/interpreter?data={{urlencode:[out:custom];rel[wikidata=Q573643];out;}}
Zeile 91:		Zeile 91:
	* Properties: type 'historic'		* Properties: type 'historic'
	* OSM.org: https://www.openstreetmap.org/way/289329862#map=19/47.30888/8.86706		* OSM.org: https://www.openstreetmap.org/way/289329862#map=19/47.30888/8.86706
	* Overpass Query: [out:json];nwr(around:5,47.30888,8.86706)[historic];out meta center;		* Overpass Query: <code>[out:json];nwr(around:5,47.30888,8.86706)[historic];out meta center;</code>
	* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A5%2C47.30888%2C8.86706%29%5Bhistoric%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A5%2C47.30888%2C8.86706%29%5Bhistoric%5D%3Bout%20meta%20center%3B
	* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A5%2C47.30888%2C8.86706%29%5Bhistoric%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A5%2C47.30888%2C8.86706%29%5Bhistoric%5D%3Bout%20meta%20center%3B
Zeile 99:		Zeile 99:
	* Properties amenity=restaurant (at ground level).		* Properties amenity=restaurant (at ground level).
	* OSM.org: https://www.openstreetmap.org/node/1706090806		* OSM.org: https://www.openstreetmap.org/node/1706090806
	* Overpass Query: [out:json];nwr(around:5,47.2229817,8.8163386)[amenity="restaurant"];out meta center;		* Overpass Query: <code>[out:json];nwr(around:5,47.2229817,8.8163386)[amenity="restaurant"];out meta center;</code>
	* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A5%2C47.2229817%2C8.8163386%29%5Bamenity%3D%22restaurant%22%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A5%2C47.2229817%2C8.8163386%29%5Bamenity%3D%22restaurant%22%5D%3Bout%20meta%20center%3B
	* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A5%2C47.2229817%2C8.8163386%29%5Bamenity%3D%22restaurant%22%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A5%2C47.2229817%2C8.8163386%29%5Bamenity%3D%22restaurant%22%5D%3Bout%20meta%20center%3B
Zeile 107:		Zeile 107:
	* Properties: room="auditorium" (at level 1, note that's at same coords as Mensa below).		* Properties: room="auditorium" (at level 1, note that's at same coords as Mensa below).
	* OSM.org: https://www.openstreetmap.org/way/903296474		* OSM.org: https://www.openstreetmap.org/way/903296474
	* Overpass Query: [out:json];nwr(around:10,47.2229817,8.8163386)[room="auditorium"];out meta center;		* Overpass Query: <code>[out:json];nwr(around:10,47.2229817,8.8163386)[room="auditorium"];out meta center;</code>
	* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A10%2C47.2229817%2C8.8163386%29%5Broom%3D%22auditorium%22%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A10%2C47.2229817%2C8.8163386%29%5Broom%3D%22auditorium%22%5D%3Bout%20meta%20center%3B
	* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A9%2C47.2229817%2C8.8163386%29%5Broom%3D%22auditorium%22%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A9%2C47.2229817%2C8.8163386%29%5Broom%3D%22auditorium%22%5D%3Bout%20meta%20center%3B
Zeile 116:		Zeile 116:
	* Properties: name~"Gebäude 4" (note that's still at same coords this time referring to an enclosing feature; around was increased again due to the larger object extension).		* Properties: name~"Gebäude 4" (note that's still at same coords this time referring to an enclosing feature; around was increased again due to the larger object extension).
	* OSM.org: https://www.openstreetmap.org/way/34754484		* OSM.org: https://www.openstreetmap.org/way/34754484
	* Overpass Query: [out:json];nwr(around:15,47.2229817,8.8163386)[name~"Gebäude 4"];out meta center;		* Overpass Query: <code>[out:json];nwr(around:15,47.2229817,8.8163386)[name~"Gebäude 4"];out meta center;</code>
	* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A15%2C47.2229817%2C8.8163386%29%5Bname~%22Geb%C3%A4ude%204%22%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with JSON output (API): https://overpass.osm.ch/api/interpreter?data=%5Bout%3Ajson%5D%3Bnwr%28around%3A15%2C47.2229817%2C8.8163386%29%5Bname~%22Geb%C3%A4ude%204%22%5D%3Bout%20meta%20center%3B
	* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A15%2C47.2229817%2C8.8163386%29%5Bname~%22Geb%C3%A4ude%204%22%5D%3Bout%20meta%20center%3B		* Overpass Permanent ID with browse OSM.org: https://overpass.osm.ch/api/interpreter?data=%5Bout%3Acustom%5D%3Bnwr%28around%3A15%2C47.2229817%2C8.8163386%29%5Bname~%22Geb%C3%A4ude%204%22%5D%3Bout%20meta%20center%3B