Location Type LOTY Light Phase LPH Layer Priority Number LPN
5.7.1.3.34 Location Type LOTY
Description: A value that uniquely attributes a location feature according to the enumerators found here. ● Identifier: LOTY ● Code: 0033 ● Data Type: Enumeration per Table 5-21: Location Type Enumeration Values ● Length: 3 characters ● Format: integer ● Range: 0 to 999 ● Usage Note: Optional. Applicable to Geopolitical Dataset polygon features. See table below for a list of accepted values. Can be used only with Location Point, Lineal or Polygon Feature Datasets which are part of the Geopolitical Datasets ● Unit: In cases where the location represents a bounded area, the approximate geometric center is assumed. ● Default: ● Compatibility: OGC CDB 1.0. 247 © 2016 Open Geospatial Consortium Table 5-21: Location Type Enumeration Values LOTY Code Description Unknown 1 Continent 2 Country 3 State 4 Capital 5 Province 6 City 7 Municipality 997 Unpopulated 998 Not Applicable 999 Other5.7.1.3.35 Light Phase LPH
Description: Used for all light types that are periodic in nature rotating, blink, flashing, etc. The value of LPH controls the phase of the light relative to all other lights that share the same LTYP. All other light characteristics, including frequency and duration are implicitly determined by the LTYP. ● Identifier: LPH ● Code: 0034 ● Data Type: numeric ● Length: 3 characters ● Format: integer ● Range: 0 to 999 ● Usage Note: Optional. In absence of a value, LPH defaults to a value of 0. ● Unit: thousands of a cycle ● Default: 000 ● Compatibility: OGC CDB 1.05.7.1.3.36 Layer Priority Number LPN
Description: A priority number that establishes the relative priority of overlapping features. LPN establishes the order starting from 0 for lowest priority by which overlapping features are processed by client-devices. ● Identifier: LPN ● Code: 0035 ● Data Type: numeric ● Length: 5 characters ● Format: integer ● Range: 0 to 32767 248 © 2016 Open Geospatial Consortium ● Usage Note: Mandatory for terrain constraint features that overlap one another. For all other features, it is optional. LPN is derived from priority information stored and maintained by the authoring tools. ● Unit: NA ● Default: None ● Compatibility: OGC CDB 1.05.7.1.3.37 LaneTrack Number LTN
Parts
» Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure
» Identifiers CDB XML Schema Definitions.
» CDB Metadata Files CDB Directory File Naming and Structure
» Conformance References Terms and Definitions CDB Feature Data Dictionary
» Purpose Document Structure Introduction
» What is the CDB Standard: An Overview
» What the CDB Standard is Not
» Coordinate Reference Systems Geographic Coordinates
» Details of the Tiling System in the CDB core model
» Tile LoD Area Coverage Rules Tile-LOD Hierarchy Rules Tile-LOD Replacement Rules
» Handling of the North and South Pole
» Adding Names to the CDB Light Name Hierarchy
» Composite Material Substrates Composite Materials
» Composite Material Tables CMT
» Bringing it all Together Determination of Material Properties by Sensor Environmental Model SEM
» Generation of Materials for Inclusion in CDB Datasets
» \CDB\: \CDB\Metadata\: The directory that contains the specific XML metadata files which are
» CDB Version Directory Structure CDB Configuration
» GSModel Geospecific 3D Model T2DModel Tiled 2D Model MModel Moving 3D Model
» Use of GSModels and GTModels
» Organizing Models into Levels of Detail
» Texture Name Level of Detail
» GTModelGeometry Entry File Naming Convention GTModelGeometry Level of Detail Naming Convention
» GTModelDescriptor Naming Convention Examples
» GTModelTexture Naming Convention GTModelMaterial Naming Convention GTModelCMT Naming Convention
» Examples GTModel Directory Structure 2: Texture, Material, and CMT
» GTModelInteriorGeometry Naming Convention GTModelInteriorDescriptor Naming Convention
» GTModelInteriorTexture Naming Convention GTModelInteriorMaterial Naming Convention Example 1
» GTModelSignature Naming Convention Examples
» MModelGeometry Naming Convention MModelDescriptor Naming Convention Examples
» MModelTexture Naming Convention MModelMaterial Naming Convention MModelCMT Naming Convention
» Naming Convention Examples MModel Directory Structure 3: Signature
» Raster Datasets Vector Datasets
» Examples Directory Level 3 Dataset Directory
» Client Specific Lights Definition Metadata
» Model Components Definition File Base Materials Table Default Values Definition Table
» Definition of the Attribute Element Requirement 75
» Definition of the Scaler Element Requirement 79 Example of CDB_Attributes.xml
» A Note about Folder Path Example
» CDB Model Textures CDB Datasets
» GTModel Library Datasets CDB Datasets
» MModel Library Datasets CDB Datasets
» List of all Elevation Dataset Components
» Data Type Supported Compression Algorithm
» Terrain Constraints Tiled Elevation Dataset
» Level of Details MinElevation and MaxElevation Components
» Data Type Default Read Value
» Default Write Value MinElevation and MaxElevation Components
» Level of Details Data Type Default Read Value Default Write Value
» Data Type Default Read Value Default Write Value Supported Compression Algorithm
» Vector Type Usage and Conventions
» Attribute Code Attribute Identifier Attribute Semantics Attributes Values Attribute Usage
» Attribution Data Compatibility Attribution Schemas
» ATARS Extended Attribute Code AEAC – Deprecated Absolute Height Flag AHGT
» Angle of Orientation AO1 Airport Feature Name APFN – Deprecated Airport ID APID
» Bounding Box Height BBH Bounding Box Width BBW Bounding Box Length BBL Boundary Type BOTY
» Bounding Sphere Radius BSR CDB Extended Attribute Index CEAI
» DIGEST Extended Attribute Code DEAC – Deprecated Depth below Surface Level DEP Directivity DIR
» Height above Surface Level HGT Junction ID JID
» Location Type LOTY Light Phase LPH Layer Priority Number LPN
» LaneTrack Number LTN Light Type LTYP Model Level Of Detail MLOD
» Moving Model DIS Code MMDC Model Name MODL Model Type MODT Network Component Selector 1 NCS1
» Populated Place Type POPT Relative TActical Importance RTAI
» Runway ID RWID Scaling SCALx Scaling SCALy Scaling SCALz
» Start Junction ID SJID Surface Roughness Description SRD
» Structure Shape Category SSC Structure Shape of Roof SSR
» Traffic Flow TRF Taxiway ID TXID Urban Street Pattern USP
» 2D Relationship Tile Connection File
» 2D Relationship Dataset Connection File
» Explicitly Modeled Representations .1 Implicitly Modeled Representations Handling of Light Points
» Allocation of CDB Attributes To Vector Datasets
Show more