Changes between Version 5 and Version 6 of rfc41_multiple_geometry_fields

Timestamp:

Jul 27, 2013, 11:29:34 AM (11 years ago)

Author:

Even Rouault

Comment:

add ODsCCreateGeomFieldAfterCreateLayer capability

rfc41_multiple_geometry_fields

@@ -224 +224 @@
 
 {{{
-        virtual OGRErr GetExtentEx(int iGeomField, OGREnvelope *psExtent,
-                                   int bForce = TRUE);
+        virtual OGRErr GetExtent(int iGeomField, OGREnvelope *psExtent,
+                                 int bForce = TRUE);
 }}}
     Default implementation would call GetExtent() if iGeomField == 0
@@ -257 +257 @@
   * CreateLayer() : signature will be unchanged. If more than one
     geometry fields are needed, OGRLayer::CreateGeomField() must be used.
-    If the name of the first geometry field must be specified, for drivers
-    supporting OLCCreateGeomField, using code should call CreateLayer() with
-    eGType = wkbNone and then add all geometry fields with
+    If the name of the first geometry field must be specified, for datasources
+    supporting ODsCCreateGeomFieldAfterCreateLayer, using code should call
+    CreateLayer() with eGType = wkbNone and then add all geometry fields with
     OGRLayer::CreateGeomField().
 
@@ -269 +269 @@
     on the returned layer object. So there is no real need for adding a way
     of specifying the geometry field at the ExecuteSQL() API level.
+
+  * TestCapability(): add a ODsCCreateGeomFieldAfterCreateLayer capability
+    to inform if CreateGeomField() is implemented after layer creation.
 
 == Explored alternative solutions ==