-
Notifications
You must be signed in to change notification settings - Fork 6
Datasets are not searchable by location #523
Comments
If we stop rolling up extras and use valid GeoJSON polygons for {
"type":"Polygon",
"coordinates":[
[[2.05827, 49.8625],[2.05827, 55.7447], [-6.41736, 55.7447], [-6.41736, 49.8625], [2.05827, 49.8625]]
]
} Then the search function works: |
To make datasets geo-searchable we need to fix/transform the old spatial data already included in the dataset To QA this is required to fix the spatial data in datasets to make them searchable. |
@avdata99 Is this ready to be moved to QA? |
All deployed to the sandbox.
|
Probable related to ckanext-spatial#218 |
The fields
are not present in schema.xml on the sole server. This is the cause of the error. |
I added the fields manually in the schema.xml file and the error disappears. The geo fields live in the schema.xml file and this file is copied with ansible
I updated Solr in catalog-next for sandbox
Log:
This rolled back my changes and delete the manually added geo fields If I run the command a second time
I assume the file is updated but we have a bad version so I created a new PR |
Working in the sandbox How to QA?
|
Related to #511
How to reproduce
Expected behavior
Should return datasets from that location
Actual behavior
Always returns 0 datasets
The text was updated successfully, but these errors were encountered: