solr is based on bounding boxes, both in the geometries indexed and and the input query geometries, and it doesn't actually use any spatial library underneath, just math operations performed on values indexed. This could be replaced by the BBoxField which provides the same functionality in Solr
solr-spatial-field is based on actual spatial operations powered by JTS (or Geo3D) in Solr, using the SpatialRecursivePrefixTreeFieldType or RPT field type. It supports points, polygons and bboxes so we can probably combine both modes of operation.
Things to explore:
RPT might require and additional LatLonPointSpatialField for sorting (see note in RPT
Solr supports WKT for indexing geometries, can we support it in our spatial field?
It would be interesting to provide a mechanism for extensions to index geometries that are not stored in the spatial field, eg from a lookup table, to avoid storing big values in the dataset metadata. Maybe this is just a matter of providing a pattern for overriding the before_dataset_index() method
A pre-built Docker image will be provided to facilitate the installation and usage, as well to be able to write tests against a spatially enabled version. See https://github.com/ckan/ckan-solr/pull/5
Solr documentation: https://solr.apache.org/guide/8_11/spatial-search.html
The Postgis search option will be dropped.
Of the other two remaining ones:
solris based on bounding boxes, both in the geometries indexed and and the input query geometries, and it doesn't actually use any spatial library underneath, just math operations performed on values indexed. This could be replaced by theBBoxFieldwhich provides the same functionality in Solrsolr-spatial-fieldis based on actual spatial operations powered by JTS (or Geo3D) in Solr, using theSpatialRecursivePrefixTreeFieldTypeor RPT field type. It supports points, polygons and bboxes so we can probably combine both modes of operation.Things to explore:
LatLonPointSpatialFieldfor sorting (see note in RPTspatialfield?spatialfield, eg from a lookup table, to avoid storing big values in the dataset metadata. Maybe this is just a matter of providing a pattern for overriding thebefore_dataset_index()methodA pre-built Docker image will be provided to facilitate the installation and usage, as well to be able to write tests against a spatially enabled version. See https://github.com/ckan/ckan-solr/pull/5