The approach using Solr's own BBoxField turned out to be not optimal as
it required the use of LocalParams. This is fine if the query is used in
`fq` but CKAN core does not allow it on `q` (unreasonably IMO). Long
story short the old implementation is a bit more verbose but supports:
* Proper spatial sorting
* Combining queries in `q` with a spatial filter
* Antimeridian queries handling
It doesn't support Point geometries, but users can use
`solr-spatial-field` if they need them
* cleanup bad chars from tags in harvester
* cleanup bad chars from tags in harvester - do safer config read
* use munge_tag to clear tags, code cleanup
* restored default tag truncate
* tests for clean tags
* removed hack for IHarvester.info()
* #188 cleanup
* #188#190 Add doc about harvester JSON config
* clean tags tests updated #188
* #188 test fixes
* #188 test fixes
* #188 test fixes
* #188 test fixes
* removed unused/bad code after review #188
* Keep old entry points for preview plugins so people does not need to
do python setup.py develop
* Version checks should be done including the min_version parameter,
otherwise they will fail for 2.4, 2.5...
* No need to define different methods for different interfaces. If
running eg 2.3, the IResourcePreview interface methods will simply be
ignored.
* Simplified same domain checking
* Add note about these being eventually migrated to ckanext-geoviews
* Added docs
No need to choose branches, we'll aim to keep master stable and working
with different ckan versions (We'll keep the stable and release-v2.0
branches up to date for the time being)
If using CKAN>=2.3 and GeoAlchemy2 is not installed an ImportError
will be raised with details about how to proceed. Added a section
on the Troubleshooting.
When creating a minimal custom theme users may start with a blank read.html file and include only the secondary_content block. This will fail, as the template needs to start with ckan_extends.