Property talk:P1708

From Wikidata
Jump to navigation Jump to search

Documentation

LfDS object ID
identifier for national heritage sites issued by the Landesamt für Denkmalpflege Sachsen
DescriptionObjekt-ID is used to identify cultural monuments in Saxony, Germany
Associated itemLandesamt für Denkmalpflege Sachsen (Q1420476)
Applicable "stated in" valueLfDS database (Q106232244)
Data typeExternal identifier
Corresponding templateTemplate:Kulturdenkmal Sachsen (Q105435498)
Template parameterID in de:Vorlage:Denkmalliste Sachsen Tabellenkopf
Domaincan be used for cultural heritage monument in Germany (Q11691318) (note: this should be moved to the property statements)
Allowed values
According to this template: 00000000 - 99999999
According to statements in the property:
0[89]\d{6}
When possible, data should only be stored as statements
ExampleAn der Läuterau 23 (Q18643398)09274762
Weißes Haus (Q77583012)09256599
Moritzburg Castle (Q156803)09284212
Sourcef. e. de:Liste der Kulturdenkmale in Seifhennersdorf (note: this information should be moved to a property statement; use property source website for the property (P1896))
Formatter URLhttps://denkmalliste.denkmalpflege.sachsen.de/CardoMap/Denkmalliste_Report.aspx?HIDA_Nr=$1
Tracking: usageCategory:Pages using Wikidata property P1708 (Q56117428)
Related to country Germany (Q183) (See 347 others) (Saxony (Q1202))
See alsoSaxony-Anhalt cultural heritage object ID (P9148), Monument Atlas Lower Saxony Objekt-ID (P7900)
Lists
Proposal discussionProposal discussion
Current uses
Total92,185
Main statement90,448 out of 90,253 (100% complete)98.1% of uses
Qualifier4<0.1% of uses
Reference1,7331.9% of uses
Search for values
[create Create a translatable help page (preferably in English) for this property to be included here]
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: Polish-Saxon Post Milestone Lengenfeld (Q84602291), Polish-Saxon Post Milestone Lengenfeld (Q49439683), Saxon post milestone Miltitz (Q49278144)
List of violations of this constraint: Database reports/Constraint violations/P1708#Unique value, SPARQL (every item), SPARQL (by value)
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/P1708#Single value, SPARQL
Format “0[89]\d{6}: 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/P1708#Format, SPARQL
Item “heritage designation (P1435): Items with this property should also have “heritage designation (P1435)”. (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/P1708#Item P1435, search, SPARQL
Item “country (P17): Germany (Q183): Items with this property should also have “country (P17): Germany (Q183)”. (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/P1708#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/P1708#Item P625, 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/P1708#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/P1708#Scope, SPARQL
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/P1708#Item P131, search, SPARQL
Conflicts with “subclass of (P279): 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/P1708#Conflicts with P279, search, SPARQL
Conflicts with “instance of (P31): person or organization (Q106559804): 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/P1708#Conflicts with P31, search, SPARQL

Map of all objects: https://w.wiki/47sT

online access[edit]

The IDs are not accessable online yet. Conny (talk) 18:58, 25 January 2015 (UTC).[reply]

Conny added a url, they are now accessible via a middlewarescript that i hacked together. Maybe the script that is currently living on one of my servers would be a possible candidate for a toolserver-script, if anyone wants to adopt this. --Ordercrazy (talk) 07:18, 14 September 2017 (UTC)[reply]

count[edit]

You can use statistics on the top of the page. Today there are 87381 items in Wikidata. Great, thanks to all helpers :) . Conny (talk) 11:37, 24 April 2018 (UTC).[reply]

It is possible to create a map via [1] . You can choose located in the administrative territorial entity (P131) to specify. Conny (talk) 14:42, 30 April 2018 (UTC).[reply]

lange Beschreibungen[edit]

Könnte man derart übernehmen und in die Kürze gehen. Gibt es Meinungen dazu? Grüße, Conny (talk) 12:04, 24 April 2018 (UTC).[reply]

Are there any ideas how to handle long descriptions in a seperate property and not in description-field? Thank you, Conny (talk) 18:50, 1 September 2018 (UTC).[reply]

Ich wende jetzt so an, wenn ein Property geeigneter ist, kann man später ersetzen. Conny (talk) 14:54, 10 September 2018 (UTC).[reply]

Is this working?[edit]

@Conny, Ordercrazy, Lutzto, Pigsonthewing, TMg: Hello. What's the correct formatter URL (P1630)? What's on offer right now seems to be broken. Thierry Caro (talk) 09:55, 16 August 2018 (UTC)[reply]

Asked also here. Regards, thank you, Conny (talk) 18:00, 16 August 2018 (UTC).[reply]
Looks like the second formatter URL posted DOES work, but it only supplies a PDF (map) of the location. The first one goes to something that was set up apparently by User:Ordercrazy - any hope of finding out what it actually did? For now I'd recommend just deleting the hochnebel.net formatter URL. ArthurPSmith (talk) 19:37, 16 August 2018 (UTC)[reply]
@ArthurPSmith: OK. I've removed the first one until further notice. But I don't have the remaining one working here. Thierry Caro (talk) 04:10, 17 August 2018 (UTC)[reply]
@Thierry Caro: It works for me for the example case listed, what happens when you try that? ArthurPSmith (talk) 15:32, 17 August 2018 (UTC)[reply]
@ArthurPSmith: OK. Thank you. It comes from my browser, which is Firefox. There's a security problem apparently. SEC_ERROR_CERT_SIGNATURE_ALGORITHM_DISABLED. Thierry Caro (talk) 15:35, 17 August 2018 (UTC)[reply]

✓ Works now with original Database link. Thank you, Conny (talk) 14:54, 10 September 2018 (UTC).[reply]

Please find [2]. Conny (talk) 06:38, 16 February 2019 (UTC).[reply]

It seems that cultural heritage monument in Germany (Q11691318) in Gemarkung (Q1499928) Dresden (Q1731) have no LfDS object ID (P1708). Conny (talk) 09:37, 19 February 2019 (UTC).[reply]

watchlist[edit]

Find a watchlist (edit) if there is deletion of P1708 (de: "Aussage entfernt: LfDS Objekt-ID (P1708)"). Conny (talk) 15:58, 29 April 2019 (UTC).[reply]

Ist not up to date and can not get updated at this time. Conny (talk) 20:13, 5 December 2019 (UTC).[reply]

Table for finding changes and new objects, updated manually [3] . Conny (talk) 21:26, 5 December 2019 (UTC).[reply]

Items without pictures[edit]

You can use this query (clustermap) to find them. Regards, Conny (talk) 14:49, 7 July 2019 (UTC).[reply]

Find gpx (zipped) for favorites to get markers of heritage sites without pictures (02/2020) in your OSMAnd~. Conny (talk) 18:36, 16 August 2020 (UTC).[reply]

@Alle, Michael_w: In dem Zusammenhang - sollte man Aussage Gesamtanlage lassen oder es in die einzelnen Teile aufgliedern oder beides (siehe beispielsweise Untere Hauptstraße 22; 22a (Q107427390)). Danke für Meinungen, Conny (talk) 13:42, 6 July 2021 (UTC). Conny (talk) 13:42, 6 July 2021 (UTC)[reply]

Hallo Conny, ich denke sobald die obere Behörde (im Nachweis) mehrere Teile zu einem Kulturdenkmal zusammenfasst, ist es eine Gesamtanlage. Aber ich bestehe da nicht drauf. Man muss es halt ordenltich begründen. --Michael w (talk) 14:13, 6 July 2021 (UTC)[reply]

former objects[edit]

How to handle former objects like Q96146787? Conny (talk) 19:53, 11 October 2021 (UTC)[reply]