WATERBOUNDARY_SURFACE The exterior shell of a can be differentiated semantically using features of the type WaterBody _WaterBoundarySurface. These features are stored in the WATERBOUNDARY_SURFACE table and can be distinguished by the OBJECTCLASS_ID attribute: '11' (WaterSurface) '12' (WaterGroundSurface) '13' (WaterClosureSurface) Since every _WaterBoundarySurface object must have at least one associated surface geometry, the foreign keys LODx_SURFACE_ID (with 2 4, no MultiSurface here) are used to realise ≤x ≤ these relations. Figure 47: WaterBody database schema Sequences Figure 48 lists predefined sequences from which multiple users may generate unique integers for primary keys automatically. Sequences help to coordinate primary keys across multiple rows and tables. For instance, the ID values of the table are generated from the BUILDING sequence. The sequences are defined to start with 1 and to be incremented CITYOBJECT_SEQ by 1 when a sequence number is generated. It is highly recommended to generate ID values for all tables by using the predefined sequences only. The sequence does not exist in the PostgreSQL version as the GRID_COVERAGE_RDT_SEQ corresponding table does not exist. Figure 48: Tables for spatial information and sequences Definition of the CRS for a 3D City Database instance The definition of the CRS of a 3D City Database instance consists of two components: 1) a valid (SRID) (EPSG code) and 2) an OGC GML conformant Spatial Reference Identifier Both components are defined during the database setup (see definition identifier for the CRS. chapter 3.3) and are further stored in the table Figure 48). DATABASE_SRS (see The SRID is an integer value key pointing to spatial reference information within Oracle’s table or table. Both DBMSs are shipped PostGIS’ MDSYS.CS_SRS SPATIAL_REF_SYS with a large number of predefined spatial reference systems. At setup time, the SRID chosen as default value for the 3D City Database instance must already exist in the mentioned tables! The GML conformant is used as value for the CRS definition identifier gml:srsName attribute on GML geometry elements when exporting database contents to CityGML instance
WATERBOUNDARY_SURFACE The exterior shell of a WaterBody can be differentiated semantically using features of the type _WaterBoundarySurface. These features are stored in the WATERBOUNDARY_SURFACE table and can be distinguished by the OBJECTCLASS_ID attribute: '11' (WaterSurface) '12' (WaterGroundSurface) '13' (WaterClosureSurface) Since every _WaterBoundarySurface object must have at least one associated surface geometry, the foreign keys LODx_SURFACE_ID (with 2 ≤x ≤ 4, no MultiSurface here) are used to realise these relations. Figure 47: WaterBody database schema Sequences Figure 48 lists predefined sequences from which multiple users may generate unique integers for primary keys automatically. Sequences help to coordinate primary keys across multiple rows and tables. For instance, the ID values of the BUILDING table are generated from the CITYOBJECT_SEQ sequence. The sequences are defined to start with 1 and to be incremented by 1 when a sequence number is generated. It is highly recommended to generate ID values for all tables by using the predefined sequences only. The sequence GRID_COVERAGE_RDT_SEQ does not exist in the PostgreSQL version as the corresponding table does not exist. Figure 48: Tables for spatial information and sequences Definition of the CRS for a 3D City Database instance The definition of the CRS of a 3D City Database instance consists of two components: 1) a valid Spatial Reference Identifier (SRID) (EPSG code) and 2) an OGC GML conformant definition identifier for the CRS. Both components are defined during the database setup (see chapter 3.3) and are further stored in the table DATABASE_SRS (see Figure 48). The SRID is an integer value key pointing to spatial reference information within Oracle’s MDSYS.CS_SRS table or PostGIS’ SPATIAL_REF_SYS table. Both DBMSs are shipped with a large number of predefined spatial reference systems. At setup time, the SRID chosen as default value for the 3D City Database instance must already exist in the mentioned tables! The GML conformant CRS definition identifier is used as value for the gml:srsName attribute on GML geometry elements when exporting database contents to CityGML instance
3DCityDB_Documentation_v3.docx