Introduction
This package provides the ability to assign geographical information to Dexterity-based (plone.app.dexterity) content types within Plone and does so using collective.geo.geographer and collective.geo.mapwidget.
By applying the behaviour Collective Geo Maps to a Dexterity content type, a Coordinates field becomes available when creating or editing said content.
This allows a user to either look-up coordinates for a place or feature via geo-coding, draw a geographical feature (such as a point, line or polygon) on a map, or enter details manually in Well-Known Text (WKT) format.
Collective.geo.behaviour also provides Collective Geo Styles behaviour. By this behaviour it is possible to customize the style of the features that will be displayed on the map for each content type.
Geographical information can be used by the rest of the collective.geo set of packages. For instance, the coordinates can be displayed on maps against Collections or Folders using collective.geo.kml.
Found a bug? Please, use the issue tracker.
Installation
This addon can be installed has any other addons, please follow official documentation.
About the Maps behaviour
The behaviour adds a coordinates field to the content type and uses a collective.z3cform.mapwidget widget in order to allow the user to manipulate the geographic information.
The behaviour effectively acts as a proxy to load and save the data into the relevant location by querying for an collective.geo.geographer.interfaces.IGeoreferenced adapter and collective.geo.geographer.interfaces.IWriteGeoreferenced respectively for the given context.
This means that changes made upon as edits to the content object and changes made in the Coordinates tab are both modifying exactly the same data.
Usage
Once your type configuration has the Collective Geo Maps behaviour applied, then content objects of said type will be marked as georeferenceable for collective.geo.geographer. This is achieved through the marker interface collective.geo.geographer.interfaces.IGeoreferenceable.
Through the web
If you are configuring your Dexterity-based type through the web-based interface, then proceed to edit your content type in the Dexterity Content Types control panel. Under the Behaviours tab you will find the Collective Geo Maps behaviour – select this and save your content type.
In the same way you could choose Collective Geo Styles in order to assing the other behaviour.
Upon adding or editing an object of your content type, you will see the new field accordingly.
Generic Setup (file system)
If you’ve created a file-system Dexterity type configuration, you need to specify the relevant interfaces as a behaviour:
collective.geo.behaviour.interfaces.ICoordinates collective.geo.behaviour.interfaces.IGeoFeatureStyle
and import or re-import your type configuration. As an example, a type configuration at ${product_dir}/profiles/default/types/my.datatype.xml would look like this:
<?xml version="1.0"?>
<object name="my.datatype"
meta_type="Dexterity FTI"
i18n:domain="tdh.metadata" xmlns:i18n="http://xml.zope.org/namespaces/i18n">
...
<property name="behaviors">
<element value="collective.geo.behaviour.interfaces.ICoordinates" />
<element value="collective.geo.behaviour.interfaces.IGeoFeatureStyle" />
</property>
...
</object>
Changelog
1.2 (2015-05-02)
Update translations [gborelli]
Added french translations [tiazma]
1.1 (2014-02-26)
Move robot tests to collective.geo.bundle and add dexterity test [gborelli]
Add Collective Geo Styles behavior to manage features’ style [gborelli]
Fix for custom style tab is not working properly [bogdangi]
Fix for issue https://github.com/collective/collective.geo.geographer/issues/5 [bogdangi]
Added German translation [href]
1.0 (2013-10-29)
Change package layout [gborelli]
Remove dependency on Grok [jianaijun]
1.0b2 (2013-06-02)
Nothing changed yet.
1.0b1 (2013-06-02)
Add install profile [gborelli]
Removed dependency from rwproperty [gborelli]
Unwrap behaviour context, it raises an error when Dexterity object is georeferenced [gborelli]
Removed Shapely dependency, added pygeoif [gborelli]
Added support for Spanish localization [macagua]
Added improvements about the Internationalization [macagua]
2 maintainers
Metadata
2 maintainers
Release files for collective.geo.behaviour 1.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.geo.behaviour-1.2.tar.gz | 24.3 kB | Without provenance | Details for collective.geo.behaviour-1.2.tar.gz |
Release files / collective.geo.behaviour-1.2.tar.gz
| Download URL | collective.geo.behaviour-1.2.tar.gz |
|---|---|
| Size | 24.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79d37555a861e5c1f4cd1aacd47f82695dfbfdc6b6e0b0e007b09002f1877de0
|
|
BLAKE2b-256 checksum How to use checksums |
a37b1a8186d13312f8c3f09d97ebf6f812a4908633952e9ab0bed63c2281ee70
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.geo.behaviour 1.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.
