Introduction
Dexterity based behaviors for geotagging.
Implements plone.formwidget.geolocation which adds LeafletJS support.
Adds catalog indexes/metadata for latitude/longitude to support GeoJSON Featurelist output/filtering.
The GeoJSON properties can be customized with the provided IGeoJSONProperties adapter.
Changelog
1.7.2 (2021-09-16)
Fix Italian .po file location [laulaz]
Add French translation [laulaz]
1.7.1 (2020-07-10)
Do not use autoinclude for ZCML, load explicit. [jensens]
1.7.0 (2019-12-09)
Make geolocation language independent [agitator]
1.6.0 (2019-04-24)
Add IGeoJSONProperties adapter. [petschki]
Add latitude/longitude indexer. [petschki]
Add uninstall profile. [petschki]
Prepare testing environment. [petschki]
1.5.1 (2017-04-04)
Explicitly include necessary zcml dependencies to avoid having to explictly doing that in tests. plone.app.testing disables z3c.autoinclude. [thet]
1.5 (2016-10-06)
Register the collective.geolocationbehavior.geolocation.IGeolocatable behavior under the name geolocatable. Do not bind for because its superfluos. [thet, jensens]
Code cleanup, remove BBB classes. [thet]
1.4 (2015-07-15)
Install the plone.formwidget.geolocation default profile in order to get Leaflet map support. [thet]
Fix upgrade step with broken persistent classes and re-create BBB class definitions for upgrading. Reindex the object while upgrading to get updated object_provides indexes. [thet]
1.3.2 (2015-03-04)
Fix the import bug, introduced of previous commit.
1.3.1 (2015-03-04)
Fix import of GeolocationField.
1.3 (2015-03-04)
Remove browserlayer, which isn’t needed any more. Includes an Upgrade step. [thet]
Switch to Attribute storage instead of Annotation storage. This is easier to access and needs less ZODB unpickling. It’s unlikely that two behaviors share the same geolocation schema name. A upgrade step is provided. [thet]
Removed code related to Google Maps integration. The integration is better done with Mockup Javascript. [thet]
PEP8. [thet]
1.2 (2014-04-30)
Add italian translation [gborelli]
Remove dependency on Products.Maps and copy some of it’s interfaces to here. Note, Google Map integration is not available at this point. For mapping functionality I suggest to backport the Leaflet integration from collective.venue. [thet]
Remove dependency on Grok and use Dexterity 2 way with plone.supermodel to define the schema. [thet]
1.1.0.2 (2012-09-21)
1.1 was somehow broken again
1.1 (2012-09-21)
Fix egg, add authors
1.0 (2012-09-21)
Initial release
Release files for collective.geolocationbehavior 1.7.2
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.geolocationbehavior-1.7.2.tar.gz | 18.7 kB | Without provenance | Details for collective.geolocationbehavior-1.7.2.tar.gz |
Release files / collective.geolocationbehavior-1.7.2.tar.gz
| Download URL | collective.geolocationbehavior-1.7.2.tar.gz |
|---|---|
| Size | 18.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2ee9597d52cd90ced1824857fbc2f8c74f979a983fd6c6f9f9885ffad21ec6e4
|
|
BLAKE2b-256 checksum How to use checksums |
8888ddcfa8ae57a5a0ef635c3d954fdde1cab183ecfe279834adcdeb8fd77054
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/3.4.1 importlib_metadata/4.0.1 pkginfo/1.7.0 requests/2.25.1 requests-toolbelt/0.9.1 tqdm/4.60.0 CPython/3.8.9
|
Security for collective.geolocationbehavior 1.7.2
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.
