============
This Product adds a geospatial index to the zope catalog for collective.geo.
OOTB it only adds the index and a searchform, query_spatialcatalog.html,
which lets you explore the usage of the index. It is meant to be used in
custom products that need a spatial search.
It depends on the spatialindex and tools libraries from SpatialIndex.
You can find installation instructions for spatialindex on
http://trac.gispython.org/lab/wiki/Rtree.
Links
=====
- Code repository: http://svn.plone.org/svn/collective/collective.geo.index/
- Questions and comments to collectivegeo-discussion@lists.coactivate.org
- Report bugs at http://plone.org/products/collective.geo.index/issues
Changelog
=========
0.1 (2012/02/16)
-------------------
- Use jQuery to pick up the query's bounding box from the form input (rendered
and escaped with Plone already) rather than regex'ing the query string.
[davidjb]
- Add getEntryForObject method for spatial catalog index to allow viewing
ZCatalog records.
[davidjb]
- Zoom to bounding box extent on load, rather than the extent of data from
the query.
[davidjb]
- Initial release
Metadata
Release files for collective.geo.index 0.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| collective.geo.index-0.1.tar.gz | 23.2 kB | Without provenance | Details for collective.geo.index-0.1.tar.gz |
Release files / collective.geo.index-0.1.tar.gz
| Download URL | collective.geo.index-0.1.tar.gz |
|---|---|
| Size | 23.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
270ebf36f0ad6f2d86d613b22a8b02e490ac6b57df6ef174c9f18133a14124a0
|
|
BLAKE2b-256 checksum How to use checksums |
b72abe5b67096086efea284168698dbcc85406a42c91c56e2317753be7e7a960
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.geo.index 0.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.