Property talk:P8988
identifier for a point of interest in Mapy.cz
(addr|area|base|cada|coun|dist|muni|quar|regi|stre|ward|osm|pubt|firm|traf)&id=[1-9][0-9]{0,9}
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P8988#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P8988#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Scope, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Entity types
List of violations of this constraint: Database reports/Constraint violations/P8988#Type Q618123, Q820477, Q131734, Q3152824, Q178561, Q15642541, Q860861, Q1190554, Q811534, Q108696, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Item P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Item P131, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Item P17, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P8988#Item P625, SPARQL
|
Style of external ID
[edit]I am personally against of this style of ids ("muni&id=1", "regi&id=1", "base&id=1933331"). There is mix of things: part of URI vs numeric identifier. I am proposing to split this identifier to multiple identifiers with proper numeric id. Skim (talk) 15:56, 30 December 2020 (UTC)
- The discussion (for which you were notified) decided otherwise... Vojtěch Dostál (talk) 07:28, 2 February 2021 (UTC)
@ArthurPSmith, Vojtěch Dostál, Skim, Jklamo, Mike Peel: This solution would be elegant if it worked. Unfortunately, there are some technical problems with this format. E.g. for Road III/2565 (Q112046119), the correct link should be:
https://mapy.cz/zakladni?source=area&id=932114
However, the Wikidata page generates the link:
https://wikidata-externalid-url.toolforge.org/?p=8988&url_prefix=https://mapy.cz/zakladni?source=&id=area%26id%3D932114
where is "source=&id=area" instead of "source=area". Nevertheless, the link works correctly and the resulting link is correct:
https://mapy.cz/zakladni?source=area&id=932114
Commons:Template:Wikidata Infobox uses this URL format pattern, but it generates
https://wikidata-externalid-url.toolforge.org/?p=8988&url_prefix=https://mapy.cz/zakladni?source=area&id=932114
The problem with double "&id=" doesn't occur here, but this string at its correct place is not decoded and it returns:
https://mapy.cz/zakladni?source=area932114
on the resulted page and the link doesn't work. The string "&id=" is somehow lost.
Before I tried to correct the long URL format pattern, the resulting link was:
https://mapy.cz/zakladni?source=932114
and didn't work as well. The whole string "area&id=" disappeared.
Is somebody able to fix this problem? --ŠJů (talk) 01:21, 2 June 2022 (UTC)
@ArthurPSmith, Vojtěch Dostál, Skim, Jklamo, Mike Peel: I don't know if anyone was trying to fix something, but shortly after my comment, the Wikidata link also stopped working. --ŠJů (talk) 16:31, 6 June 2022 (UTC)
- @ŠJů Could it be your edit? https://www.wikidata.org/w/index.php?title=Property%3AP8988&type=revision&diff=1652409421&oldid=1651667713 Vojtěch Dostál (talk) 16:37, 6 June 2022 (UTC)
- @Vojtěch Dostál: This my edit caused the change in behavior I described above (the wrong link from the infobox https://mapy.cz/zakladni?source=932114 changed to wrong link https://mapy.cz/zakladni?source=area932114. The link from Wikidata then worked for about next day, but it is possible that my change was reflected in it and disrupted the function later. --ŠJů (talk) 16:50, 6 June 2022 (UTC)
- I reverted that my edit, but https://wikidata-externalid-url.toolforge.org responds to changes in the formatting pattern with a delay. --ŠJů (talk) 16:56, 6 June 2022 (UTC)
As far as I can tell, it was working right in the first place, at least here? On the Wikidata Infobox site, I think it's urldecoding where it shouldn't do, so it's passing multiple "&id=" parameters where it shouldn't. But the Infobox is undergoing a big rewrite at the moment, so solving this there needs to wait until that process is further along. Thanks. Mike Peel (talk) 20:08, 6 June 2022 (UTC)
@ArthurPSmith, Vojtěch Dostál, Skim, Jklamo, Mike Peel: The problem with erroneous encoding of two-parameter URL adresses is further discussed at Commons:Template talk:Wikidata Infobox#Mapy.cz ID etc. (April – July 2022). --ŠJů (talk) 15:33, 29 July 2022 (UTC)
- @ŠJů Actually rather here: :commons:Template_talk:Wikidata_Infobox#Mapy.cz_ID_etc. Vojtěch Dostál (talk) 18:16, 29 July 2022 (UTC)
Katastr
[edit]Přidal jsem identifikátor cada pro katastrální území. Nově je klikatelné při zapnutí vrstvy katastrálních dat. Otázka, jestli nějak ta data nespárovat s kú. na WD, nicméně pak bude třeba nějak ošetřit duplicity s identifikátorem area. — Draceane talkcontrib. 11:20, 25 April 2024 (UTC)
- Příklad: https://mapy.cz/zakladni?source=cada&id=7212. — Draceane talkcontrib. 11:21, 25 April 2024 (UTC)
subject type constraint
[edit]Subject type constraint makes no sense with point of interest. Die Eigenschaftseinschränkung „Typ“ macht meiner Meinung nach keinen Sinn bei den Poi's von Mapy.cz. Lutzto (talk) 13:56, 23 June 2024 (UTC)
- Czech Republic-related properties
- All Properties
- Properties with external-id-datatype
- Properties used on 100000+ items
- Properties with format constraints
- Properties with unique value constraints
- Properties with single value constraints
- Properties with scope constraints
- Properties with entity type constraints
- Properties with constraints on type
- Properties with constraints on items using them
- Properties with conflicts with constraints