: Public <<XSDsimpleType>> Class

Created: | 8/10/2016 5:09:02 PM
Modified: | 3/16/2020 12:10:51 PM
Project: |
Author: | FAA
Version: | 4.0.0
Phase: |
Status: | Implemented
Complexity: | Easy
Difficulty: |
Priority: |
Multiplicity: |
Advanced: |
UUID: | {505962E3-185D-4fb7-8A0F-4CBE92D17E6E}
Appears In: |

This three or four character field contains the city and state where the equipment is physically located. Location identifiers assignment process is detailed in Order 6000.5E, Chapter 3, Section 3.1 Location Identifier Process. This is the field FAC_IDENT in the RMLS/FSEP database but which is typically referred to as LOC_ID. There are three sources for a LOC_ID:<br/><ol>
<li>A value from the IDENT column in the 7350.9.</li><li>A value from the IDENT column in the 7350.9 to which a single character suffix is added. The suffix is added when there is more than one instance of the same FSEP Facility at a specific location. An example is the Precision Approach Path Indicators (PAPI) at Boston Logan Airport. There are 4 of these, and each has a different LOC_ID derived from BOS, the identifier for Logan. These are BOS, BOSA, BOSB and BOSC.</li><li>A made up value starting with a Q. These are known as Q Identifiers and are created when there is no established identifier within 20 miles of the location of the FSEP Facility.</li></ol>
Sample values include I90, DAL, TPA, CXYA, DCAP, PUB, ZDCC, DFWA.<br/><br/>

- Tagged Values
- Constraints
- Advanced

Tag | Value
derivation | restriction
Details: Values: restriction | list Default: restriction Description: Defines derivation type
pattern | [A-Z0-9]{3,4}
Details: Description: As defined by XML Schema Datatypes specification

Constraint | Type | Status
No attributes or associations | Invariant | Implemented
Details: This UML class may not have any attributes or associations originating from it.<br/>
Parent must be simpleType | Invariant | Implemented
Details: If a superclass is specified, it must also be a SimpleType<br/>

Property | Value
isFinalSpecialization: | 0