filter: Same as above we need to add URLencode, but in addition here more can be added to facilitate user's life. Indeed this parameter is supposed to receive OGC filter encoded as text/xml. ows4R provides bindings to generate these filters, eg.
Encoding to xml requires $encode() to the filter. A user that wants to specify such a filter will have to encode it, coerce it to character and URL-encode it. This is too much, and all this should be done transparently by ows4R.
The purpose of this enhancement is to facilitate the use of filtering params in WFS:
cql_filter: In most of cases this filter needs to be URL-encoded. By adding this, we avoid the user to specify URLencode by (him/her)self.wfs$getFeatures(cql_filter = "property = 'value'")instead of
wfs$getFeatures(cql_filter = URLencode("property = 'value'"))filter: Same as above we need to add URLencode, but in addition here more can be added to facilitate user's life. Indeed this parameter is supposed to receive OGC filter encoded as text/xml. ows4R provides bindings to generate these filters, eg.OGCFilter$new( PropertyIsEqualTo$new("property", "value") )Encoding to xml requires
$encode()to the filter. A user that wants to specify such a filter will have to encode it, coerce it to character and URL-encode it. This is too much, and all this should be done transparently by ows4R.wfs$getFeatures(filter = OGCFilter$new( PropertyIsEqualTo$new("property", "value") ))instead of
wfs$getFeatures(filter = URLencode(as(OGCFilter$new( PropertyIsEqualTo$new("property", "value") )$encode(), "character")))