Geokey-epicollect

Latest version: v1.0.3

Safety actively analyzes 613482 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

1.0.3

We officially now be supporting only GeoKey v1.6+ because of Django v1.11 support ⭐️

This patch also adds README to [PyPI deployment](https://pypi.org/project/geokey-epicollect/).

1.0.2

Fixed includes in the manifest, before not including templates when installing via PyPI.

1.0.1

Fixed scheme in the URL of the EpiCollect project (correctly using http/https).

1.0.0

Full stable release.

0.2.2

Improvements to be able to run with GeoKey and Django 1.9 (optionally). Although, Django 1.8 is still preferred to be used with GeoKey.

0.2.1

- Fixes [5](https://github.com/ExCiteS/geokey-epicollect/issues/5): Returns an error if latitude or longitude are not set
- Fixes [12](https://github.com/ExCiteS/geokey-epicollect/issues/12): When is not set or a non-existing category id is used, an error is return to the client.
- Fixes [13](https://github.com/ExCiteS/geokey-epicollect/issues/13): `Location` field is now required by default
- Fixes [14](https://github.com/ExCiteS/geokey-epicollect/issues/14): Returns an error if the a file with the file name has not been registered with the contribution.
- Allows uploads of files with `full_image` flag, instead of `thumbnail` only

Links

Releases

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.