Difference between revisions of "Setting up geonode"

Revision as of 17:01, 27 February 2014

>> return Cedeus IDE

Basic Install for GeoNode v. 2.0

This is the fast install from GeoNode.org Quickstart. Full install instructions, including installation of PostGIS, can be found in this Admin tutorial

1. Install from PPA in Ubuntu 12.04 -> see http://docs.geonode.org/en/latest/intro/install.html
   1. if Tomcat7 is not installed, do: sudo apt-get install tomcat7 (but see below in step 1.5)
   2. sudo add-apt-repository ppa:geonode/release . Note, if add-apt does not work (command not found) then do first sudo apt-get update && sudo apt-get install python-software-properties
   3. sudo apt-get update
   4. check what geonode versions are available use: apt-cache showpkg geonode. When I looked there was only one version, i.e. 2.0.0+thefinal5
   5. sudo apt-get install geonode (before I could run this I had do to do sudo apt-get install libtomcat7-java so that Tomcat6 will be removed and then I could install tomcat7 - which was needed to for GeoServer - used by GeoNode. Another time I installed with Ubuntu Server as default solo OpenSSH and LAMPS (no tomcat no psql), so I could just do sudo apt-get install tomcat7)
   6. Note that the packages are stored in /var/cache/apt/archives. So they can be copied from there to another machine.
2. Set the IP address and create a superuser (also described here: http://docs.geonode.org/en/latest/deploy/production.html)
   • sudo geonode-updateip 127.0.0.1 (=> Use the real IP if you have one, and for the VM I actually used the one given by ifconfig: 10.0.2.15)
   • geonode createsuperuser
   • set GeoServer ProxyURL as described in the geonode install instructions. Use user admin with geoserver.
   • If starting up Apache results in the following message: "Could not reliably determine the server’s fully qualified domain name, using 127.0.1.1 for ServerName.", Then do this:
     • sudo vim /etc/apache2/httpd.conf
     • add ServerName localhost to the blank file (the word ServerName needs to stay as such)
     • sudo service apache2 restart
3. When using a VM with -nat I got at this point "There was a problem loading this page - Please contact your GeoNode administrator (he may have received an email automatically if he configured it properly).". I checked what is going on with tail -f /var/log/apache2/error.log. The log showed me that I should add the bridged IP 146.155.17.113:14080 to allowed hosts in /etc/geonode/local_settings.py. Hence I did changed the corresponding line in local_settings.py to ALLOWED_HOSTS=["*"]
4. Import data

Read the admin docs and also OSGeo Live DVD Quickstart tutorial

#!/bin/sh 
JAVA_OPTS="-Xms512m -Xmx4g -XX:MaxPermSize=270m -server -Djava.awt.headless=true -Djava.util.prefs.systemRoot=$CATALINA_HOME/content/thredds/javaUtilPrefs" 
export JAVA_OPTS

Notes on installing PostGIS

Basic PostgreSQL + PostGIS install

First check if PostgreSQL exists and what version exists. Use which psql which should return the path. Then with the path I did /usr/bin/psql --version to retrieve the version installed. As it was not installed on my brand new PostGIS VMs I installed Postgres 9.3 with PostGIS 2.1 as described here:

• http://trac.osgeo.org/postgis/wiki/UsersWikiPostGIS21UbuntuPGSQL93Apt :
  • add the repository
    1. sudo sh -c 'echo "deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main" >> /etc/apt/sources.list'
    2. wget --quiet -O - http://apt.postgresql.org/pub/repos/apt/ACCC4CF8.asc | sudo apt-key add -
    3. sudo apt-get update
  • install: sudo apt-get install Postgresql-9.3-postgis pgadmin3 postgresql-contrib
  • enable admin pack:
    1. sudo -u postgres psql
    2. CREATE EXTENSION adminpack;
    3. leave psql \q
  • create the users
    1. sudo su - postgres (logs in as postgres user)
    2. createuser -d -E -i -l -P -r -s yourUserName => create user for own login, and a "geonode" user
    3. logout as postgres user exit
  • adjust remote connection permission in postgresql.conf and pg_hba.conf, for details see below (Note, the VM setting also needs to allow connections, i.e. "nat" rules)
  • enable the extensions "postgis" and "postgis_topology" for the particularDB (i.e. geonodegisdb93 > via PgAdmin: Expand the database tree in PGAdmin, and reveal the extensions node > Right-click the extensions node, and click new extension)

However, one can also install from source: see: http://trac.osgeo.org/postgis/wiki/UsersWikiPostGIS20Ubuntu1204src

PostGIS install comments with respect to my first GeoNode install

Here now some more install logs/info with respect to GeoNode:

• So, Postgres 9.1 was installed, but when I executed "psql" I got this: psql: FATAL: role "ssteinig" does not exist
• Hence, I first had to creating my account as a user using sudo -u postgres createuser -s $USER (got this from here).
• Now I could create a db using createdb mygeodb, and connect via commandline with psql -d mygeodb
• Finally I spatially enabled the db with CREATE EXTENSION postgis; and CREATE EXTENSION postgis_topology;
  • However, for CREATE EXTENSION postgis; I got the following error: "ERROR: could not open extension control file "/usr/share/postgresql/9.1/extension/postgis.control": No such file or directory".
  • This may be solved using the install instructions from here: http://wiki.postgresql.org/wiki/Apt
  • However, I followed now what is written here: http://trac.osgeo.org/postgis/wiki/UsersWikiPostGIS21UbuntuPGSQL93Apt
  • the stuff described below did not work either, I think:
    • echo "deb http://apt.postgresql.org/pub/repos/apt/ precise-pgdg main" | sudo tee /etc/apt/sources.list.d/postgis.list
    • sudo apt-get update
    • sudo apt-get install postgresql-9.3 pgadmin3
    • and then...., I got again an error: update-alternatives: error: alternative pg_basebackup.1.gz can't be slave of psql.1.gz: it is a slave of postmaster.1.gz, which send me to this page: http://www.postgresql.org/message-id/20130508192711.GA9243@msgid.df7cb.de
• then add a Postgres/postgis port forwarding rule for port 5432

GeoNode with external PostgreSQL DB

• modify settings in "/etc/geonode/local_settings.py" (before first use of db)
• the changes may require to run geonode syncdb --noinput --all (and perhaps a tomcat7/apache2 restart?) to sync
• if the db contains data/layers already (e.g. geonodegisb93 > schemata > public > tables), and those should be visible again from GeoNode, then
  • each table/layer needs to be published (re-loaded) in GeoServer and
  • geonode updatelayers command needs to be run.

Accessing GeoNode - PostgreSQL

• create user: sudo su postgres
• and: createuser -d -E -i -l -P -r -s sstein or all in one: sudo -u postgres createuser -P ssteinig
• to access via terminal use psql -U sstein -d geonode -h localhost
• to access via pgAdmin:
  • edit the file /etc/postgresql/9.1/main/postgresql.conf to allow access from other hosts, and /etc/postgresql/9.1/main/pg_hba.conf to add the users that can login, see http://www.glom.org/wiki/index.php?title=Initial_Postgres_Configuration
  • restart postgres as follows: sudo /etc/init.d/postgresql restart

Some PostgreSQL commands

• quit psql: \q
• connecting: psql -U geonode93 -d geonodegisdb93 -h localhost -p 5432
• listing of dbs: psql -l -p 5432<code> or <code>\l(including spec of port, as the PostGIS VM has postgres 9.1 (:9434) and 9.3 (:9432) installed)
  • or alternatively: SELECT datname FROM pg_database WHERE datistemplate = false;
• adding / removing users createuser and dropuser e.g.: dropuser geonode -p 5434 but needs to be done as "sudo su - postgres"
• creating /removing dbs createdb and dropdb e.g.: createdb geonodegisdb93
• listing of tables: \dt : but this will only list the table from the database currently connected to
  • to see at least something (if nothing added yet) it can also be done using: SELECT table_schema,table_name FROM information_schema.tables ORDER BY table_schema,table_name;
• showing a tables content, e.g. all layers: SELECT * FROM layers_layer;

Testing GeoExplorer with remote WMS clients

• a list of running GeoNode instances can be found in this email thread: http://groups.google.com/d/topic/geonode-users/icuYPeL3rIg/discussion
• a server to test is http://demo.geonode.org/geoserver/wms , or the server from the World Food Program: http://geonode.wfp.org/geoserver/wms (= http://74.3.255.211/geoserver/wms)
• if errors occur to check what is going on run: tail -f /var/log/apache2/error.log
• if a 403 error occurs, then the list of allowed hosts needs to be modified in the /etc/geonode/local_settings.py file (perhaps a "sudo service apache2 restart" is needed)
• if a 500 error occurs, then it could be that the mapping domain => IP does not work and the DNS has to be added to the computer settings (i.e. adding the DNS to /etc/resolv.conf - but see ask-ubuntu : i edited now /etc/network/interface and ifdown/ifup eth0 => but this made me loosing the network connection !!! ...and I had to use VNC to connect to the VM again and do sudo ifup eth0 in a terminal)

Changing the GeoNode logo (GeoNode 2.0)

The original documention on how to do this is here: http://docs.geonode.org/en/latest/deploy/customize.html. However, some things have changed for GeoNode v 2.0. So we have to do the following:

• The static web documents are in /var/www/geonode/static/geonode. And CSS and images are in the subfolders /css and /img.
• Create a new logo file. The original logo file is called logo.png and has a dimension of 127x29 px.
• Create a subfolder in /etc/geonode/media/ => so we have now the folder /etc/geonode/media/geonode/img/
• Make this img subfolder accessible for ftp (e.g. using chmod 777)
• copy the new logo into the etc/.../img subfolder
• run sudo geonode collectstatic -v0
• this should copy the new logo image into /var/geonode/static/geonode/img/.

Changing the GeoNode Theme (GeoNode 2.0)

Change of GeoNode web page colors

See comments above... for simple change of the CSS. I actually took the bootstrap? created base.css (see also base.less) and changed the color/backgroundcolor for web page elements (see personal notes in my log-book).

Apart from that: Everything else is more complicated and requires lots of others software (bootstrap, etc):

• a theme is available here: http://github.com/ingenieroariel/geonode-project
• a recent Oct. 2013 email thread: http://groups.google.com/d/msg/geonode-users/pI3-7QiFzs0/3nrvyjAX2rYJ
  1. install geonode with apt-get
  2. install git-core and clone https://github.com/GeoNode/geonode-project.git
  3. Install your custom project in the virtualenv, you can do this via pip install -e . or python setup.py develop
  4. Modify geonode's /var/www/geonode/wsgi/geonode.wsgi to import yourproject.settings instead of geonode.settings.
  5. Add a symlink to /etc/geonode/local_settings.py next to yourproject.settings so it picks up all the information about database and template locations in production. (run geonode collectstatic)
  6. Restart apache.

Translation + Change of GeoNode Welcome text

GeoNode is a Django Project - well, according to Daniel they put it into package for distribution (see here). So for that reason the GeoNode Django "project" can be found under the following path /usr/local/lib/python2.7/dist-packages/geonode/locale.

To edit the text of the GeoNode welcome page, one can edit the English, Spanish, etc, locales stored under /usr/local/lib/python2.7/dist-packages/geonode/locale. However, I need to check if they should get replaced when an upgrade is performed. The translation is in .po files. Information on how to compile these files can be found here: http://docs.djangoproject.com/en/1.6/topics/i18n/translation/#how-to-create-language-files

However, what did I do to change the german translation for the front page.

• copy (backup first) and open /locale/de/LC_MESSAGES/django.po
• check out in the file /templates/index.html what strings are used
• modify the text for the corresponding language keys in django.po
• save and cope the file to the server (ensure that you have a backup of the original!!! and use chmod to enable copying)
• compile the changed language file using: django-admin.py compilemessages -l de or: sudo geonode compilemessages
• perhaps do a sudo service apache2 restart?
• now check if the german text changed.

Note, for a new language file, e.g. Chile Spanish one would create the template po files using: django-admin.py makemessages -l es_cl or: sudo geonode makemessages -l es_cl first. (I think so ;)

Adding own Tiles to GeoExplorer

Own background tiles can be created with TileMill and then distributed with TileStream. Daniel has done that on Lautaro, and the tiles can be access from here: http://lautaro.ing.puc.cl/map/v2/Fondef/{z}/{x}/{y}.png . The max zoom level seems to be "16".

How to enable showing of my own tiles served by TileStream can be found in the OpenQuake bugfix for "hack the MapBoxSource gxp plugin to allow for our tilestream data". The Git pull request can be found here. According to this, the following changes are necessary:

1. check the js file by Ben Wyss TileStreamSource.js which is based on MapBoxSource.js plugin. The MapBoxSource.js is part of /var/www/geonode/static/geoexplorer/script/GeoExplorer.js in minified version, but can be seen raw in GeoExplorer-debug.js. Insert this code into GeoExplorer.js and replace with the IP of my private TileStream server.
2. modifying local_settings.py by adding gxp_tilestreamsource equally as gxp_mapboxsource is added (+ restart Apache2 service)

Note: This is still not working, but I can definitively see the OpenQuake layers. So it should be a small step. It seems a bit like the tilsets metadata (zoom levels => coordinate dimensions) that can be derived from /api/v1/Tilset are the issue. That is, until now I have not been able to localize this API endpoint on Lautaro

PS: some more info is perhaps found in the tutorial: http://docs.geonode.org/en/latest/reference/developers/settings.html

Working fill-in code for OpenQuake tile layers for GeoExplorer.js

• The OpenQuake TileStream server can be accessed via: http://tilestream.openquake.org (this link allows to browse the tile sets as well using Leaflet)
• interestingly the following code executes first a request for a tile server description (a json document) to get info about all existing tile sets. This json metadata file is obtained from: http://tilestream.openquake.org/api/v1/Tileset .Lautaro doesn't seem to have installed api/v1/Tileset (at least I could not found it in /srv/www/.
• Tiles from OpenQuake server are then accessed using this scheme: http://tilestream.openquake.org/v2/" + tileStreamLayerName + "/${z}/${x}/${y}.png

  var tilestreamPlugin = {
     ptype: "gxp_tilestreamsource",
     title: "TileStream Layers",
  
   /** api: method[createStore]
    *
    *  Creates a store of layer records.  Fires "ready" when store is loaded.
    */
   createStore: function() {  
 
       var options = {
           sphericalMercator: true,
           wrapDateLine: true,
           //numZoomLevels: 7
           numZoomLevels: 16
       };  
       var layers = new Array();
       $.getJSON(
       	'http://tilestream.openquake.org/api/v1/Tileset',
       	function(json) {
           	   for (var i=0; i < json.length; i++) {
               	// Get the tile name and zoom level from the tilestream API
       		var tileStreamLayerName = json[i].id;
               	var tileMaxZoom = json[i].maxzoom;    
               	// Build the list of layers
                       var newLayer = new OpenLayers.Layer.XYZ(
                                       tileStreamLayerName,
                   	                ["http://tilestream.openquake.org/v2/" + tileStreamLayerName + "/${z}/${x}/${y}.png"],  
                   	                OpenLayers.Util.applyDefaults(
                                             {
                       	                   layername: tileStreamLayerName,
                       	                   numZoomLevels: tileMaxZoom
                   	                      }, 
                                            options)
               		        );
                                      layers.push(newLayer);
           	   }
           	   newLayerStore(layers);
       	}
       ); 
       var plugin = this;
       var newLayerStore = function(layers) {
           plugin.store = new GeoExt.data.LayerStore({
               layers: layers,
           	fields: [
                   {name: "source", type: "string"},
                   {name: "name", type: "string", mapping: "layername"},
                   //{name: "abstract", type: "string"},
                   {name: "group", type: "string"},
                   {name: "fixed", type: "boolean"},
                   {name: "selected", type: "boolean"}
               ]
           });
           plugin.fireEvent("ready", this);
       };
   },
   /** api: method[createLayerRecord]
    *  :arg config:  ``Object``  The application config for this layer.
    *  :returns: ``GeoExt.data.LayerRecord``
    *
    *  Create a layer record given the config.
    */
   createLayerRecord: function(config) {
       var record;
       var index = this.store.findExact("name", config.name);
       if (index > -1) {
           record = this.store.getAt(index).copy(Ext.data.Record.id({}));
           var layer = record.getLayer().clone();
           // set layer title from config
           if (config.title) {
               /**
                * Because the layer title data is duplicated, we have
                * to set it in both places.  After records have been
                * added to the store, the store handles this
                * synchronization.
                */
               layer.setName(config.title);
               record.set("title", config.title);
           }
           // set visibility from config
           if ("visibility" in config) {
               layer.visibility = config.visibility;
           }
           record.set("selected", config.selected || false);
           record.set("source", config.source);
           record.set("name", config.name);
           if ("group" in config) {
               record.set("group", config.group);
           }
           record.data.layer = layer;
           record.commit();
       }
       return record;
   }
 };
 gxp.plugins.TileStreamSource = Ext.extend(gxp.plugins.LayerSource, tilestreamPlugin);
 Ext.preg(gxp.plugins.TileStreamSource.prototype.ptype, gxp.plugins.TileStreamSource);
 Ext.ns("gxp.plugins");

Simple working fill-in code for Lautaro - Fondef tile layers for GeoExplorer.js

Link to zipped version of the GeoExplorer.js minified version.

var tilestreamPlugin = {
   
   /** api: ptype = gxp_mapboxsource */
   ptype: "gxp_tilestreamsource",
   
   /** api: config[title]
    *  ``String``
    *  A descriptive title for this layer source (i18n).
    */
   title: "CEDEUS TileStream Layers",
   
   /** api: method[createStore]
    *  Creates a store of layer records.  Fires "ready" when store is loaded.
    *  sstein: in my case it creates only one layer "Fondef" that is part of the store
    *  I removed the original loop to gather layers from /api/v1/Tileset json
    */
   createStore: function() {
       
       var options = {
           sphericalMercator: true,
           wrapDateLine: true,
           //numZoomLevels: 7
           numZoomLevels: 16
       };  
       
       var layers = new Array();      
       var tileStreamLayerName = "Fondef";
       var tileMaxZoom = 17;
 
       var newLayer = new OpenLayers.Layer.XYZ( 
                               tileStreamLayerName,
                   		["http://lautaro.ing.puc.cl/map/v2/" + tileStreamLayerName + "/${z}/${x}/${y}.png"],  
                   		OpenLayers.Util.applyDefaults(
                   			{
                       			layername: tileStreamLayerName,
                       			numZoomLevels: tileMaxZoom
                   		        }, 
                   			options)
               		);
       layers.push(newLayer);  
		 		
       var plugin = this;
       var newLayerStore = function(layers) {
           plugin.store = new GeoExt.data.LayerStore({
               layers: layers,
           	fields: [
                   {name: "source", type: "string"},
                   {name: "name", type: "string", mapping: "layername"},
                   //{name: "abstract", type: "string"},
                   {name: "group", type: "string"},
                   {name: "fixed", type: "boolean"},
                   {name: "selected", type: "boolean"}
               ]
           });
           plugin.fireEvent("ready", this);
       };
        newLayerStore(layers);
   },
   
   /** api: method[createLayerRecord]
    *  :arg config:  ``Object``  The application config for this layer.
    *  :returns: ``GeoExt.data.LayerRecord``
    *
    *  Create a layer record given the config.
    */
   createLayerRecord: function(config) {
       var record;
       var index = this.store.findExact("name", config.name);
       if (index > -1) {

           record = this.store.getAt(index).copy(Ext.data.Record.id({}));
           var layer = record.getLayer().clone();

           // set layer title from config
           if (config.title) {
               /**
                * Because the layer title data is duplicated, we have
                * to set it in both places.  After records have been
                * added to the store, the store handles this
                * synchronization.
                */
               layer.setName(config.title);
               record.set("title", config.title);
           }

           // set visibility from config
           if ("visibility" in config) {
               layer.visibility = config.visibility;
           }
           
           record.set("selected", config.selected || false);
           record.set("source", config.source);
           record.set("name", config.name);
           if ("group" in config) {
               record.set("group", config.group);
           }
           record.data.layer = layer;
           record.commit();
       }
       return record;
   }
};
 
gxp.plugins.TileStreamSource = Ext.extend(gxp.plugins.LayerSource, tilestreamPlugin);
Ext.preg(gxp.plugins.TileStreamSource.prototype.ptype, gxp.plugins.TileStreamSource);
Ext.ns("gxp.plugins");

GeoNode Settings

ToDo: check for settings that still need to be adjusted for a running system:
see http://docs.geonode.org/en/latest/reference/developers/settings.html