Changes between Version 3 and Version 4 of RFC59-Draft


Ignore:
Timestamp:
Aug 6, 2010, 8:56:40 AM (14 years ago)
Author:
sdlime
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • RFC59-Draft

    v3 v4  
    77
    88A principle motivation for this work is to support OGC filter expressions in a single pass in a driver-independent manner.
     9
     10All of the work detailed here is being prototyped in a sandbox, visit:
     11
     12  [http://svn.osgeo.org/mapserver/sandbox/sdlime/common-expressions/mapserver]
    913
    1014== Existing Expression Parsing ==
     
    6771'''Extending the Yacc grammar to support spatial operators'''
    6872
    69 The mapserver.h definitions above allow for using shapeObj's within the Yacc grammar. There are two types of shape-related tokens: 1) a shape binding, that is, a reference to the geometry being evaluated and 2) shape literals, shapes described as WKT within the expression string. For example:
     73The mapserver.h definitions above allow for using shapeObj's within the Yacc grammar (we also define a shapeObj as a new base token type within mapparser.y). There are two types of shape-related tokens: 1) a shape binding, that is, a reference to the geometry being evaluated and 2) shape literals, shapes described as WKT within the expression string. For example:
    7074
    7175{{{
     
    7781}}}
    7882
     83We can use these tokens in the grammar to implement all of the MapServer supported (via GEOS) logical operators.
    7984
    8085== Backwards Compatibility Issues ==