EEA Geotags package redefines the location field in Plone. Right now in Plone location field is a free text field. EEA Geotags lets you easy define locations using a map picker and http://geonames.org geographical database.
Project description
Contents
Introduction
EEA Geotags is an alternative for the default location field in Plone.
Main features
EEA Geotags features:
User friendly search for locations
Map preview of selected locations
Suggest geographic entities based on http://geonames.org
Country/regions drill down selection, including several layers like biogeographical region, countries group, country, nuts region, city and natural feature
The widget can be used as single or multiple location picker
Also read README.txt under eea.alchemy.
More details about how to use this package can be found at the following link:
Installation
The easiest way to get eea.geotags support in Plone 4 using this package is to work with installations based on zc.buildout. Other types of installations should also be possible, but might turn out to be somewhat tricky.
To get started you will simply need to add the package to your “eggs” and “zcml” sections, run buildout, restart your Plone instance and install the “eea.geotags” package using the quick-installer or via the “Add-on Products” section in “Site Setup”.
You can download a sample buildout at:
https://svn.eionet.europa.eu/repositories/Zope/trunk/eea.geotags/buildouts
Dependecies
Plone 4.x
Products.ATVocabularyManager
archetypes.schemaextender
eea.jquery
eea.alchemy
Source code
- Latest source code (Plone 4 compatible):
https://svn.eionet.europa.eu/repositories/Zope/trunk/eea.geotags/trunk
- Plone 2 and 3 compatible:
https://svn.eionet.europa.eu/repositories/Zope/trunk/eea.geotags/branches/plone25
Copyright and license
The Initial Owner of the Original Code is European Environment Agency (EEA). All Rights Reserved.
The EEA Geotags (the Original Code) is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.
More details under docs/License.txt
Links
EEA Geotags wiki page: https://svn.eionet.europa.eu/projects/Zope/wiki/HowToGeotag
Funding
EEA - European Enviroment Agency (EU)
Changelog
5.5 - (2013-03-15)
Bug fix: load geotagsClusterLayer using dojo.require instead of loading it with portal_javascripts [ichimdav #14039]
5.4 - (2013-01-25)
Bug fix: fix location field @@rdf output [tiberich #13694]
5.3 - (2013-01-15)
Bug fix: drill down geotags categories now return alphabetically sorted results [ichimdav #9989]
Feature: added a checkbox enabled by default that will add individual countries that are part of a country group instead of the group itself [ichimdav #9998]
Feature: added point clustering support to map view [ichimdav #7337]
Change: switched to version 2.8 of the arcgis Dojo library in order to have clustering support [ichimdav #7337]
5.2 - (2012-11-26)
Bug fix: rdfencode geotags as geo:SpatialThing to stay generic, since not all geotags are points, can also be Features/Polygons etc. [demarant refs #7409]
5.1 - (2012-11-22)
Bug fix: map infoTemplate template is constructed only the information that is available for that object [ichimdav #7337]
Feature: rdf export of geotags now includes geonames URI with owl:sameAs. [demarant refs #7409]
Bug fix: fix issue with map view crashing when urllib got a Description that couldn’t quote because of unicode characters [ichimdav #10006]
Feature: Now we export all tags as geo:Point including locations labels. [demarant refs #3425]
Bug fix: corrected export of points according to wgs84 rdf vocabulary. [demarant refs #3425]
Bug fix: use folder_listing and atct_topic_view macros to avoid errors when using the map on non Topic content types [ichimdav #3353]
Feature: added rdf adapter for geotag field [tiberich, demarant, #3425]
5.0 - (2012-07-30)
Bug fix: Fixed deletion of geotags when the user creates a new translation [voineali fixes #5390]
4.9 - (2012-07-17)
Bug fix: fix preview of geotags widget on edit form when using eea.forms [ichimdav #5339]
4.8 - (2012-07-13)
Bug Fix: Fixed i18n:domain in .pt files [prospchr refs #5162]
4.7 - (2012-06-13)
Ugrade step: Within ZMI > portal_types > Topic add map_view to Available view methods [ichimdav #3355]
Bug fix: fixed markup of HISTORY.txt file [ciobabog refs #5231]
Upgrade step: Within “Plone > Site setup > Add-ons” click on upgrade button available for eea.geotags
Feature: Added ‘geotags’ zCatalog metadata to store the objects geographic information on brain in order for this to be used in map views [voineali refs #3355]
Bug fix: display scalebar on map [ichimdav #4788]
Feature: display tags left aligned for the map macros that use the version with events variable defined [ichimdav #4788]
Bug fix: fixed eea.alchemy suggestions url to get suggestions for the object, instead of the parent folder [batradav]
4.6 - (2012-04-26)
Feature: added modal map as a pop-up for geotags [ichimdav #3354]
Bug fix: Make it work with eea.inidicators aggregated edit [voineali #5077]
Bug fix: fixed so ‘title’ get saved on the field when ‘description’ is empty on geonames.org response [ghicaale #5008]
4.5 - (2012-03-30)
Bug fix: fixed that eea.geotags field on set will convert on the fly strings toward geonames service and saves the geoJSON structure. This will also fix the auto-tagging from eea.alchemy [ghicaale #5008]
Feature: eea.geotags widget view macro is now using ArcGIS JavaScript framework to display locations on a map [ghicaale #3354]
Feature: the view macro has two options, with map or plain text [ghicaale #3354]
Feature: the map view use CSS3 transform for better performance on rendering, disabled wheel scroll, loading image, continous pan, default map is centered on Europe and visible scalebar in km [ghicaale #3354]
4.4 - (2012-02-06)
Feature: implemented first basic list view of geotags. [demarant]
4.3 - (2011-11-29)
Bug fix: Fixed geotags widget to keep filled values if the edit form fails to submit due to validation errors [voineali #4773]
4.2 - (2011-11-21)
Bug fix: Fixed required validation for location field [voineali #4694]
Bug fix: Fix test if context is annotable [voineali #4741]
4.1 - (2011-11-18)
Rerelease broken egg
4.0 - (2011-11-18)
Feature: Added a way to override default Archetypes location field/widget by just adding eea.geotags.default within zcml directive in your buildout [voineali #4694]
Bug fix: Fixed geotags dialog on Add form when portal_factory is enabled [voineali #4696]
Bug fix: Fixed search results description and tags when searching with geonames.org [voineali #4525]
Feature: Updated geonames API usage according with this specifications: http://www.geonames.org/export/web-services.html Please update the ‘geonames_key’ in portal_properties/geographical_properties with your geonames username [voineali #4525]
Feature: Use geonames.org service for free search, then fallback to Google service [voineali #4525]
Feature: Geotag widget usability, add tag in one click [voineali #4429]
Bugfix: Fixed IE js error on google maps, we don’t move the navigation widget to the right of the map on preview [szabozo #4542]
Bugfix: Fixed missing google map api [szabozo0 #4428]
Cleanup: Fixed all pylint, pyflakes warnings [voineali #4236]
Feature: Added upgrade steps [voineali #4392]
Feature: Plone 4.0.4 compatible release [ghicaale #4236]
1.3 - (2011-04-20)
Bug fix: fix widget bugs [szabozo0 #4260]
1.2 - (2011-04-19)
Bug fix: fix import errors [szabozo0 #4260]
Feature: created formlib version of the widget [szabozo0 #4260]
Cleanup: of most pylint violations [ichimdav #4140]
Cleanup: of pyflakes warnings [ichimdav #4141]
Bug fix: Remove geotags suggestion duplicates [voineali #3357]
Change: Moved alchemy auto-discover code to eea.alchemy as it’s not only about geotags, it will also discover temporal coverage and keywords [voineali #3357]
1.1 - (2010-12-13)
Bug fix: Fixed jslint warnings [voineali #3821]
Bug fix: Fixed doc tests [voineali #3821]
1.0 - (2010-10-12)
Initial release
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
