Changes between Initial Version and Version 1 of FDORfc11

Timestamp:

09/06/07 14:26:23 (17 years ago)

Author:

thomasknoell

Comment:

--

FDORfc11

@@ +1 @@
+
+
+= FDO RFC 11 -  Adding Geometric Expression Functions =
+
+This page contains a request for comments document (RFC) for the FDO Open Source project.  
+More FDO RFCs can be found on the [wiki:FDORfcs RFCs] page.
+
+== Status == 
+ 
+||RFC Template Version||(1.0)|| 
+||Submission Date||Aug 03, 2007||
+||Last Modified||Thomas Knoell [[Timestamp]]||
+||Author||Thomas Knoell||
+||RFC Status||Draft||
+||Implementation Status ||Under Development||
+||Proposed Milestone||3.3.0.0||
+||Assigned PSC guide(s)||Greg Boone||
+||'''Voting History'''||  ||
+||+1||||
+||+0||||
+||-0||||
+||-1||||
+ 
+== Overview ==
+
+This RFC follows from RFC 8 by adding two geometric functions. RFC 8 laid the foundation for a common set of functions that providers could support. That RFC left out two commonly used geometric functions, ''Area()'' and ''Length()''. This RFC adds those two functions. A reason for adding these functions in a separate RFC is that there are coordinate system considerations that need to be defined and discussed that do not apply to the list of functions in RFC8. Many providers do not include a coordinate system library internally (e.g. SHP, SDF) while other providers (e.g. Oracle) do include a coordinate system library. ''Area()'' and ''Length()'' calculations on geometry with geodetic coordinate systems require a coordinate system library to do the spheroid-based calculations to provide correct results. While most coordinate system libraries include a distance calculation on the spheroid, most do not include area calculation on the spheroid. It is the proposal of this RFC that providers that do not use coordinate system libraries simply return simple calculations directly against the lat/long data (i.e. using Euclidian geometry based calculations). We would like feedback from the discussion list on the handling of this.
+
+
+== Signatures ==
+This RFC proposes the following signatures for the geometric functions Area and Length:
+
+'''!FdoDouble Area (<geometry property>);'''
+
+'''!FdoDouble Length (<geometry property>);'''
+
+
+Both functions accept a geometry property only. The result of the functions depend on the provided geometry:
+
+''AREA()'':
+ * if the provided geometry is a line or point geometry, the result is 0.
+ * if the provided geometry is a polygon, area is the result of the area of the exterior loops minus the area of the interior loops.
+
+''LENGTH()'':
+ * if the provided geometry is a point geometry, the result is 0
+ * if the provided geometry is a line, the result is the length of the object
+ * if the provided geometry is a polygon, the result is the length of the perimeter which includes all exterior and interior loops.
+
+For non-geodetic systems and if the provider is ignoring the handling of geodetic coordinate systems, the function ''Length()'' will return XY units while ''Area()'' will use the square of the length units. If the provider has a coordinate system library for geodetic coordinate systems, the length will be expressed in meters, the area in square meters.
+
+It should also be noted that the functions execute 2D calculations only. Therefore, if an object is defined in space, the functions should not be used to determine the area or length of such an object.
+
+Like the standard functions listed in RFC 8, the user can get access to the geometric function definitions via the FDO interface ''!GetWellKnownFunctions''. The new functions will be categorized as geometry functions (''!FdoFunctionCategoryType_Geometry'').
+
+
+=== Example ===
+
+Assuming that a class ''Road'' has a geometry property named ''geom'', a call to ''Length(geom)'' will return the length of a road object.
+
+
+== Affected Providers ==
+
+This enhancement will affect the following providers: ArcSDE, MySQL, SDF and SHP.
+
+
+== Required FDO Enhancements ==
+
+No FDO enhancements are required.
+
+
+== Implications ==
+
+This change will not cause any side-effects. No existing provider needs to change unless the provider wants to expose the new capability.
+
+== Test Plan ==
+
+Existing unit tests will be enhanced to test those changes.
+
+== Funding/Resources ==
+
+Autodesk to provide resource / funding to implement the feature for the affected providers.
+