spatial-d4science/pip-requirements.txt

GeoAlchemy>=0.6
GeoAlchemy2==0.5.0
Shapely>=1.2.13
OWSLib>=0.19.0
lxml>=2.3
argparse
pyparsing>=2.1.10
requests>=1.1.0
future>=0.18.2
Support for automatic indexing of spatial extent (#1272) The spatial_query plugin now automatically checks for the existance of an 'spatial' extra when creating, updating or deleting a package and syncs its value (in GeoJSON format) with the geometry column of the package_extent table. The extension now uses GeoAlchemy, that makes performing spatial operation extremely easy. The geometry field has been updated to support multiple geometry types (Polygons, Points, MultiPolygons...) and the default srid has been set as WGS 84 lat/lon (EPSG:4326). 2011-09-29 16:40:49 +02:00			`GeoAlchemy>=0.6`
fix crash caused by new GeoAlchemy2 version This patch fixes an issue where new versions of GeoAlchemy2 caused crashes. We've locked the dependency to a known, working version. 2019-03-11 04:26:14 +01:00			`GeoAlchemy2==0.5.0`
Support for automatic indexing of spatial extent (#1272) The spatial_query plugin now automatically checks for the existance of an 'spatial' extra when creating, updating or deleting a package and syncs its value (in GeoJSON format) with the geometry column of the package_extent table. The extension now uses GeoAlchemy, that makes performing spatial operation extremely easy. The geometry field has been updated to support multiple geometry types (Polygons, Points, MultiPolygons...) and the default srid has been set as WGS 84 lat/lon (EPSG:4326). 2011-09-29 16:40:49 +02:00			`Shapely>=1.2.13`
update requirements 2020-01-30 15:51:48 +01:00			`OWSLib>=0.19.0`
[#34] Update lxml requirement Latest OWSLib introduces changes that require lxml>=2.3. 2013-08-14 14:14:55 +02:00			`lxml>=2.3`
Merged in ckanext-csw @44d5a04656dff084e6bca57dda7b63deec69778c. Not tested yet. 2012-10-17 17:59:02 +02:00			`argparse`
Update pip-requirements.txt 2017-03-01 10:11:46 +01:00			`pyparsing>=2.1.10`
[#2470] Allow newer requests versions. Tested with 2.7. Its only the WAF harvester that currently uses it, and that is only basic use. 2015-10-09 16:37:38 +02:00			`requests>=1.1.0`
Split plugins 2019-12-11 11:31:25 +01:00			`future>=0.18.2`