Adrià Mercader

@ebuckley this looks great, it would be great if you could update the tests (and test this new behaviour) thanks

@raymedia The `spatial` extra field currently only supports GeoJSON [geometry](http://geojson.org/geojson-spec.html#geometry-objects) objects, not the higher level feature ones. If you have a way to extract it from the `FeatureCollection` just pass...

@torfsen Several things involved here. Regarding `GeometryCollection` support: - This is the [code](https://github.com/ckan/ckanext-spatial/blob/master/ckanext/spatial/lib/__init__.py#L52:L59) that is complaining about GeometryCollections not being supported. It is the [shapely](https://github.com/Toblerity/Shapely) library, which at the time...

Agree on all points @torfsen. Let's leave this for reference in case someone can work on this in the future.

@FuhuXia can you point me to an ISO doc where this is failing? thanks

Wow, that's disappointing, I totally missed any previous announcement. That's bound to affect many people as MapQuest was the default option on all spatial widgets. It looks like the way...

BTW does anyone know of a free alternative to use as default tiles?

I summarized the available options (Excerpt from https://lists.okfn.org/pipermail/ckan-dev/2016-July/010124.html) You can provide a working alternative right now without any code change, just by configuring an [alternative base layer](http://docs.ckan.org/projects/ckanext-spatial/en/latest/map-widgets.html). The recommended options...

@jayhuggins you don't need to change the source code to access these tiles, have a look above for the relevant config options

The spatial search widget should definitely be able to be moved to a separate location like the homepage. The only thing the widget does is generate the url parameters needed...