Property talk:P10689

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

List of violations of this constraint: Database reports/Constraint violations/P10689#Format, hourly updated report, SPARQL

Scope is as main value (Q54828448), as qualifier (Q54828449), 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/P10689#Scope, SPARQL

Allowed entity types are Wikibase item (Q29934200), Wikibase MediaInfo (Q59712033): 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/P10689#Entity types

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).
List of violations of this constraint: Database reports/Constraint violations/P10689#Unique value, SPARQL (every item), SPARQL (by value)

Single best value: this property generally contains a single value. If there are several, one would have preferred rank (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/P10689#single best value, SPARQL

Type “geographical feature (Q618123), geographic entity (Q27096213), hotel (Q27686), work of art (Q838948), educational institution (Q2385804), combined facility (Q56352703)”: item must contain property “instance of (P31), subclass of (P279)” with classes “geographical feature (Q618123), geographic entity (Q27096213), hotel (Q27686), work of art (Q838948), educational institution (Q2385804), combined facility (Q56352703)” or their subclasses (defined using subclass of (P279)). (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: Black Lives Matter (Q96081169)
List of violations of this constraint: Database reports/Constraint violations/P10689#Type Q618123, Q27096213, Q27686, Q838948, Q2385804, Q56352703, SPARQL

Format “(?!relation).*”: value must be formatted using this pattern (PCRE syntax). (Help)

List of violations of this constraint: Database reports/Constraint violations/P10689#Format, hourly updated report, SPARQL

Item “located in the administrative territorial entity (P131)”: Items with this property should also have “located in the administrative territorial entity (P131)”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: oceanic trench (Q119253)
List of violations of this constraint: Database reports/Constraint violations/P10689#Item P131, search, SPARQL

Item “country (P17)”: Items with this property should also have “country (P17)”. (Help)

Exceptions are possible as rare values may exist. Exceptions can be specified using exception to constraint (P2303). Known exceptions: oceanic trench (Q119253)
List of violations of this constraint: Database reports/Constraint violations/P10689#Item P17, search, SPARQL

Item “coordinate location (P625)”: Items with this property should also have “coordinate location (P625)”. (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/P10689#Item P625, SPARQL

Item “instance of (P31)”: Items with this property should also have “instance of (P31)”. (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/P10689#Item P31, search, SPARQL

This property is being used by: sk:Šablóna:Geobox it:Template:Area protetta sv:Mall:Insjöfakta Sverige, sv:Mall:Testmall/Dengamlapotatisen/Insjöfakta Sverige test vec:Modeło:Infobox de Àrea protexesta Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Pattern ^way/([1-9]\d*)$ will be automatically replaced to \1. Testing: TODO list

Pattern ^node/([1-9]\d*)$ will be automatically replaced to \1 and moved to OpenStreetMap node ID (P11693) property. Testing: TODO list

https://wiki.openstreetmap.org/wiki/Template:Hardcoded_IDs --Nw520 (talk) 18:35, 25 April 2022 (UTC)[reply]

Is there a reason not to allow adding the OSM object property as structured data to a wikimedia commons item? --Middle river exports (talk) 02:01, 5 May 2022 (UTC)[reply]

@Middle river exports: No, I do not think so. Do you have an example of such Wikimedia Commons item? Pamputt (talk) 06:31, 5 May 2022 (UTC)[reply]

Sure. I linked the node of the intersection this image depicts for example https://commons.wikimedia.org/wiki/File:Indiana_East_1200_South--East_900_North_at_Adams_County_-_Jay_County_border,_United_States.jpg Middle river exports (talk) 06:43, 5 May 2022 (UTC)[reply]

Well I've gone ahead and added Wikibase MediaInfo which should do it Middle river exports (talk) 22:23, 7 May 2022 (UTC)[reply]

Multiple objects should be allowed. Wikidata objects are not always precise. For example the object Amada can describe the temple of Amada or the world heritage site (which has a larger area). It makes sometimes sense to reference different objects with different roles (here temple building or world heritage site). You can also mix this property with a relation, so there is no protection against ambiguity. Sinuhe20 (talk) 20:14, 19 July 2022 (UTC)[reply]

Better to fix Wikidata and remove the conflation of two entities into one item. GeoGQL (talk) 13:48, 15 March 2023 (UTC)[reply]

Nodes, ways, and relations are OpenStreetMap elements, not OpenStreetMap objects. Maybe the English description of this property and associated translation in other languages should be modified in order not to generate confusion (more details on OSM Wiki). Dcapillae (talk) 13:13, 16 December 2022 (UTC)[reply]

I agree. So9q (talk) 15:41, 16 December 2022 (UTC)[reply]

Renamed the property in German and English. --Nw520 (talk) 12:44, 21 December 2022 (UTC)[reply]

The property is designed to store

1. an ID of an OpenStreetMap element not the element
2. a node or way ID, not a relation ID example bug

Please rename to "OpenStreetMap node or way ID" and in usage instruction tell that the prefix should be used. GeoGQL (talk) 12:24, 15 March 2023 (UTC)[reply]

Done for label, not done for usage instruction, but changed description instead. GeoGQL (talk) 08:41, 16 March 2023 (UTC)[reply]

Why would that be so? E.g. streets in OSM can be split into several ways, why should one of these be the single best? GeoGQL (talk) 13:29, 15 March 2023 (UTC)[reply]

Maybe it is correct for nodes, but for ways it seems not to be correct. See Wikidata:Property proposal/OpenStreetMap node ID which allows to have that constraint only for nodes. GeoGQL (talk) 06:36, 16 March 2023 (UTC)[reply]

@GeoGQL: If a feature on OSM is made up of multiple ways then they should be grouped together in a relation, and that relation then linked to the relevant Wikidata item. It's only if there's a single way that this property should be used. (At least, this is my understanding.) Sam Wilson 05:30, 2 August 2023 (UTC)[reply]

Wikidata:Property proposal/OpenStreetMap node ID - a proposal to move the node IDs to a seperate property.

1. 1:1 mapping: each of the three sets of IDs for the three OpenStreetMap element types is mapped to exactly one of three Wikidata properties
2. storing without prefix: reduce storage space, make data comparison and sorting of results easier
3. allow single-value constraint for nodes, which for ways isn't feasible
4. allow easier querying

GeoGQL (talk) 06:35, 16 March 2023 (UTC)[reply]

When I click on most links I just get an error message, what is going on? See Mount Olivet Cemetery (Q21586308) for example. RAN (talk) 16:28, 27 March 2023 (UTC)[reply]

@Richard Arthur Norton (1958- ): This property was recently repurposed as a by-product of the creation of OpenStreetMap node ID (P11693) and values need to be migrated. --Nw520 (talk) 19:46, 27 March 2023 (UTC)[reply]

In that case the value has been changed 2023-03-25 02:35 but the old URL formatter is still applied, it was changed to the new pattern 2023-03-25 19:44. A bug in the software. GeoGQL (talk) 12:01, 29 March 2023 (UTC)[reply]

@Richard Arthur Norton (1958- ): each value is now changed to be numeric only and those converted before the formatter change seem to have been refreshed, so hopefully each issue is fixed. [1]. GeoGQL (talk) 17:42, 31 March 2023 (UTC)[reply]

changed by Lucarpedia / swedish Wikipedia presentation

1. please explain this swedish translation? Is that your own thoughts or is it used at other places
2. when you change name other people will have difficulties finding the property please add the old value as alias....
3. this new label is 26 characters long --> I feel best practice is not using long names as this will impact reports and search queries
4. better start with OSM or Open Street Map --> then type ahead will show all properties reláted to OSM...

- Salgo60 (talk) 08:29, 25 September 2023 (UTC)[reply]

1. A way in OSM is called a "sträcka" on the OSM website with Swedish locale. As an example, way 4421145 is described as "Sträcka: Tillfällavägen (4421145)".
2. The old name "OSM way" is generic and is searchable in other languages, but I will add it as an alias as it is probably good practice to do so.
3. I agree, but is there a Wikidata guideline you can point me at supporting the use of abbreviations in the labels?
4. Reasonable, I'll look into that.

Lucarpedia (talk) 10:39, 26 September 2023 (UTC)[reply]

Lucarpedia guess no guidelines but lesson learned is that long names easy makes a mess in the UI - Salgo60 (talk) 07:46, 29 September 2023 (UTC)[reply]

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:P402/P10689 to display the shape and not a empty maplink frame) 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 P402 page. Dengamlapotatisen (talk) 09:50, 18 August 2024 (UTC)[reply]

Is it allowed for a bot to automatically fill this attributes on Wikidata item Qxxx based on the presence of wikidata:Qxxx on an OSM object? This page indicates that it is forbidden to import OSM data on Wikidata: https://wiki.openstreetmap.org/wiki/Wikidata but it seems unclear to me whether this also applies on numerical ids of OSM objects... Thanks in advance. Best regards. Peter17 (talk) 16:13, 14 October 2024 (UTC)[reply]

check https://www.wikidata.org/wiki/Property_talk:P402#use_of_automatic_tool

i requested a feature to have the reverse linking process as well as already happen in osm GiovanniPen (talk) 12:17, 26 November 2024 (UTC)[reply]