By using the WorldMap optional application, GeoNode is extended with the following additional features:

  • a customized GeoExplorer viewer
    • the table of contents is hierarchical with layer categories. When a layer is added a new category containing the layer is added to the table of contents. If the category is already in the table of contents, then the layer is added to it. By default the category is the same as the layer’s topic category, but that can be renamed by right clicking on it
    • the “Add Layers” dialog comes with a “Search” tab which uses Hypermap Registry (Hypermap) as a catalogue of remote and local layers. Hypermap is a requirement when using the WorldMap contrib application
  • a gazetteer application: it is possible to add a given layer to a gazetteer. The gazetteer can be checked using the map client. When a layer is part of the gazetter it is possible to include it in a general gazetteer or in a specific project one. It is possible to search place names in the gazetteer by date range, in which case it is necessary to specify the layer attributes for the start and end depict dates



We are assuming a Ubuntu 16.04.1 LTS development environment, but these instructions can be adapted to any recent Linux distributions:

# Install Ubuntu dependencies
sudo apt-get update
sudo apt-get install python-virtualenv python-dev libxml2 libxml2-dev libxslt1-dev zlib1g-dev libjpeg-dev libpq-dev libgdal-dev git default-jdk postgresql postgis

# Install Java 8 (needed by latest GeoServer 2.14)
sudo apt-add-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java8-installer

Virtual environment creation and installation of Python packages

Create and activate the virtual environment:

cd ~
virtualenv --no-site-packages env
. env/bin/activate

Now install GeoNode from source code:

git clone -b
cd geonode
pip install -r requirements.txt
pip install pygdal==
pip install -e .
paver setup
paver sync

Set the following environment variables as needed (change SITE_NAME and SERVER_IP s needed. Also HYPERMAP_REGISTRY_URL and SOLR_URL may be different). Even better, create a file and source it:

export USE_WORLDMAP=True
export SITE_NAME=worldmap
export SERVER_IP=
export PG_USERNAME=worldmap
export PG_PASSWORD=worldmap
export PG_WORLDMAP_DJANGO_DB=worldmap
export ALLOWED_HOSTS="localhost, $SERVER_IP, "
export GEOSERVER_LOCATION=http://localhost:8080/geoserver/
export SOLR_URL =http://localhost:8983/solr/hypermap/select/
export HYPERMAP_REGISTRY_URL =http://localhost:8001
export MAPPROXY_URL=http://localhost:8001

You can install GeoNode WorldMap in two different ways:

  1. By installing GeoNode itself
  2. By using the recommended way of a geonode-project

GeoNode/WorldMap without a geonode-project

Copy the included file and customize it to your needs:


GeoNode/WorldMap with a geonode-project

You will use a geonode-project in order to separate the customization of your instance from GeoNode.

Create your geonode project by using the WorldMap geonode-project as a template ( Rename it to something meaningful (for example your web site name):

cd ~
django-admin startproject $SITE_NAME --template= -epy,rst

Create a by copying the included template:

make build
paver setup

Start the Server

Start GeoNode with Worldmap using pavement:

python runserver
paver start_geoserver

To upload layers you can login with the default GeoNode administrative account:

user: admin password: admin

Configuring instance for production

Please follow best practices suggested by GeoNode documentation:

Remember to add the ip of your server in ALLOWED_HOSTS in the file:

ALLOWED_HOSTS = ['localhost', '', ]

Hypermap Registry

GeoNode with the WorldMap contribute module requires a Hypermap Registry (Hypermap) running instance.

You can install Hypermap by following these instructions (use the “Manual Installation” section):

Note that you can bypass Java 8 installation as it was installed previously. As a search engine you should install Solr, as we haven’t tested Elasticsearch with WorldMap so far. Create a specific virtual environment for Hypermap in order not to interfere with the GeoNode/WorldMap virtual environment.

After installing Hypermap, start it on a different port than 8000, for example:

python runserver

In another shell start the Celery process as well:

cd HHypermap
celery -A hypermap worker --beat --scheduler django -l info

Test the stack

Now that GeoNode/WorldMap and Hypermap are both running, test the stack by uploading a layer.

Login in GeoNode (admin/admin) and upload a shapefile from this page: http://localhost:8000/layers/upload

Make sure the shapefile is correctly displayed in GeoNode by going to the layer page.

Now login in Hypermap (admin/admin) and go to the admin services page: http://localhost:8001/admin/aggregator/service/ Add a service like this:

Go to the Hypermap service page and check it the service and the layer is there: http://localhost:8001/registry/

In order to have layers in the search engine (Solr) there are two options:

  1. from task runner press the “Index cached layers” button
  2. schedule a task in celery

We recommend the second option, which can be configured in the next section.

Schedule Celery tasks

Go to the Periodic Task administrative interface: http://localhost:8001/admin/django_celery_beat/periodictask/

Create the following two tasks:

Index Cached Layer Task

This task will sync the layers from the cache to the search engine. Layers are sent in the cache every time they are saved:

  • Name: Index Cached Layer
  • Task (registered): hypermap.aggregator.tasks.index_cached_layers
  • Interval: every 1 minute (or as needed)

Check Worldmap Service

This task will do a check of all of WorldMap service:

  • Name: Check WorldMap Service
  • Task (registered): hypermap.aggregator.tasks.check_service
  • Interval: every 1 minute (or as needed)
  • Arguments: [1] # 1 is the id of the service. Change it as is needed

Now upload a new layer in GeoNode/WorldMap and check if it appears in Hypermap and in Solr (you may need to wait for the tasks to be executed)

Update Last GeoNode WorldMap Layers

If your GeoNode/WorldMap instance has many layers, it is preferable to runt the check_service not so often, as it can be time consuming, and rather use the update_last_wm_layers.

As a first thing, change the interval for the check_service task you created for GeoNode/WorldMap to a value such as “one day” or “one week”.

Then create the following periodic task:

  • Name: Sync last layers in WorldMap Service
  • Task (registered): hypermap.aggregator.update_last_wm_layers
  • Interval: every 1 minute
  • Arguments: [1] # 1 is the id of the service. Change it as is needed