ATARS Extended Attribute Code AEAC – Deprecated Absolute Height Flag AHGT
5.7.1.3 CDB Attributes
This section provides a list and description of the attributes that are governed by the CDB standard. Note that it is possible to provide attributes other than those listed here by making use of the Geomatics and Vendor Extended-level attribution schema.5.7.1.3.1 ATARS Extended Attribute Code AEAC – Deprecated
Description: See OGC CDB Best Practice5.7.1.3.2 Absolute Height Flag AHGT
Description: Indicates how to interpret the Z component of a vertex. ● Identifier: AHGT ● Code: 0002 ● Data Type: Logical ● Length: 1 character ● Format: NA ● Range: F, f, N, n false and T, t, Y, y true ● Usage Note: Optional. Specifies how to interpret vector data type features with a Z component. If AHGT is true, the feature is positioned to the value specified by the Z component Absolute Terrain Altitude, irrelevant of the terrain elevation dataset. If AHGT is false or not present, the feature is positioned to the value specified by the underlying terrain offset by the Z component value. Refer to section 5.7.1.1, Vector Type Usage and Conventions for more details. AHGT can be present only in datasets using PointZ, PolylineZ, PolygonZ and MultiPointZ vector data types types. AHGT should not be present for all other vector data types or must be ignored otherwise. Refer to Section 6.3 in Volume 7: CDB Data Model Guidance formerly Appendix A – “How to Interpret the AHGT, HGT, BSR, BBH, and Z Attributes” for additional usage guidelines. ● Unit: NA ● Default: False ● Compatibility: OGC CDB 1.0 NOTE: It is recommended that the AHGT flag be set to false because it facilitates the creation of CDB compliant datasets that are independent of each other. When the Z coordinate altitude of a feature is relative to the ground, the terrain elevation dataset can be updated without the need to re-compute the altitude of the feature. 233 © 2016 Open Geospatial Consortium CAUTION: When the AHGT flag is set to true, the feature will be at a fixed WGS-84 elevation independently of the terrain LOD selected by the client-device. As a result, there is no guarantee that the feature and its modeled representation will remain above the terrain across all terrain LODs. RECOMMENDATION: Limit the use of AHGT=TRUE to data whose source is inherently absolute. Such source data include geodetic marks or survey marks that provide a known position in terms of latitude, longitude, and altitude. Good examples of such markers are boundary markers between countries.5.7.1.3.3 Angle of Orientation AO1
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