Property talk:P2824

Documentation

• Start a query
• Current uses
• Statistics by class
• String length
• List of qualifiers
• Count

Gazetteer of Planetary Nomenclature ID
identifier of a feature on an astronomical body in the Gazetteer of Planetary Nomenclature

Applicable "stated in" value	Gazetteer of Planetary Nomenclature (Q24033439)
Data type	External identifier
Template parameter	en:Template:GPN: |id= - Template:Gazetteer of Planetary Nomenclature (Q12981608)
Allowed values	[1-9][0-9]{0,3}|1[0-9]{4}|
Example	Rossby (Q19972237) → 5194 Vallis Snellius (Q422224) → 6301
Source	http://planetarynames.wr.usgs.gov/
Formatter URL	http://planetarynames.wr.usgs.gov/Feature/$1
Tracking: same	no label (Q32084860)
Tracking: differences	no label (Q32069096)
Tracking: usage	Category:Pages using Wikidata property P2824 (Q32069094)
Tracking: local yes, WD no	no label (Q32069097)
Lists	Items with the most statements of this property Count of items by number of statements (chart) Items with the most statements Items with the fewest statements Count of items by number of sitelinks (chart) Items with the most sitelinks Items with the most sitelinks, but no link to one Wikipedia (sample: Welsh Wikipedia, cywiki) Items with the fewest sitelinks Most linked wikis Items with the most identifier properties Items with no other external identifier Items with no other statements Most recently created items Items with novalue claims Items with unknown value claims Usage history (total) Usage history (main statement) Chart by item creation date Database reports/Constraint violations/P2824 Map Random list
Proposal discussion	Proposal discussion
Current uses	Total 8,870 Main statement 8,841 99.7% of uses Qualifier 2 <0.1% of uses Reference 27 0.3% of uses
Search for values

[create Create a translatable help page (preferably in English) for this property to be included here]

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

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

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/P2824#Single value, SPARQL

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/P2824#Unique value, SPARQL (every item), SPARQL (by value)

Conflicts with “instance of (P31): human (Q5)”: 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/P2824#Conflicts with P31, search, SPARQL

Item “located on astronomical body (P376)”: Items with this property should also have “located on astronomical body (P376)”. (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/P2824#Item P376, search, SPARQL

Scope is as main value (Q54828448), as reference (Q54828450): the property must be used by specified way only (Help)

List of violations of this constraint: Database reports/Constraint violations/P2824#Scope, hourly updated report, 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/P2824#Entity types

This property is being used by: it:Template:GPN en:Template:Gazetteer of Planetary Nomenclature ja:Template:GPN, ja:Template:Gazetteer of Planetary Nomenclature es:Plantilla:Gpn ca:Plantilla:Gpn, ca:Plantilla:Accident geogràfic extraterrestre, ca:Plantilla:Infotaula accident geogràfic extraterrestre uk:Шаблон:Кратер eu:Txantiloi:Gpn la:Formula:Data astronomica ast:Plantía:Gpn bh:टेम्पलेट:Gazetteer of Planetary Nomenclature my:Template:Gazetteer of Planetary Nomenclature, my:တမ်းပလိတ်:Gazetteer of Planetary Nomenclature th:แม่แบบ:GPN as:সাঁচ:Gpn zh:Template:Gpn vi:Bản mẫu:Gpn be-x-old:Шаблён:Геаграфічны даведнік плянэтнай намэнклятуры pt:Predefinição:GPN bcl:Plantilya:Gazetteer of Planetary Nomenclature vec:Modeło:Infobox de Insidente zeogràfego extraterestre, vec:Modeło:Infobox de Zeografia extraterestre azb:شابلون:Gazetteer of Planetary Nomenclature hr:Predložak:Gazetteer of Planetary Nomenclature bs:Šablon:Gpn tum:Template:Gazetteer of Planetary Nomenclature be-tarask:Шаблён:Геаграфічны даведнік плянэтнай намэнклятуры ro:Format:GPN simple:Template:Gazetteer of Planetary Nomenclature Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.)

Allowing 'no value' constraint ?

Hi,

ValterVB raised an interesting point on my talk page. Should we allow 'no value'/'some value' when a value can be expected but there is none? Right now there is two constraint violations for Mons Argenteus (Q1945231) (added by me) and Henry (Q18559333) (added by Nikki), there will be probably a few more.

FYI, that's something we usually do with Mérimée ID (P380) but with 'some value' ; for example on Église Saint-Aubin de Saint-Aubin-du-Cormier (Q23497952) as we know there will be a value added to the database in 2016-2017.

Arlo Barnes Athulvis Buller1 cdo256 Cekli829 Harlock81 Jc3s5h JenlovesbigD J. N. Squire Jura1 Kepler-1229b LiMr Manlleus Meodudlye, with only limited amount of time to spend in the foreseable future. Mike Peel mu301 (mikeu) Paperoastro Path slopu Ptolusque Romuald 2 Sarilho1 Sherman Alexander Shisma Simon Villeneuve SM5POR Tom.Reding VIGNERON Wallacegromit1 - generally like to add ground and space observatory instrument data Ysogo Jck1337

Notified participants of WikiProject Astronomy

Cdlt, VIGNERON (talk) 10:24, 4 June 2016 (UTC)

I think it should be allowed (I was intending to modify the constraint to allow it, I added a bunch more of them earlier today) because it allows us to distinguish between things which probably do have one and it just hasn't been added yet from things which haven't been assigned one. I think novalue is the right thing to use here. somevalue would mean that it does have an ID but we don't know what it is, but there is no reason to think that the items already have IDs or even that they will definitely get one in the future. It would probably be a good idea to add point in time (P585) qualifiers to the statements. - Nikki (talk) 12:23, 4 June 2016 (UTC)

@Nikki, VIGNERON: The meaning of "no value" is: id exist but we (wikidata user) haven't found, or the value don't exist but we (wikidata user) think that is necessary? --ValterVB (talk) 13:10, 4 June 2016 (UTC)

@ValterVB, Nikki: here, the meaning of "no value" is more id doesn't exist but should exist/is expected. id exist but we (wikidata user) haven't found match the meaning of "some value". In the case of Mérimée ID (P380) "some value" stand for id will exist but we have to wait the next database update (update around once a year, usually in the summer) ; I don't know exactly how database is updated concerning the Gazetteer (if someone has insights, you're welcome to share them). Cdlt, VIGNERON (talk) 13:17, 4 June 2016 (UTC)

The first one would be "some value", the second one would be "no value" (see the glossary). - Nikki (talk) 08:53, 5 June 2016 (UTC)

"Somevalue" is generally taken to mean that it actually exists, but we don't know it (which seems odd for identifiers with formatter urls). It shouldn't be based on some forecast.
--- Jura 08:56, 5 June 2016 (UTC)

I'm not the one using it as a forecast. Maybe you intended to reply to VIGNERON. - Nikki (talk) 09:11, 5 June 2016 (UTC)

True we shouldn't forecast but it's more than forecasting when you are sure the ID will exist (and for Mérimée ID (P380) we are 99,99% sure). Plus, I don't see any real difference between « value is unknown because XXX » or « value is unknown yet », is both case the value is unknown...

Does anybody know precisely and exactly how the Gazetteer of Planetary Nomenclature process of the database works ? Does 'no value' or 'some value' fit best the situation(s) ? I think 'no value' is better here since the value isn't unknown, we do know there is no value.

Cdlt, VIGNERON (talk) 10:41, 5 June 2016 (UTC)

Just for the chronicle

• Mars completed at 15 July 2016 (only approved feature) query --ValterVB (talk) 10:02, 15 July 2016 (UTC)
• Venus completed at 15 July 2016 (only approved feature) query --ValterVB (talk) 10:02, 15 July 2016 (UTC)
• Mercury completed at 16 July 2016 (only approved feature) query --ValterVB (talk) 15:11, 16 July 2016 (UTC)
• Ceres completed at 16 July 2016 (only approved feature) query --ValterVB (talk) 16:03, 16 July 2016 (UTC)

502 Bad Gateway (Q97445863)

The pages themselves seem to be erroring out, but the search page still reveals:

• Feature ID
• Feature Name
• Clean Feature Name
• Target
• Diameter
• Center Lat/Lon
• Lat/Lon Boundaries
• Coordinate System
• Continent/Ethnicity
• Feature Type
• Feature Type Code
• Quad (link to PDF map page with Control-Fable labels)
• Approval Status
• Approval Date
• Reference (on hover)
• Origin
• Additional Info
• Last Updated

in a table; as such, should we link to https://planetarynames.wr.usgs.gov/AdvancedSearch instead until their system is repaired? Arlo Barnes (talk) 06:20, 26 March 2022 (UTC)

Well, it's back up now. Arlo Barnes (talk) 16:08, 5 April 2022 (UTC)