Changes between Version 7 and Version 8 of FDORfc63

Timestamp:

06/01/12 07:25:01 (12 years ago)

Author:

danstoica

Comment:

--

FDORfc63

@@ -118 +118 @@
     ///      32 bits (32-63) - 1-based segment # 
     /// 
+    /// In Mode #3 a exception will be thrown in case the encoding fails. In this case
+    /// Mode #2 can be used instead.
+    ///
     /// \param featId 
     /// Input The feature identifier
@@ -127 +130 @@
     /// 
     FDO_SPATIAL_API void InsertObject(FdoInt32 featId, FdoByteArray* fgfArray);
+
+    /// \brief
+    /// Erases an entry in the spatial index given the id and a bounding box
+    ///
+    /// \remarks
+    /// In Mode #2 removes all the entries related to the feature identifier. 
+    /// In Mode #3 the spatial index will be emptied.
+    ///
+    /// \param featId 
+    /// Input The feature identifier. 
+    /// \param ext 
+    /// Input The bounding box of the feature. It may be NULL in which case 
+    /// the spatial index total extents will be used.
+    /// 
+    /// \return
+    /// Returns Nothing
+    /// 
+    FDO_SPATIAL_API void EraseObject(FdoInt64 featId, FdoIEnvelope *ext);
 
     /// \brief
@@ -223 +244 @@
 * Mode 1 implements a regular spatial index, very performant
 * For mode 2 and 3 the client code has to implement a segment visitor in order to retrieve a segment from the geometry. 
-* The actual implementation will be the R-tree implementation found under Sqlite provider and developed by Traian Stanev. 
+* This API is a wrapper over the R-tree implementation located in the Sqlite provider and developed by Traian Stanev. 
+* The location of this API will be FDO Spatial.
 
 == How to use this API ==