Property talk:P239
Documentation
four-character alphanumeric identifier for designating airports (for airlines, see P230)
List of violations of this constraint: Database reports/Constraint violations/P239#Type Q62447, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P239#Single value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P239#Unique value, SPARQL (every item), SPARQL (by value)
List of violations of this constraint: Database reports/Constraint violations/P239#Item P625, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P239#Item P17, search, SPARQL
([A-Z]{2}|[CKY][A-Z0-9])([A-Z]{2}|[0-9]{2,4})
”: value must be formatted using this pattern (PCRE syntax). (Help)List of violations of this constraint: Database reports/Constraint violations/P239#Format, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P239#single best value, SPARQL
List of violations of this constraint: Database reports/Constraint violations/P239#Item P2786, SPARQL
This property is being used by:
Please notify projects that use this property before big changes (renaming, deletion, merge with another property, etc.) |
Request to change en title to ICAO airport code[edit]
I want to have the title changed to ICAO airport code, in order to avoid conflict with the ICAO airline code property. Harryboyles (talk) 10:32, 7 March 2013 (UTC)
- Have done so. Harryboyles (talk) 10:41, 7 March 2013 (UTC)
format constraint[edit]
i changed it from [A-Z][A-Z][A-Z][A-Z] to ([A-Z][A-Z]|[CKY][A-Z0-9])[A-Z0-9][A-Z0-9], since the locally assigned code parts may contain digits. --Akkakk 23:40, 3 June 2013 (UTC)
- I've changed the regex since there happen to be pseudo codes (very small aerodromes using a country-based ICAO code) for instance Q30738830
testable here ([A-Z]{2}|[CKY][A-Z0-9])([A-Z]{2}|[0-9]{2,4})
Feel free to modify the regex if you find it inappropriate. Bouzinac (talk) 19:44, 23 November 2019 (UTC)
- @Bouzinac: Many small Czech airfields (e. g. Kejžlice Airfield (Q111494366) and Jehnědí Airfield (Q112066471)) has LKABCD-type code. I don't know, whether the airport code has been officially assigned, but those 6-letter codes seem to appear in may aviation maps. — Draceane talkcontrib. 21:46, 15 December 2022 (UTC)
Property constraint concerning IATA code[edit]
The constraint regarding IATA codes should be removed, because not all airfields with an ICAO code even have an IATA code assigned. Cheers --MB-one (talk) 15:13, 12 August 2017 (UTC)
- Done --MB-one (talk) 10:49, 26 September 2017 (UTC)
ICAO codes being reassigned...[edit]
For example, en:MOD_St_Athan changed ICAO code from EGXD to EGSY (which used to be en:Sheffield City Airport.
This means the warnings on Q3565572 and Q3915754 for ICAO code reuse, and having more than one ICAO code are irritating...
Reedy (talk) 00:10, 28 April 2019 (UTC)
Distinct values constraint Closed Airport[edit]
Q330015 and Q1436575 have overlapping values for P239. How should this be handled because Q1436575 is closed?
- Done with deprecated values. Bouzinac (talk) 19:37, 23 November 2019 (UTC)
Proposal - Change Data type of ICAO airport code (P239) from String to External identifier[edit]
I think String is the wrong type for ICAO airport code (P239). Can we please change it to be External identifier.
As per Help:Data_type#Changing_datatype please indicate support/opposition below. Iwan.Aucamp (talk) 16:52, 15 October 2019 (UTC)
Discussion[edit]
- Comment See the large number of "Unique value" constraint violations in the constraint report linked above. These should be cleaned up somehow before this is made a real external id, if that is to happen. ArthurPSmith (talk) 17:23, 15 October 2019 (UTC)
- All Properties
- Properties with string-datatype
- Properties used on 10000+ items
- Properties with constraints on type
- Properties with single value constraints
- Properties with unique value constraints
- Properties with constraints on items using them
- Properties with scope constraints
- Properties with format constraints
- Properties with single best value constraints