Property talk:P402

From Wikidata
Jump to navigation Jump to search

Documentation

OpenStreetMap relation ID
identifier for a relation in OpenStreetMap
Descriptionthe ID of the relation of this place/object in OpenStreetMap (Q936). http://wiki.openstreetmap.org/wiki/Relation
RepresentsOpenStreetMap relation (Q100320716)
Applicable "stated in" valueOpenStreetMap (Q936)
Data typeExternal identifier
Corresponding templateTemplate:OSM relation (Q6177348)
Domaingeographical 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
ExampleBerlin (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)
Sourcehttps://www.openstreetmap.org
Formatter URLhttps://www.openstreetmap.org/relation/$1
Tracking: differencesCategory:OSM relation different from Wikidata (Q15088393)
Tracking: usageCategory:Pages using Wikidata property P402 (Q28003135)
Tracking: local yes, WD noCategory:OpenStreetMap Relation identifier not in Wikidata, but available on Wikipedia (Q14947065)
See alsoOpenStreetMap 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 discussionProposal discussion
Current uses
Total425,348
Main statement410,292 out of 11,501,272 (4% complete)96.5% of uses
Qualifier19<0.1% of uses
Reference15,0373.5% 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.)

OpenStreetMap (Q936)–related properties
Property
Open proposals
  • None at present

Discussion[edit]


Notability[edit]

Following the example of OSM Name Suggestion Index ID (P8253), should this be instance of (P31) Wikidata property for an identifier that suggests notability (Q62589316)? Bovlb (talk) 13:04, 3 October 2022 (UTC)[reply]

This property clearly doesn't suggest notability since OSM is user-generated. Dexxor (talk) 08:14, 5 October 2022 (UTC)[reply]
So? Seems that we need to comment "notability" into all in-use properties, see Google's ID, Property_talk:P2671, with no notability comment. --Krauss (talk) 20:27, 18 February 2023 (UTC)[reply]

New Formatter URL to expand scope[edit]

The scope of the current Property:P1630 (Formatter URL) is "OpenStreetMap relation", so, it is impossible to use P402 (OpenStreetMap relation ID) with points or addresses.

For example Q41796695 is represented by the node https://www.openstreetmap.org/node/4913452739

With a consistent PURL redirector we can use all 3 kinds of OSM identifiers: node, way and relation (abbreviated by the "n", "w" or "r" letters).

Allowed values will be expanded to [nrw]?[1-9]\d{0,8}, where [nrw]? is the new optional 1-letter prefix.

Examples using https://osm.codes/$1 for each entity type:

The change from the current Formatter URL to this new (more widely usable) URL, causes no impact (the default with no letter is the relation). And it is also a solution for many constraint violations.

PS1: an alternative Formatter URL would be https://nominatim.openstreetmap.org/ui/details.html?osmid=$1. Problems:

PS2: suggestion to Nominatim community, enhance with an osmid_mix resolution, as "mix osmtype+osmid".

--Krauss (talk) 20:18, 18 February 2023 (UTC)[reply]

Retrieved from "https://www.wikidata.org/w/index.php?title=Property_talk:P402&oldid=2149056553"