28 | | TBD |
| 28 | This RFC proposes the following signatures for the new functions: |
| 29 | |
| 30 | double MinX(<geometry property>); |
| 31 | double MinY(<geometry property>); |
| 32 | double MinZ(<geometry property>); |
| 33 | |
| 34 | double MaxX(<geometry property>); |
| 35 | double MaxY(<geometry property>); |
| 36 | double MaxZ(<geometry property>); |
| 37 | |
| 38 | All of the above functions accept a geometry property only. The result of the functions depend on the provided geometry: |
| 39 | |
| 40 | if the provided geometry is a point geometry, the result of the Min/Max functions is the x, y, z values of the point |
| 41 | if the provided geometry is a line, the result of the Min/Max functions is the x, y, z values of the start and end points |
| 42 | if the provided geometry is a polygon, the result of the Min/Max functions is the x, y, z values of the start and end points of the exterior ring of the polygon |
| 43 | |
| 44 | 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). |