This work is based on the ol.expr package by @tschaub.
It adds a few named expression functions to that package:
* INTERSECTS, CONTAINS, DWITHIN, WITHIN (no client-side implementation as yet)
* LIKE (like comparison with wildcard, singleChar and escapeChar)
* IEQ (case-insensitive equality)
* INEQ (case-insensitive non-equality)
It also adds a few extra parameters to the existing EXTENT function to be able
to deserialize and serialize all info (i.e. projection and property name).
Some changes were needed for the GML parser as well:
* createGeometry function needed to be public
* when parsing Box (GML2) and Envelope (GML3) also parse the srsName
* fix up writing for Box and Envelope now that bounds is an array
Also added createDocumentFragment function to the XML parser. Implementation
is similar to OpenLayers 2.
Some addtional notes on the implementation:
* PropertyIsBetween was implemented as an ol.expr.Logical with operator
ol.expr.LogicalOp.AND and two ol.expr.Comparison instances with operator
ol.expr.ComparisonOp.GTE and ol.expr.ComparisonOp.LTE
* In OGC Filter And and Or can contain more than 2 sub filters, so this
is translated into a hierarchy of ol.expr.Logical
This was previously called getTransformFeatureInfo, which is a method instead of an option. In addition, the generate-exports.py script does not properly export properties whose names appear on a different line than the @property annotation. This makes the vector-layer.html, kml.html, and gpx.html examples work with the built lib.
In combination with a (not yet implemented) `Symbolizer#isLiteral` method, calling `Symbolizer#evaluate` without a feature is the fast track for rendering batches of like-styled features. This change also simplifies the handling of undefined symbolizer literal properties (where stroke or fill properties are optional).
The canvas vector layer still has the (API candidate) `getFeatures` method that accepts an arbitrary expression (was filter). This, and the `getFeaturesObject` method under it are only used in the tests. The rendering code that was using filters is now calling `layer.getFeaturesObjectForExtent` with an explicit extent and optional geometry type.
Bart van den Eijnden
Tim Schaub
Éric Lemoine
Frédéric Junod
Éric Lemoine