JPEG 2000 .jp2: used for the representation of an image encoded in accordance to 3D Models: Currently OpenFlight is used for the representation of 3-dimensional Vector features and geometry: Currently ShapeFiles are used for the representation Extensib
4. JPEG 2000 .jp2: used for the representation of an image encoded in accordance to
the JPEG 2000 standard. CDB-compliant JPEG 2000 readers must be fully compliant with the JPEG 2000 standard while reading such still image file types. JPEG 2000 encoded images can be used for the representation of geo-referenced terrain imagery with some degree of compression levels and is only applicable in the case of terrain raster imagery. Volume 2 CDB Core: Model and Physical Structure: Annexes C and H describe the use of the JPEG 2000 file format in a CDB data store.5. 3D Models: Currently OpenFlight is used for the representation of 3-dimensional
geometric representation of all models statically positioned cultural models, moving models. Please refer to the requirements described in Volume 6 OGC CDB Rules for Encoding Data using OpenFlight need URL.6. Vector features and geometry: Currently ShapeFiles are used for the representation
and attribution of the vector feature datasets in a CDB data store. Please see the requirements described in Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage.7. Extensible Markup Language .xml: used to store metadata that describes CDB
versioning, describes CDB Composite and Base material structure, defines CDB light type naming conventions and hierarchy, and defines CDB model component hierarchy.8. Cross-platform and interoperable file storage and transfer format .zip: used to
archive and store geospecific 3D model datasets. For all other formats used by this standard, CDB readers should be fully compliant 29 . File Format Versions Currently Supported by CDB CDB Client-device Behavior for Prior Versions .tif 6.0 Ignores data .rgb 1.0 Ignores data .jp2 1.0 Ignores data .flt 16.0 Ignores data .shp, .shx Esri White Paper, July 98 Ignores data .dbf, .dbt dBASE III+ and above Ignores data .xml 1.0 Ignores data .zip 6.3.1 Ignores data 29 This table will be expanded as Best Practices for additional formats and encodings are developed. 127 © 2016 Open Geospatial Consortium5. CDB Datasets
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