You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ckanext-spatial is an old extension and hasn't had a big refactoring in a long while. Postgis and other python requirements make it difficult to install and deploy. In addition, the spatial search capabilities in Solr have evolved significantly since the current implementation and both indexing and querying can be greatly simplified in ckanext-spatial.
Refactor search logic. Use modern Solr fields to support the existing backend modes (solr for bboxes and solr-spatial-field for polygons, points, etc), they can be probably merged into a single implementation. Write actual Solr based tests. See Refactor spatial search to use modern Solr options #291
This work could be tagged as v2.0.0, and ideally will only target CKAN 2.9+ in Python 3, although we can re-assess this when we know the scope of the changes
@amercader I think #289 could be part of this mayor change.
I assume you want to take care of this, but let me know if I have to do any of the work. Maybe start building version 2.0.0 for Python 3.
ckanext-spatial is an old extension and hasn't had a big refactoring in a long while. Postgis and other python requirements make it difficult to install and deploy. In addition, the spatial search capabilities in Solr have evolved significantly since the current implementation and both indexing and querying can be greatly simplified in ckanext-spatial.
The main areas of work will be:
solr
for bboxes andsolr-spatial-field
for polygons, points, etc), they can be probably merged into a single implementation. Write actual Solr based tests. See Refactor spatial search to use modern Solr options #291This work could be tagged as
v2.0.0
, and ideally will only target CKAN 2.9+ in Python 3, although we can re-assess this when we know the scope of the changescc @avdata99
The text was updated successfully, but these errors were encountered: