Wikidata:Property proposal/OSM node ID
OSM node ID edit
Originally proposed at Wikidata:Property proposal/Authority control
Not done
| Description | identifier for a node in OpenStreetMap |
|---|---|
| Represents | OpenStreetMap node (Q42375175) |
| Data type | External identifier |
| Domain | abstract geographic object (Q1503302) |
| Allowed values | 64-bit integer number ≥ 1 |
| Example 1 | Mattenengebrunnen (Q55411751) → 5344650914 |
| Example 2 | Anna-Seiler-Brunnen (Q559126) → 670560354 |
| Example 3 | Badgassbrunnen (Q55445914) → 558843441 |
| Example 4 | Schiffländtebrunnen (Q55446249) → 558838130 |
| Source | https://wiki.openstreetmap.org/wiki/Node |
| Planned use | The property will be used to reference geographical objects contained in OpenStreetMap. |
| Number of IDs in source | 4'300'000'000+ |
| Expected completeness | always incomplete (Q21873886) |
| Formatter URL | https://www.openstreetmap.org/node/$1 |
| See also | OpenStreetMap relation ID (P402), OpenStreetMap tag or key (P1282) |
Motivation
I was in the process of setting up an example item for Wikipedians planning to import geographical object data (fountains) from OpenStreetMap when I noticed that someone had already attempted to create this property in the entity space: OpenStreetMap node (Q42375175). It appears that this is one out of three main elements of OpenStreetMap (nodes, ways, relations). In addition, there are tags which describe the meaning of particular OSM elements. Wikidata presently has properties to point to OSM relations and to OSM tags, but none to point to nodes or ways. Beat Estermann (talk) 07:13, 10 July 2018 (UTC)
Discussion
Support David (talk) 15:02, 10 July 2018 (UTC)- Support AnBuKu (talk) 23:23, 10 July 2018 (UTC)
Oppose Geonick (talk) 23:45, 10 July 2018 (UTC)
Comment Use coordinate and ev. other properties to identify a real world object. Although many (third party) apps are using OSM ID's, it is strongly recommended to abstain using such an "ID", especially in projects like Wikidata. Even the OSM relation ID should never have passed it's proposal. // Use coordinate property in the first place, like e.g. also https://www.mediawiki.org/wiki/Help:Extension:Kartographer does. Discussion about OSM IDs are repeatedly coming up in OSM mailing lists, and led to the "Permanent ID" proposal, which is still in experimental stage, see https://wiki.openstreetmap.org/wiki/Overpass_API/Permanent_ID . -- Geonick
- Comment Members of the OSM community have pointed me to the fact that OSM node IDs are not stable (especially the practice of re-assigning deprecated IDs to other nodes seems problematic). As a consequence, they suggested that I withdraw this property proposal – an advise which I will follow as soon as a consensus has been reached on how to approach the mapping between Wikidata and OSM by other means. In my understanding, the consensus should also cover the handling of OpenStreetMap relation ID (P402) in Wikidata, as it does not make sense to handle the two in different ways. See also: Wikidata:OpenStreetMap --Beat Estermann (talk) 08:31, 11 July 2018 (UTC)
- Oppose For the reasons laid out by Michael and me, being: OSM IDs are not stable. --Das-g (talk) 09:58, 11 July 2018 (UTC)
- Comment There was some discussion last year about OpenStreetMap relation ID (P402) on property for deletion. The conclusion was that it's considered sufficiently stable to have as an external identifier property (see Wikidata:Requests_for_deletions/Archive/2017/Properties/1#OSM_relation_ID_(P402)). Not sure if some otherwise unknown OSM contributors stopped by mainly to promote their tool generate them instead.
For this proposal, we generally wouldn't have "external-ids" when they are not sufficiently stable. Instead one would use string-datatype. In this case, one would probably want to include date of retrieval and possibly name of the node in the statement.
--- Jura 13:53, 11 July 2018 (UTC) - Oppose for the reasons Beat himslef gives. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:14, 11 July 2018 (UTC)
- Support. Thierry Caro (talk) 15:50, 11 July 2018 (UTC)
- Oppose; not a stable external identifier. It's better to link the Wikidata item from the node, since Wikidata items aren't supposed to be deleted. Jc86035 (talk) 07:15, 17 July 2018 (UTC)
- Oppose per Jc86035. Mahir256 (talk) 13:18, 17 July 2018 (UTC)
- Oppose per Jc86035. We can have a one-sided link from OSM to Wikidata and query it with Overpass Turbo. NMaia (talk) 22:55, 25 July 2018 (UTC)