Changes between Version 4 and Version 5 of FDORfc39


Ignore:
Timestamp:
Jun 24, 2009, 12:19:41 PM (15 years ago)
Author:
danstoica
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • FDORfc39

    v4 v5  
    1 = FDO RFC 39 - =
     1= FDO RFC 39 - Spatial operator combinations support =
    22
    33This page contains an change request (RFC) for the FDO Open Source project. 
     
    39392) Assign values to FdoSpatialOperations so they can be bitmapped:
    4040
     41
     42{{{
    4143enum FdoSpatialOperations
    4244{
     
    4446    FdoSpatialOperations_Relate     = 0x0001, 
    4547    FdoSpatialOperations_Contains   = 0x0002,
    46     FdoSpatialOperations_Crosses    = 0x0004, 
     48    FdoSpatialOperations_Crosses    = 0x0004,
    4749    FdoSpatialOperations_Disjoint   = 0x0008,
    4850    FdoSpatialOperations_Equals     = 0x0010,
     
    5456    FdoSpatialOperations_Inside     = 0x0400
    5557};
     58}}}
    5659
    57603) Enhance FdoSpatialCondition to handle a bitmapped mask of spatial operators. Avoid creating a new set of constructors just for RELATE by adding a extra optional parameter to existing constructors. Add setter and getter for the mask.
    5861
     62
     63{{{
    5964class FdoSpatialCondition : public FdoGeometricCondition
    6065{
     
    8489    FDO_API FdoInt32 GetRelateMask();
    8590}
     91}}}
    8692
    87934) Provide a common implementation for computing the pattern matrix in FdoSpatialUtility:
    8894
     95
     96{{{
    8997class FdoSpatialUtility
    9098{
     
    104112    ///
    105113    FDO_API static FdoString* GetOGSPatternMatrix(FdoInt32 value);
    106 
    107 
     114}}}
    108115
    109116== Implications ==