Geometry storage in Surface Geometry – polygonal geometry Oracle PostGIS SDO_GTYPE must have the type Only POLYGON Z is allowed, i.e. a Polygon, i.e. a polygon with 3D polygon with 3D coordinates coordinates (SDO_GTYPE = 3003), Polygons might have holes SDO_ETYPE must be 1003/2003 with The IMPLICIT_GEOMETRY column SDO_INTERPRETATION = 1 (i.e. has no SRID defined. Thus, entries polygon with 3D coordinates in the in that column will have the SRID 0 boundary, bounded just by line automatically segments, possibly including holes) In addition Oracle allows the representation of a rectangle by two corner points (SDO_ETYPE=1003/2003, with SDO_INTERPRETATION = 3) SDO_SRID of implicit geometries can be any SRID Oracle supports. No spatial index is defined on the column by default. Table 4: Storage of polygonal geometry A solid is the basis for 3-dimensional geometry. The extent of a solid is defined by the boundary surfaces (outer shell). A shell is represented by a composite surface, where every shell is used to represent a single connected component of the boundary of a solid. It consists of a composite surface (a list of orientable surfaces) connected in a topological cycle. Unlike a ring, a shell's elements have no natural sort order. Like rings, shells are simple. The geometry in the field SOLID_GEOMETRY of the table SURFACE_GEOMETRY is limited as follows: Geometry storage in Surface Geometry – 3D geometry Oracle PostGIS SDO_GTYPE must have the type Only POLYHEDRALSURFACE is Solid, i.e. a solid with 3D allowed, i.e. the outer shell of a coordinates (SDO_GTYPE = 3008) solid with 3D coordinates SDO_ETYPE must be 1007 (simple A simple polyhedral surface can be solid) or 1008 (composite solid). represented by using several A simple solid can be represented polygons as its boundary by using several polygons as its boundary (SDO_ETYPE=1007, with SDO_INTERPRETATION = 1). The composite solid can be constructed with a number of simple solids, e.g. a composite solid with 4 simple solids (SDO_ETYPE=1008, with SDO_INTERPRETATION = 4)
Geometry storage in Surface Geometry – polygonal geometry Oracle PostGIS SDO_GTYPE must have the type Polygon, i.e. a polygon with 3D coordinates (SDO_GTYPE = 3003), SDO_ETYPE must be 1003/2003 with SDO_INTERPRETATION = 1 (i.e. polygon with 3D coordinates in the boundary, bounded just by line segments, possibly including holes) In addition Oracle allows the representation of a rectangle by two corner points (SDO_ETYPE=1003/2003, with SDO_INTERPRETATION = 3) SDO_SRID of implicit geometries can be any SRID Oracle supports. No spatial index is defined on the column by default. Only POLYGON Z is allowed, i.e. a polygon with 3D coordinates Polygons might have holes The IMPLICIT_GEOMETRY column has no SRID defined. Thus, entries in that column will have the SRID 0 automatically Table 4: Storage of polygonal geometry A solid is the basis for 3-dimensional geometry. The extent of a solid is defined by the boundary surfaces (outer shell). A shell is represented by a composite surface, where every shell is used to represent a single connected component of the boundary of a solid. It consists of a composite surface (a list of orientable surfaces) connected in a topological cycle. Unlike a ring, a shell's elements have no natural sort order. Like rings, shells are simple. The geometry in the field SOLID_GEOMETRY of the table SURFACE_GEOMETRY is limited as follows: Geometry storage in Surface Geometry – 3D geometry Oracle PostGIS SDO_GTYPE must have the type Solid, i.e. a solid with 3D coordinates (SDO_GTYPE = 3008) SDO_ETYPE must be 1007 (simple solid) or 1008 (composite solid). A simple solid can be represented by using several polygons as its boundary (SDO_ETYPE=1007, with SDO_INTERPRETATION = 1). The composite solid can be constructed with a number of simple solids, e.g. a composite solid with 4 simple solids (SDO_ETYPE=1008, with SDO_INTERPRETATION = 4) Only POLYHEDRALSURFACE is allowed, i.e. the outer shell of a solid with 3D coordinates A simple polyhedral surface can be represented by using several polygons as its boundary
3DCityDB_Documentation_v3.3.docx