Tile LoD Area Coverage Rules Tile-LOD Hierarchy Rules Tile-LOD Replacement Rules
2.1.2.1 Tile LoD Area Coverage Rules
Requirement 14 http:opengis.netspecCDB1.0core lod-area-coverage A tile from LOD –10 to LOD 0 SHALL occupy the area of exactly one CDB Geocell. This is true for all CDB Geocells from all CDB Zones. Starting with LOD 1 and up, this area SHALL recursively be subdivided into smaller tiles, every level corresponding to a finer representation of the previous level allowing for multiple levels of detail. Consequently, tiles at a given LOD never overlap with others of the same LOD, and are always aligned with at least two of the edges of tiles at the previous LOD. Figure 2-4 illustrates how different Levels of Detail LOD’s can be combined within individual geocells. In the illustration, some CDB Geocells of the pictured earth slice are represented using five LODs, while others have only three or four LODs. Each Geocell included in a CDB data store shall represented by an instance of at least the coarsest tile supported, i.e., one tile at LOD −10. In addition, it is not necessary that the entire geocell be represented at the same level of resolution across the entire cell. However, if a tile is present at LOD n, it implies that a courser tile exists at LOD n−1 covering the area of the tile at LOD n, until LOD −10 is reached 40 © 2016 Open Geospatial Consortium Figure 2- 4: Earth Slice Example Five Levels of Detail2.1.2.2 Tile-LOD Hierarchy Rules
Requirement 15 http:opengis.netspecCDB1.0core hierarchy The LOD hierarchy of all tiled datasets SHALL be complete for every CDB Geocell. However, each CDB Geocell may have a different number of Tile-LODs. 41 © 2016 Open Geospatial Consortium2.1.2.3 Tile-LOD Replacement Rules
In general, finer tiles replace coarser tiles. The requirements are: Requirement 16 http:opengis.netspecCDB1.0core tile-lod-replacement For negative levels of details, a tile at LOD n SHALL replace exactly one tile at LOD n−1 since both tiles cover the same area. For positive levels of details, a tile at LOD n SHALL be replaced by 4 tiles at LOD n+1 since tiles from LOD n+1 cover only a quarter of the area covered by the tile at LOD n. In the case of positive LODs, note that it is not necessary that all 4 tiles from LOD n+1 exist; as long as one of the four tiles is present, the replacement of the tile at LOD n can take place. For instance, one tile at LOD −1 is replaced by one tile at LOD 0 which is in turn replaced by four tiles at LOD 1. The replacement of coarser tiles with finer tiles stops when no finer tiles exist.2.1.3 Handling of the North and South Pole
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