Changes between Version 3 and Version 4 of FDORfc64

Timestamp:

Sep 24, 2012, 10:20:35 AM (12 years ago)

Author:

danstoica

Comment:

--

FDORfc64

@@ -52 +52 @@
     /// \param g1 
     /// Input Left hand Geometry to Evaluate
-    /// \param si1
-    /// Input The spatial index associated with g1. A valid spatial index is not NULL
-    /// and of type BySegmentsSingleFeature or BySegmentsMultipleFeatures (just one
-    /// feature). If an invalid spatial index is provided, then this method will silently
-    /// delegate to Evaluate(g1, op, g2, tolXY). 
     /// \param op 
     /// Input The spatial operation to apply to the left and right hand geometries 
     /// \param g2 
     /// Input Right hand Geometry to Evaluate
+    /// \param si2
+    /// Input The spatial index associated with g2. A valid spatial index is not NULL
+    /// and of type BySegmentsSingleFeature or BySegmentsMultipleFeatures (just one
+    /// feature). If an invalid spatial index is provided, then this method will silently
+    /// delegate to Evaluate(g1, op, g2, tolXY). 
     /// \param toleranceXY
     /// Input XY tolerance to evaluate the spatial condition
@@ -68 +68 @@
     /// \return
     /// Returns the evaluation of spatial operation.
-    FDO_SPATIAL_API static bool Evaluate(FdoIGeometry* g1, FdoSpatialIndex* si1, FdoSpatialOperations op, FdoIGeometry* g2, double toleranceXY); 
+    FDO_SPATIAL_API static bool Evaluate(FdoIGeometry* g1, FdoSpatialOperations op, FdoIGeometry* g2, FdoSpatialIndex* si2, double toleranceXY); 
 
 }}}
@@ -74 +74 @@
 
 == Remarks ==
-
+ 
+   * the implementation of this new API will focus on FDO Polygons, MultiPolygons, CurvePolygons and MultiCurvePolygons as filter geometries.
+   * FdoExpressionEngineImp::ProcessSpatialCondition() will be changed to take advantage of this new API.
 
 == How to use this API ==
 
+       // The filter geometry
+       FdoPtr<FdoIGeometry> geomRight = ...
+
+       FdoPtr<FdoFgfGeometryFactory> gf = FdoFgfGeometryFactory::GetInstance();
+       FdoPtr<FdoByteArray> fgf = gf->GetFgf(geomRight);
+
+       // Check the geometry type. Create a spatial index in case the type is Polygon or MultiPolygon
+       // and it has a non-trivial number of segments (say over 400).
+       FdoPtr<FdoSpatialIndex> si = NULL;
+       try
+       {
+           si = FdoSpatialIndex::Create(FdoSpatialIndex_BySegmentsSingleFeature);
+           si->InsertObject(0, fgf);
+       }
+       catch (FdoException* ex)
+       {
+           ex->Release();
+
+           // Creation failed due to excessive number of parts or subparts
+           // Try BySegmentsMultipleFeatures mode. It should succeed.
+           si = FdoSpatialIndex::Create(FdoSpatialIndex_BySegmentsMultipleFeatures);
+           si->InsertObject(0, fgf);
+       }
+
+       // Assume the spatial operation is FdoSpatialOperations_Intersects
+       // For every candidate geometry evaluate against the filter geometry...
+
+       FdoPtr<FdoIGeometry> geomLeft = ... // The candidate geometry
+
+       bool eval = FdoSpatialUtility::Evaluate(geomLeft, FdoSpatialOperations_Intersects, geomRight, si, 0.001);
+
+       // Do something with the result
 
 == Managed FDO API ==
 
-At this time there is plan to update the FDO Managed Interfaces.
+At this time there is no plan to update the FDO Managed Interfaces since the managed spatial index is not implemented yet.
 
  
 == Test Plan ==
 
-    * Add unit test to test the new API in all modes and primary filtering with boundary conditions.
+    Add unit tests to test the new API for polygons and multipolygons with the spatial index mode #2 and #3 (i.e. BySegmentsSingleFeature and BySegmentsMultipleFeatures):
+    * Fidelity tests for Contains, Crosses, Disjoint, Equals, Intersects, Overlaps, Touches, Within, CoveredBy, and Inside spatial operators.
+    * Performance test to compare Evaluate() with and without spatial index
 
 == !Funding/Resources ==