Welcome, guest | Sign In | My Account | Store | Cart

Notice! PyPM is being replaced with the ActiveState Platform, which enhances PyPM’s build and deploy capabilities. Create your free Platform account to download ActivePython or customize Python with the packages you require and get automatic updates.

pypm install eea.geotags

How to install eea.geotags

  1. Download and install ActivePython
  2. Open Command Prompt
  3. Type pypm install eea.geotags
 Python 2.7Python 3.2Python 3.3
Windows (32-bit)
5.9Never BuiltWhy not?
4.6 Available View build log
4.4 Available View build log
4.3 Available View build log
Windows (64-bit)
5.9Never BuiltWhy not?
4.6 Available View build log
4.4 Available View build log
4.3 Available View build log
Mac OS X (10.5+)
5.9 Available View build log
4.6 Available View build log
4.4 Available View build log
4.3 Available View build log
Linux (32-bit)
5.9 Available View build log
4.8 Available View build log
4.7 Available View build log
4.6 Available View build log
4.4 Available View build log
4.3 Available View build log
Linux (64-bit)
5.9 Available View build log
4.8 Available View build log
4.7 Available View build log
4.6 Available View build log
4.4 Available View build log
4.3 Available View build log
Lastest release
version 5.9 on Jul 13th, 2013

EEA Geotags product

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.


EEA Geotags is an alternative for the default location field in Plone.

Main features

EEA Geotags features:

  1. User friendly search for locations
  2. Map preview of selected locations
  3. Suggest geographic entities based on http://geonames.org
  4. Country/regions drill down selection, including several layers like biogeographical region, countries group, country, nuts region, city and natural feature
  5. 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:

  1. https://svn.eionet.europa.eu/projects/Zope/wiki/HowToGeotag


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:



  1. Plone 4.x
  2. Products.ATVocabularyManager
  3. archetypes.schemaextender
  4. eea.jquery
  5. eea.alchemy


EEA - European Enviroment Agency (EU)


5.9 - (2013-07-10)
  • Upgrade step: ONLY in EEA context Within "Plone > Site setup > Add-ons" click on button available for eea.geotags available [ichimdav #14667]
  • Feature: Added search results mutator with implementation for EEA in order to allow mutation of search results [ichimdav #14667]
5.8 - (2013-07-08)
  • Feature: modified loading of map data so that you could load more than one map widget in the page [ichimdav]
  • Bug fix: properly load eea.geotags.jsondata when viewing the page with /view [ichimdav #14592]
5.7 - (2013-05-20)
  • Bug fix: add also countries from Asia for the Pan-Europe group when using the geotags edit widget since the search was restricted to the Europe Continent [ichimdav #14329]
  • Feature: Removed lovely.memcached dependency [voineali refs #14343]
5.6 - (2013-04-17)
  • Feature: Added possibility to specify dimensions of map modal popup when adding geotags macro to any template [ichimdav #8523]
  • Bug fix: fixed issue where clicking on a geotags like Norway took you to Denmark since they have the same x coordinate and the check for geometry was only done on the x coordinate [ichimdav #8523]
  • Bug fix: fixed issue where map infoTemplate displayed undefined as header text when itemTitle returned undefined [ichimdav refs #8523]
  • Bug fix: better fix for loading of geotagsClusterLayer.js [ichimdav #8523]
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

Subscribe to package updates

Last updated Jul 13th, 2013

Download Stats

Last month:1

What does the lock icon mean?

Builds marked with a lock icon are only available via PyPM to users with a current ActivePython Business Edition subscription.

Need custom builds or support?

ActivePython Enterprise Edition guarantees priority access to technical support, indemnification, expert consulting and quality-assured language builds.

Plan on re-distributing ActivePython?

Get re-distribution rights and eliminate legal risks with ActivePython OEM Edition.