Adrià Mercader

If you are using the `solr-spatial-field` backend for the spatial search, and your geometry is a valid `MultiPolygon`, the search should work just fine. This extent works for me (by...

@benjwadams you are right that the parser used in WAF is very brittle. Any improvements on that front would be a great contribution

@jbrown-xentity It's been a long time since I worked on this but IIRC the harvesters call `package_delete` to delete a dataset, which will mark it as `deleted` but leave it...

I agree with @davidread that the use case for this is very specific. Another option if you don't want to add the extra complexity of displaying/hiding the coordinate fields is...

I think it might be useful so happy to get it in. But I think it should have at least some basic tests. Can you have a look at `test_harvest.py`...

You can choose a different validator that is perhaps more flexible. There are different profiles [available](https://github.com/ckan/ckanext-spatial/tree/master/ckanext/spatial/validation/xml), and here you can read about how to configure it: http://docs.ckan.org/projects/ckanext-spatial/en/latest/harvesters.html

This looks good. I'll wait until the tests are fixed on master to double check is not breaking anything and I'll merge it.

I'm pretty sure we can upgrade the ckanext-spatial requirement to align it with pycsw, but I haven't work on the harvesters for a long time. Do you think there will...

@kalxas Apologies for the really late answer Just to understand how this works, (sorry if I'm a bit slow), is your goal: 1. hide the parent "collection records" from the...

A bit of refactoring on `plugin.py` to not initialize the tables or store the extent if not using the `postgis` backend should be enough. And ideally add some tests using...