spatial-d4science/pip-requirements.txt

GeoAlchemy>=0.6
Shapely>=1.2.13
# Temporal requirement until there is an OWSLib release
# that requires python-dateutil<2.0
-e git+https://github.com/geopython/OWSLib.git@4b0a62cd37a5a03aafc5c0cd9606e0658d5ac664#egg=owslib
lxml>=2.3
argparse
pyparsing==1.5.6
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`
			`Shapely>=1.2.13`
Modify OWSLib requirement to prevent conflicts We will target a specific changeset of OWSLib for the time being, just until there is a proper release which includes geopython/OWSLib@4b0a62cd. Basically OWSLib required python-dateutil==2.1, which is intended for Python 3 and conflicted with the version used by CKAN core. 2013-08-13 12:53:22 +02:00			`# Temporal requirement until there is an OWSLib release`
			`# that requires python-dateutil<2.0`
			`-e git+https://github.com/geopython/OWSLib.git@4b0a62cd37a5a03aafc5c0cd9606e0658d5ac664#egg=owslib`
[#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`
[#14] Add pyparsing requirement. Fixes #14 2013-03-14 18:47:57 +01:00			`pyparsing==1.5.6`