Documentation

OpenStreetMap relation ID
identifier for a relation in OpenStreetMap

Description

the ID of the relation of this place/object in OpenStreetMap (Q936). http://wiki.openstreetmap.org/wiki/Relation

Represents

OpenStreetMap relation (Q100320716), OpenStreetMap (Q936)

Applicable "stated in" value

OpenStreetMap (Q936)

Has quality

numeric identifier (Q93868746)

Data type

External identifier

Corresponding template

Template:OSM relation (Q6177348)

Domain

geographical feature: streets, countries, states, buildings, places, everything with geocoordinates (note: this should be moved to the property statements)

Allowed values

[1-9][0-9]{0,9}

Usage notes

本項用來對應開放街圖中的關聯物件。填入關係識別碼，可連結至開放街圖的對應頁面。
Buat relasi di OpenStreetMap yang menunjukkan suatu titik, garis, atau area. Lalu tambahkan kode relasinya disini

Example

Berlin (Q64) → 62422 (RDF)
Lizard Head Wilderness (Q6660504) → 396588 (RDF)
Washington County (Q501559) → 270624 (RDF)
Sudirman Road (Q12487040) → 13000761 (RDF)
Busan Asiad Main Stadium (Q482589) → 10952708 (RDF)
Vrelo Bosne (Q108146920) → 28784587 (RDF)

Source

https://www.openstreetmap.org

Formatter URL

https://www.openstreetmap.org/relation/$1

Tracking: differences

Category:OSM relation different from Wikidata (Q15088393)

Tracking: usage

Category:Pages using Wikidata property P402 (Q28003135)

Tracking: local yes, WD no

Category:OpenStreetMap Relation identifier not in Wikidata, but available on Wikipedia (Q14947065)

See also

OpenStreetMap tag or key (P1282), OpenStreetMap zoom level (P6592), URL (P2699), OpenHistoricalMap relation ID (P8424), OpenStreetMap way ID (P10689), OpenStreetMap numeric user ID (P8754), OpenStreetMap node ID (P11693)

Lists

Proposal discussion

Current uses

Total	472,057
Main statement	456,144 out of 12,604,763 (4% complete)	96.6% of uses
Qualifier	32	<0.1% of uses
Reference	15,881	3.4% of uses

Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

Single value: this property generally contains a single value. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P402#Single value, SPARQL

Distinct values: this property likely contains a value that is different from all other items. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: U.S. Route 29 in the District of Columbia (Q718261), U.S. Route 29 in Maryland (Q2214556)
List of violations of this constraint: Database reports/Constraint violations/P402#Unique value, SPARQL (every item), SPARQL (by value)

Format “[1-9]\d{0,9}”: value must be formatted using this pattern (PCRE syntax). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P402#Format, SPARQL

Allowed entity types are Wikibase item (Q29934200): the property may only be used on a certain entity type (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P402#Entity types

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P402#Scope, SPARQL

Conflicts with “instance of (P31): Wikimedia disambiguation page (Q4167410), Wikimedia category (Q4167836), Wikimedia list article (Q13406463)”: this property must not be used with the listed properties and values. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303).
List of violations of this constraint: Database reports/Constraint violations/P402#Conflicts with P31, SPARQL

Conflicts with “instance of (P31): Wikimedia project page (Q14204246)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P402#Conflicts with P31, hourly updated report, search, SPARQL

Conflicts with “instance of (P31): Wikimedia template (Q11266439)”: this property must not be used with the listed properties and values. (Help)

List of violations of this constraint: Database reports/Constraint violations/P402#Conflicts with P31, hourly updated report, search, SPARQL

This property is being used by:

Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Discussion

P402 mediwiki synchronization with kartographer tags

Is there any documente use of tools like OpenRefine to synchronize these tags with what Kartographer have?

Is there any talks of automating the import from the Kartopgrapher server copy of all the OSM (Tools such as Maplink needs both a wikidata QID on the OSM data and someone to fill in the Property:P10689/P402 to display the shape and not to display the maplink frame if there is not a value in those properties as defualt behaviour) This could also work to mitigate problems when the OSM way or relation ID have changed for a object which could happen. The only thing you really need is the OSM folks to put in the wikidata tag and we could look at the Kartographer copy for tags without these Properties in the wikidata entries.

Also posted a dicussion topic on the P10689 page. Dengamlapotatisen (talk) 09:50, 18 August 2024 (UTC)[reply]

use of automatic tool

https://github.com/EdwardBetts/osm-wikidata/issues/669
https://osm.wikidata.link/
imho is good to link automatically also on wikidata, not only putting the wikidata tag on osm; thats why i opened the request (to ask/suggest a reverse feature functionality) GiovanniPen (talk) 12:15, 26 November 2024 (UTC)[reply]