search

TREEcg / bucketizers

Bucketize Linked Data Event Stream members
MIT License
3 stars 2 forks source link

Improvements geospatial bucketizers #10

Open ddvlanck opened 3 years ago

ddvlanck commented 3 years ago

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 commented 3 years ago

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 commented 2 years ago

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