3D Spatial Engine RDBMS Geometric Validation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional Geographic Information Systems (GIS) using three-dimensional spatial data face inefficiencies and scalability issues due to incomplete and ambiguous validation of geometric representations, particularly in systems employing three-dimensional models.
Innovation Solution
A three-dimensional spatial engine integrated with a relational database management system (RDBMS) that utilizes an open data type (e.g., SDO_GEOMETRY) to store and compute geometric properties, including decomposition of complex geometries, intersection calculations, and validation rules for ensuring geometric integrity, facilitating efficient storage and querying of three-dimensional objects.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If conventional two-dimensional spatial data representations are used, then system simplicity is maintained, but the ability to represent and process three-dimensional terrestrial objects is insufficient
Solution Approach 1:
The patent extends conventional two-dimensional spatial data models to three dimensions by introducing Z-coordinates to existing geometric types (points, lines, polygons) and creating new three-dimensional geometric types (solids). This allows the system to represent terrestrial objects in three-dimensional space while building upon existing two-dimensional spatial database infrastructure.
2Reliability
If three-dimensional geometric representations are implemented without comprehensive validation, then processing speed is improved, but geometric accuracy and reliability deteriorate
Solution Approach 1:
The patent implements validation rules that are applied during data insertion and modification operations to verify geometric integrity before the data is committed to the database. This preliminary validation ensures geometric accuracy is maintained while avoiding the need for time-consuming post-processing validation checks.
Solution Approach 2:
The patent replaces manual geometric validation processes with automated validation rules embedded in the spatial engine. These rules automatically check geometric properties (such as whether polygons are closed, whether lines intersect improperly, or whether solids have valid volumes) without requiring human intervention, thus maintaining accuracy while improving processing efficiency.
3Reliability
If comprehensive validation rules are applied to three-dimensional geometries, then geometric integrity is improved, but system complexity increases
Solution Approach 1:
The patent divides the validation system into separate, modular validation rules for different geometric types (points, lines, polygons, solids) and different geometric properties (closure, intersection, volume, surface area). Each validation rule is an independent unit that can be applied selectively based on the specific geometric type and operation, making the overall system more manageable and maintainable.
Solution Approach 2:
The patent creates a universal validation framework that can handle multiple geometric types and validation scenarios through a common set of validation rules. The same validation infrastructure supports two-dimensional and three-dimensional geometries, as well as various spatial operations (insertion, modification, querying), reducing overall system complexity through reuse.
4Adaptability or versatility
If complex three-dimensional spatial queries are supported, then query capability is improved, but computational overhead increases
Solution Approach 1:
The patent pre-computes and stores spatial indices and geometric properties (such as bounding volumes, surface areas, and volumes) during data insertion and modification operations. This preliminary computation allows complex spatial queries to be executed more efficiently by utilizing pre-computed data rather than calculating these properties from scratch during query processing.
Data Source
AI summary
Systems, methodologies, media, and other embodiments associated with a three dimensional spatial engine in an RDBMS are described. One example system includes logic to receive and store data representing a set of spatial features of a three dimensional geometry object. The example system may also include logic to validate the three dimensional geometry object and to provide a signal concerning the validity of the object.