Changes between Version 2 and Version 3 of FDORfc38

Timestamp:

Jul 8, 2009, 2:02:07 PM (15 years ago)

Author:

gregboone

Comment:

--

FDORfc38

@@ -33 +33 @@
 Modify the FDO SHP provider:
 
-* Change its capability setting to indicate that it supports multi-polygon geometry types.
-* On input of geometry, there is no further processing needed as the current code will save all input loops without checking whether they are outer or inner.
-* On read of geometry, the code should check the geometry to see if there are multiple loops. If there are multiple loops, determine if there are more than one outer loops. If so, change the output geometry type to FDO multi-polygon, otherwise, leave it as polygon with interior rings.
-* If any loops of a geometry are not closed, then the current behavior of not changing the geometry at all is followed. The geometry is returned as-is.
+    * Change its capability setting to indicate that it supports multi-polygon geometry types.[[BR]]
+    * On input of geometry, there is no further processing needed as the current code will save all input loops without checking whether they are outer or inner.[[BR]]
+    * On read of geometry, the code should check the geometry to see if there are multiple loops. If there are multiple loops, determine if there are more than one outer loops. If so, change the output geometry type to FDO multi-polygon, otherwise, leave it as polygon with interior rings.[[BR]]
+    * If any loops of a geometry are not closed, then the current behavior of not changing the geometry at all is followed. The geometry is returned as-is.[[BR]]
 
 == Implications ==
 
-* The code for this is mostly done, just turned off. We will need to measure the performance impact, but the extra processing would only apply for cases where there are multiple loops. The most common case of a single loop polygon would not be processed any differently and would not have a performance impact.
+    * The code for this is mostly done, just turned off. We will need to measure the performance impact, but the extra processing would only apply for cases where there are multiple loops. The most common case of a single loop polygon would not be processed any differently and would not have a performance impact.
 
-* The FDO geometry type will be corrected automatically on reading. The caller must expect either a polygon or a multi-polygon regardless of original geometry type on insert.
+    * The FDO geometry type will be corrected automatically on reading. The caller must expect either a polygon or a multi-polygon regardless of original geometry type on insert.
 
 == Test Plan ==
 
-* Enhance the unit test and add roundtripping fidelity tests.
-* Performance benchmarks on large datasets containing polygons with many interior rings.
+    * Enhance the unit test and add roundtripping fidelity tests.
+    * Performance benchmarks on large datasets containing polygons with many interior rings.
 
 == Funding/Resources ==