Introduction
Some web mapping clients like Leaflet or Polymaps accept json as an input format. This product produces it.
It does not have any user interface, it just provides a GeoJson view for contentitems, folders and collections. To test just append /@@geo-json.json to the url.
Links
Code repository: https://github.com/collective/collective.geo.json
Questions and comments to collectivegeo-discussion@lists.coactivate.org
Report bugs at https://github.com/collective/collective.geo.json/issues
Tests
This package is tested using Travis CI. The current status is :
Changelog
0.4.1 (2018-01-09)
Improve way to get title and description for collection and folder json view. [bsuttor]
0.4 (2018-01-05)
Add plone.app.contenttypes comptability. [bsuttor]
0.3 (2016-09-06)
Update way to get json, do not construct json into __call__ mehtod, so you can create/use json into other products without modify request. [bsuttor]
0.2 (2014-08-01)
Add plone.app.collection provider [bsuttor]
Add ATFolder provider (not only folder rich) [bsuttor]
Add collective.geo.contentlocations dependency because collective_geo_styles catalog index is required. [bsuttor]
Add tests. [bsuttor]
0.1 (2012/02/24)
Initial release
2 maintainers
Metadata
2 maintainers
Release files for collective.geo.json 0.4.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.json-0.4.1.tar.gz | 17.3 kB | Without provenance | Details for collective.geo.json-0.4.1.tar.gz |
Release files / collective.geo.json-0.4.1.tar.gz
| Download URL | collective.geo.json-0.4.1.tar.gz |
|---|---|
| Size | 17.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
fe824cb8ab737ffebf3f646f4146ccd95f57d82577b07f48bb2876bb84ffc64b
|
|
BLAKE2b-256 checksum How to use checksums |
bbec23774e4834917245bb40705ba75c796951aec2cded01982a6c805a8b8d66
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for collective.geo.json 0.4.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.
