Property talk:P3257
Documentation
identifier of place, in the official Queensland Government gazetteer
Associated item | Department of Natural Resources, Mines and Energy (Q5260420) | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Applicable "stated in" value | Queensland place name Gazetteer (Q64381451) | ||||||||||||
Has quality | numeric identifier (Q93868746) | ||||||||||||
Data type | External identifier | ||||||||||||
Template parameter | |id= in en:Template:Cite QPN | ||||||||||||
Domain | According to this template:
Places in Q36074
When possible, data should only be stored as statements | ||||||||||||
Allowed values | \d+ | ||||||||||||
Example | Kenmore (Q6389457) → 41505 Pimpama (Q14935543) → 46080 County of Rochedale (Q14935393) → 28612 | ||||||||||||
Source | https://www.resources.qld.gov.au/qld/environment/land/place-names/search | ||||||||||||
Formatter URL | https://gisservices.information.qld.gov.au/arcgis/rest/services/Location/QldPlaceNames/MapServer/0/query?where=REF_NO%3D$1&outFields=REF_NO%2CPLACE_NAME%2CALT_NAME%2CTYPE%2CDESCRIPTION%2CSTATUS%2CCURRENCY%2CGAZETTED_DATE%2CGAZETTE_PAGE%2CPLAN_NO%2CMODIFIED_DATE%2CLGA_NAME%2CCOMMENTS%2CLONGITUDE%2CLATITUDE%2CLONGITUDE_DD%2CLATITUDE_DD%2CORIGIN%2CHISTORY%2CLINKS | ||||||||||||
Robot and gadget jobs | import from en.Wikipedia Probably needs a bot, as most instances are in references, so not found by HarvestTemplates | ||||||||||||
Related to country | Australia (Q408) (See 200 others) (Queensland (Q36074)) | ||||||||||||
Lists |
| ||||||||||||
Proposal discussion | Proposal discussion | ||||||||||||
Current uses |
| ||||||||||||
Search for values |
List of violations of this constraint: Database reports/Constraint violations/P3257#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P3257#Item P31, search, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3257#Type Q3257686, Q618123, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P3257#Entity types
List of violations of this constraint: Database reports/Constraint violations/P3257#Scope, SPARQL
in Queensland (Q36074) (Help)
Violations query:
SELECT ?item { ?item wdt:P3257 []. FILTER NOT EXISTS { ?item wdt:P131 wd:Q36074 } FILTER NOT EXISTS { ?item wdt:P131* wd:Q36074 } FILTER NOT EXISTS { ?item wdt:P31 wd:Q4022 } }
List of this constraint violations: Database reports/Complex constraint violations/P3257#In Queensland
Constraint violations
editHaving had the constraint violations Wikidata:Database reports/Constraint violations/P3257 drawn to my attention, I can only say that there is some misunderstanding here about the Qld Place Name identifier. It does uniquely identifies a database entry in the Queensland Place Names database as a particular type of "place". Most towns, e.g. Goondiwindi will have two entries as standard, one as a populated place (town) which is defined by a centre point and the other which is a locality which is bounded and has a centroid. If I write the Goondiwindi article on Wikipedia, I need to refer to both entries. Furthermore Goondiwindi is also the name of a railway station (within both the town and locality of Goondiwindi) and of a parish (which are now historic concepts here in Queensland). An article on Goondiwindi may refer to these too or to a related place e.g. the Macintyre River which flows past it.
However, it seems someone has scrapped the *citation* template Template:Cite QPN from en.WP articles and populated the values it found in that template use into Wikidata, resulting in Wikidata entries with multiple of these IDs, which appears to be the cause of all these constraint violations. An article about a place in Wikipedia will use the template to "define" itself (noting above that the definition of a town may involve two entries) as well as to "refer" to information about related (but different) places, such as a railway station in a town or a river passing through a town, or the mountain that gives the town its name, etc. It may be disambiguating between places with similar names and so on. So the scraping of the data without understanding it properly has resulted in a lot of rubbish going into Wikidata, leading to these constraint violation reports.
The other thing to be aware of is these database entries get replaced if there is a small change in boundaries etc, so the old definitions are retained and the new definition published with a new identifier. Unfortunately the redesign of the the web interface no longer lets the user see the old entries as it once did (apparently it confused some people), which is very frustrating.
So, we have a combination of bad modelling and inppropriate scraping. It is a valuable property of a Queensland place, but it's pretty much unusable on Wikidata at the moment given the current modelling and the current scraped data. Kerry Raymond (talk) 00:21, 20 October 2017 (UTC)
- To be specific, the unique value violations generally arise from the data that appears to have been scraped from the use of the Cite QPN template on en.WP. The single value violations are a modelling error in that places like small towns usually have two QPN entries, one as a populated place and one as a locality. Kerry Raymond (talk) 02:26, 20 October 2017 (UTC)
- Having had no response in over 5 years, I have removed the single-value constraint. Kerry Raymond (talk) 03:07, 12 March 2023 (UTC)