You are here: Home

Modified items

All recently modified items, latest first.
RPMPackage collective.geo.mapcontent-0.1-1.lbn25.noarch
This is a very small and lightweight integration of OpenLayers and collective.geo.mapwidget. Idea is to have a map content type to create full customizable maps with the collective.geo flexibility. And the final goal is to store some javascript boilerplate on a content type to initiliaze the map. As it requires writing some javascript with OpenLayers and jquery, it is not an 'end user' solution but a convenient and flexible way to integrate OpenLayers in plone.
RPMPackage collective.geo.leaflet-0.2.3-1.lbn25.noarch
This package use the collective.geo.* suite with leaflet. How to add baseLayer ==================== What is a leaflet baseLayer : http://leafletjs.com/examples/layers-control.html In Plone, if you want to add a baseLayer, you have to add a subscriber on collective.geo.geographer.interfaces.IGeoreferenced (for exemple, in `configure.zcml`):: <subscriber for="collective.geo.geographer.interfaces.IGeoreferenced" provides="collective.geo.leaflet.interfaces.IMapLayer" factory=".maplayers.OpenStreetMap /> After, create your factory in python (`maplayers.py`):: from collective.geo.leaflet.maplayers import MapLayer from Products.Five.browser.pagetemplatefile import ViewPageTemplateFile class OpenStreetMap(MapLayer): name = u"osm" title = _(u"Open Street Map") index = ViewPageTemplateFile('browser/layers/osm.pt') And add your javascript into a template file `osm.pt`:: <script type="text/javascript"> var osmAttrib = '&copy; <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'; var osmUrl = 'http://{s}.tile.osm.org/{z}/{x}/{y}.png'; var %(name)s = L.tileLayer(osmUrl, { attribution: osmAttrib, }); </script>
RPMPackage collective.geo.kml-3.2-1.lbn25.noarch
collective.geo.kml provides KML views for georeferenced objects, allowing Plone containers and collections to be visualized in Google Earth. It also provides a map view to Plone Folder and Topic content types to display kml data.
RPMPackage collective.geo.json-0.3-1.lbn25.noarch
Some web mapping clients like leaflet or polymaps only 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 at the url.
RPMPackage collective.geo.index-0.1-1.lbn25.noarch
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
RPMPackage collective.geo.geopoint-0.1-1.lbn25.noarch
collective.geo.geopoint provides some generic classes for collective.geo.* packages.
RPMPackage collective.geo.geographer-2.1-1.lbn25.noarch
collective.geo.geographer provides geo annotation for Plone. This package is based on Sean Gillies's idea (zgeo.geographer) and integrates its functionalities in collective.geo project.
RPMPackage collective.geo.flexitopic-0.5-1.lbn25.noarch
Use collective.geo.flexitopic to easily build interactive maps out of plone collections. It combines plone maps (collective.geo) with collective.flexitopic. collective.flexitopic Flexitopic integrates the easy use of plone collections with a Flexigrid AJAX view. The criteria from the topic are taken to construct a simple query form to narrow down a search inside a collection. For old style colletions subtopics are displayed inside tabs of the collection. Flexitopic does not install a new content type but just adds an additional view to the collection type. it degrades for non javascript browsers to a simple table - (almost) same usability, no information loss. it requires JQuery only (built into plone 4) no JQueryUI lightweight JS Flexigrid: 24 KB packed JSlider: 15 KB packed
RPMPackage collective.geo.file-0.6-1.lbn25.noarch
collective.geo.file provides a view for KML, KMZ (Keyhole Markup Language) and GPX (GPS eXchange Format) files. The view renders the file in a openlayers Map using the collective.geo library. The product does not introduce a content type but adds an additional view to the Archetypes file and collection type. When you upload a file with the correct mimetype 'application/vnd.google-earth.kml+xml' (i.e with the extension *.kml), 'application/vnd.google-earth.kmz' (extension *.kmz) or 'application/gpx+xml' (i.e. with the extension *.gpx) the map view will be applied by default. KML, KMZ and GPX files are displayed in the KML Openlayers View of collections and Folders
RPMPackage collective.geo.fastkml-0.3-1.lbn25.noarch
collective.geo.fastkml replaces the template based generation of collective.geo.kml with the objectoriented approch of fastkml collective.geo.fastkml does support Polygons and MultiPolygons with holes. Depending how many holes your polygons have it may take longer to generate you KML file with collective.geo.fastkml (as collective.geo.kml ignores the holes). Generally collective.geo.fastkml is slightly faster than collective.geo.kml and produces smaller files. The style for polygons is created from the linestyle and polygonstyle so polygons can have an outline that is diffrent from the polygon fill style collective.geo.fastkml does not have an interface of its own, it just overrides the kml-document view of collective.geo.kml.collective.geo.fastkml replaces the template based generation of collective.geo.kml with the objectoriented approch of fastkml collective.geo.fastkml does support Polygons and MultiPolygons with holes. Depending how many holes your polygons have it may take longer to generate you KML file with collective.geo.fastkml (as collective.geo.kml ignores the holes). Generally collective.geo.fastkml is slightly faster than collective.geo.kml and produces smaller files. The style for polygons is created from the linestyle and polygonstyle so polygons can have an outline that is diffrent from the polygon fill style collective.geo.fastkml does not have an interface of its own, it just overrides the kml-document view of collective.geo.kml.
RPMPackage collective.geo.exif-0.1-1.lbn25.noarch
This Product extracts latitude and longitude out of the EXIF informations of an Image and sets its coordinates to them. The placemark marker is set to the images thumbnail. It extracts the information when an image is added or you can call it manually by appending /@@extract_exif_geoannotations.html to its url. You may also mass annotate all contents of a folder or an entire site by calling this view on a folder or the site root.
RPMPackage collective.geo.contentlocations-3.1-1.lbn25.noarch
collective.geo.contentlocations is a GUI for collective.geo.geographer. It provides some simple forms to add geographical coordinates and associated settings to Plone content types.
RPMPackage collective.geo.cesium-0.1-1.lbn25.noarch
Cesium view for collective.geo
RPMPackage collective.geo.bundle-2.1-1.lbn25.noarch
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.
RPMPackage collective.geo.behaviour-1.2-1.lbn25.noarch
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.
RPMPackage collective.geo-1.0-1.lbn25.noarch
collective.geo module
RPMPackage collective.galleria-1.2.3-1.lbn25.noarch
Galleria integration into Plone
RPMPackage collective.forgetit-0.0.1-1.lbn25.noarch
Remove uninstalled Products/package residue
RPMPackage collective.flowplayerclipviews-0.1.0a-1.lbn25.noarch
Add to your Plone videos (that use collective.flowplayer or derivated products), a "views count" feature.
RPMPackage collective.flowplayercaptions-0.1.0-1.lbn25.noarch
The captions pluging offer a great set of configuration options that you can easily change, thanks to the collective.flowplayer structure. You will find many new entry in the flowplayer_properties, but you can add new ones. Please, see the "Configuration" section of the "Flash plugin: Captions" given above, but also the Display properties and Styling properties of Flowplayer plugings guide. You are welcome to change default settings if you want cool stuffs like transparency, gradient and other. This product use a default configuration that look first of all to high video accessibility.