Overview
collective.geo allows to geo-reference Plone content types and to display this information over a map.
The core of collective geo is composed by the following packages:
- collective.geo.geographer
provides geo annotation for Plone. (repository)
- collective.geo.openlayers
enables openlayers machinery into Plone. (repository)
- collective.geo.settings
provides some utilities where settings of collective.geo packages can be stored (repository)
- collective.geo.mapwidget
provides some handy page macros and adapters to easily manage multiple maps on one page. (repository)
- collective.z3cform.mapwidget
provides a mapwidget for z3c.form framework. (repository)
- collective.geo.contentlocations
provides a GUI for collective.geo.geographer. It provides some simple forms to add geographical coordinates to Plone content types. (repository)
- collective.geo.kml
provides KML views for georeferenced objects, allowing Plone content types to be visualized in Google Earth. (repository)
To display the maps, collective.geo takes advantage of Openlayers, a JavaScript library for displaying map data in web browsers, with no server-side dependencies.
As a default map source we can select OpenStreetMap, Google Maps or Bing Maps.
Requirements
BeautifulSoup (geopy)
geopy >=0.98
Plone >= 4.2
collective.geo.kml >= 3.2
collective.geo.behaviour >= 1.2
Installation
This addon can be installed has any other addons, please follow official documentation.
Upgrade
To upgrade collective.geo go to in the Plone Site Setup > Addon.
When an upgrade is available a button will appear next to Plone Maps (collective.geo) product. Click the button to upgrade.
Documentation
The package is documented at collectivegeo.readthedocs.org. The sourcecode for this documentation resides in the docs folder of this package, please contribute.
Contributors
Giorgio Borelli - gborelli
Silvio Tomatis - silviot
Gerhard Weis - gweis
David Beitey - davidjb
Adam Tang - adam139
Christian Ledermann - cleder
Leonardo J. Caballero G. - macagua
Metrics
Changelog
2.3 (2015-05-02)
Update requirements [gborelli]
Remove c.geo.behavior as extra requires and include it as default [gborelli]
2.2 (2014-08-16)
Updated c.geo.mapwidget to 2.1.3 [gborelli]
Updated version and year of collective.geo docs [macagua]
Added documentation about collective.geo.usersmap [macagua]
Added documentation about collective.geo.flexitopic [macagua]
2.1 (2014-02-26)
Moved robot test from c.geo.behaviour [gborelli]
2.0 (2013-10-29)
Added robotframework tests [gborelli]
Added Sphinx documentation [gborelli]
Added travis-ci configuration [gborelli]
Added extras_requires in setup.py to use g.ceo with Dexterity [gborelli]
Added buildout configuration
Refacrtorized package structure [giacomos]
0.1 (2011-03-06)
First release
3 maintainers
Metadata
3 maintainers
Release files for collective.geo.bundle 2.3
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.bundle-2.3.tar.gz | 3.0 MB | Without provenance | Details for collective.geo.bundle-2.3.tar.gz |
Release files / collective.geo.bundle-2.3.tar.gz
| Download URL | collective.geo.bundle-2.3.tar.gz |
|---|---|
| Size | 3.0 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cd62064a79ebe3756df866b2aaf54ab722c5fd35d864546141fcb781eccc7cab
|
|
BLAKE2b-256 checksum How to use checksums |
c4f93ad6b03c02cf53ee595a1a6967a38a773cfe10828727f143eb96e0550ff4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.geo.bundle 2.3
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.
