Coordinate Reference Systems Geographic Coordinates
1.7.2.2 Compression of other imagery datasets
In general, all TIFFGeoTIFF files benefit from LZW compression. For this reason, and as a general practice, the compression of all TIFF-based raster datasets is recommended. The one exception is when every cell in the raster dataset is a unique floating point number. In this case, the compressed file may be larger than the original.1.7.2.3 Units of Measure
Requirement 7 http:opengis.netspecCDB1.0core uom All units of measure in a CDB conformant data store SHALL be in meters.1.7.3 Coordinate Reference Systems
Requirement 8 http:opengis.netspecCDB1.0core crs Geographic locations in CDB SHALL be expressed usingWGS-84 World Geodetic System 1984, equivalent to EPSG European Petroleum Survey Group code 4326 2 dimensions and EPSG code 4979 3 dimensions. If a geographic location also has an altitude, the altitude SHALL be expressed relative to the WGS-84 reference ellipsoid. Please see the Volume 8: OGC CDB Spatial Reference System Guidance. Requirement 9 http:opengis.netspecCDB1.0core crs-client 29 © 2016 Open Geospatial Consortium Each implementation of the simulator client-devices accessing the CDB geospatial data SHALL at a minimum support the WGS-84 geodetic coordinate system as specified in Req 8 . Other reference systems may be used in the client application.1.7.4 Geographic Coordinates
Requirement 10 http:opengis.netspecCDB1.0core coordinates Coordinates SHALL be described using the decimal degree format without the “°”symbol. The values of latitude and longitude SHALL be bounded by ±90° and ±180° respectively. Positive latitudes are north of the equator, negative latitudes are south of the equator. Positive longitudes are east of the Prime Meridian; negative longitudes are west of the Prime Meridian. Latitude and longitude are expressed in that sequence, namely latitude before longitude.2. CDB Concepts
This chapter presents basic CDB data store model concepts. These concepts are either reused by other concepts or used repeatedly throughout the Standard. The CDB core data model may be viewed as an instance of a Discrete Global Grid System as defined in OGC 15-104. Please note, however, that the CDB data model and structure predates the OGC DGGS activity by over a decade and as such should not be deemed compliant with the OGC DGGS standard.. A DGGS is a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo- encoding, quantization strategy and associated mathematical functions. The following sections detail the CDB tiling storage model. Requirements Class - TilesGeocells and LoD relationships 11-16 and 41 req corecdb-structure-tiles-lodParts
» 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