Objects that are components of a Spatial Index Related Geometry or Spatial Index Related Features shall be fully contained within the spatial extents defined for that <Spatial Index Related> grouping, if the strict_organizing_principle field has value SE_TRUE.
If strict_organizing_principle has value SE_FALSE, no guarantees exist as to how accurately the components were placed into their 'sorted bins' (the branches of the Spatial Index Related Features or Spatial Index Related Geometry.
SEDRIS' spatial indexing mechanism was designed to allow the use of spatial indexing even when a few Features or Geometry cross the boundaries of the organizing principles.
<Spatial Index Related Geometry>
<>
|------- <UTM Location 3D>
| (0,0,0)
|
--------------------------------------------------------------
| | | |
| | | |
|- <Geometry |- <Geometry |- <Geometry |- <Geometry
| Spatial Index | Spatial Index | Spatial Index |Spatial
| Data> | Data> | Data> |Index Data>
| (index = 1) | (index = 2) | (index = 3) |(index = 4)
| | | |
| | | |
<Union of <Union of <Union of <Union of
Primitive Primitive Primitive Primitive
Geometry> Geometry> Geometry> Geometry>
Since the origin of the collection (its lower-left corner, the
UTM Location 3D is (0, 0, 0), the
coverages of the branches are:
(Note that a Spatial Index Related Geometry does not specify the range of z/height/elevation values.)
Consider a triangular Polygon in branch #2 of this aggregation, with Vertex Locations (1995,0,0), (2005,0,0) (2005,10,0).
Since this Polygon crosses the boundary between branch #2 and branch #3, this Spatial Index Related Geometry's strict_organizing_principle must be set to SE_FALSE.
<Spatial Index Related Features>
<>
|------- <UTM Location 3D>
| (0,0,0)
|
-----------------------------------------------------------
| | | |
| | | |
|- <Feature |- <Feature |- <Feature |- <Feature
| Spatial Index | Spatial Index | Spatial Index | Spatial
| Data> | Data> | Data> | Index Data>
| (index = 1) | (index = 2) | (index = 3) | (index = 4)
| | | |
| | | |
<Union of <Union of <Union of <Union of
Features> Features> Features> Features>
Since the origin of the collection (its lower-left corner, the
UTM Location 3D is (0, 0, 0), the
coverages of the branches are:
(Note that a Spatial Index Related Features does not specify the range of z/height/elevation values.)
Consider a triangular Areal Feature in branch #2 of this aggregation, consisting of one Regular Feature Face, which in turn has External Feature Face Ring containing 3 Feature Edges as follows:
<External Feature Face Ring>
<>
-----------------------------------------------
| | |
|- <Feature Ring |- <Feature Ring |- <Feature Ring
| Edge Direction> | Edge Direction> | Edge Direction>
| (forwards=SE_TRUE) | (forwards=SE_TRUE) | (forwards=SE_TRUE)
| | |
<Feature Edge> <Feature Edge> <Feature Edge>
(from A to B) (from B to C) (from C to D)
where A, B, C are Feature Nodes such that
Since the Areal Feature thus crosses the boundary between branch #2 and branch #3, the Spatial Index Related Features' strict_organizing_principle must be set to SE_FALSE.