Property talk:P402
Documentation
identifier for a relation in OpenStreetMap
List of violations of this constraint: Database reports/Constraint violations/P402#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P402#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P402#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P402#Entity types
List of violations of this constraint: Database reports/Constraint violations/P402#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P402#Conflicts with P31, 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 edit
Archives | |||
---|---|---|---|
|
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)
- This property clearly doesn't suggest notability since OSM is user-generated. Dexxor (talk) 08:14, 5 October 2022 (UTC)
- 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)
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:
- Q171617 is a city-polygon, represented by the OSM-relation 298227. http://osm.codes/r298227 and http://osm.codes/298227 redirects to it.
- Q41796695 is a address-point, represented by the OSM-node 4913452739. http://osm.codes/n4913452739 redirects to it.
- Q82941 is a building-line, represented by the OSM-way 419922808. http://osm.codes/w419922808 redirects to it.
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:
- The default resolution is not a relation, for example
r298227
is not redirected at https://nominatim.openstreetmap.org/ui/details.html?osmid=298227 - Need for change from "2 steps" to "1 step", see for example osmid=r298227 or osmid=w419922808.
PS2: suggestion to Nominatim community, enhance with an osmid_mix
resolution, as "mix osmtype+osmid".