Changes between Version 9 and Version 10 of FDORfc63
- Timestamp:
- 06/13/12 08:19:55 (12 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
FDORfc63
v9 v10 8 8 9 9 ||RFC Template Version||(1.0)|| 10 ||Submission Date|| June 04, 2012 ||11 ||Last Modified|| Dan Stoica May 18, 2012 ||10 ||Submission Date|| June 13, 2012 || 11 ||Last Modified|| Dan Stoica June 13, 2012 || 12 12 ||Author||Dan Stoica|| 13 13 ||RFC Status||For review|| … … 91 91 /// 92 92 /// \remarks 93 /// Applies only for Mode #1. The Featid is not encoded.94 /// 95 /// \param featId96 /// Input The featureidentifier93 /// Applies only for Mode #1. The objectId is not encoded. 94 /// 95 /// \param objectId 96 /// Input The object identifier 97 97 /// \param ext 98 98 /// Input A bounding box … … 101 101 /// Returns Nothing 102 102 /// 103 FDO_SPATIAL_API void InsertObject(FdoInt64 featId, FdoIEnvelope *ext);103 FDO_SPATIAL_API void InsertObject(FdoInt64 objectId, FdoIEnvelope *ext); 104 104 105 105 /// \brief … … 107 107 /// 108 108 /// \remarks 109 /// Applies for Mode #2 and #3. The FeatId is encoded as follows:109 /// Applies for Mode #2 and #3. The objectId is encoded as follows: 110 110 /// Mode #2: 111 /// 32 bits (0-31) - 1-based featId #111 /// 32 bits (0-31) - 1-based object identifier 112 112 /// 32 bits (32-63) - 1-based segment # (contiguous) 113 113 /// 114 114 /// Mode #3: 115 /// 0 bits - featId #(will be ignored)115 /// 0 bits - object identifier (will be ignored) 116 116 /// 16 bits (0-15) - part # (for multi-features) max. 65534 117 117 /// 16 bits (16-31) - subpart # (e.g. polygons with interior rings) max 65534 … … 121 121 /// Mode #2 can be used instead. 122 122 /// 123 /// \param featId124 /// Input The featureidentifier123 /// \param objectId 124 /// Input The object identifier 125 125 /// \param fgfArray 126 126 /// Input A geometry in FGF format … … 129 129 /// Returns Nothing 130 130 /// 131 FDO_SPATIAL_API void InsertObject(FdoInt32 featId, FdoByteArray* fgfArray);131 FDO_SPATIAL_API void InsertObject(FdoInt32 objectId, FdoByteArray* fgfArray); 132 132 133 133 /// \brief … … 138 138 /// In Mode #3 the spatial index will be emptied. 139 139 /// 140 /// \param featId141 /// Input The featureidentifier.140 /// \param objectId 141 /// Input The object identifier. 142 142 /// \param ext 143 143 /// Input The bounding box of the feature. It may be NULL in which case … … 147 147 /// Returns Nothing 148 148 /// 149 FDO_SPATIAL_API void EraseObject(FdoInt64 featId, FdoIEnvelope *ext);149 FDO_SPATIAL_API void EraseObject(FdoInt64 objectId, FdoIEnvelope *ext); 150 150 151 151 /// \brief … … 163 163 /// \param marker 164 164 /// Input A marker returned by the Spatial index iterator 165 /// \param featId166 /// Output The featId165 /// \param objectId 166 /// Output The object identifier 167 167 /// \param iVertex 168 168 /// Output The index of the segment in the original geometry, 1-based … … 171 171 /// Returns Nothing 172 172 /// 173 FDO_SPATIAL_API void DecodeMarker(FdoInt64 marker, FdoInt32 & featId, FdoInt32 &iSegment);173 FDO_SPATIAL_API void DecodeMarker(FdoInt64 marker, FdoInt32 &objectId, FdoInt32 &iSegment); 174 174 175 175 /// \brief … … 241 241 == Remarks == 242 242 243 * The API proposes 3 usage modes. This provides maximum flexibility for various scenarios.244 * Mode 1 implements a regular spatial index, very performant 243 * The API proposes 3 usage modes. This provides maximum versatility for various scenarios. 244 * Mode 1 implements a regular spatial index, very performant. 245 245 * For mode 2 and 3 the client code has to implement a segment visitor in order to retrieve a segment from the geometry. 246 246 * This API is a wrapper over the R-tree implementation located in the Sqlite provider and developed by Traian Stanev.
