Improvements geospatial bucketizers

[ddvlanck]

1. Parsing WKT literal that contain extra information

In the case of https://marineregions.org/feed, the wkt literal contains extra information → <http://www.opengis.net/def/crs/OGC/1.3/CRS84> Polygon(180 -42.5802,179.87257 -42.5802,179.87257 -42.86535,180 -42.86535,180 -42.5802). The bucketizer fails to parse this wkt literal.

2. Add support for other geospatial types such as GML

At this moment, only WKT is supported

[ddvlanck]

Parsing WKT literals with the coordinate system present in the string is fixed. However, wkt literals with an invalid (?) location, e.g. <http://www.opengis.net/def/crs/OGC/1.3/CRS84> Point( ) are failing.

Should we implement behaviour that when failing to process the property path should result that the LDES member is added to a page, through the fallback mechanism?

[pietercolpaert]

Yes: we certainly need to be forgiving wrt parsing literals!