gfdrr / geonode-afghanistan

http://disasterrisk.af

Afg

You should write some docs, it's good for the soul.

Installation

Install geonode with:

$ sudo add-apt-repository ppa:geonode/stable

$ sudo apt-get update

$ sudo apt-get install geonode

Create a new template based on the geonode example project.:

$ django-admin startproject my_geonode --template=https://github.com/GeoNode/geonode-project/archive/2.6.zip -epy,rst
$ sudo pip install -e my_geonode

Note

You should NOT use the name geonode for your project as it will conflict with the default geonode package name.

Usage

Rename the local_settings.py.sample to local_settings.py and edit it's content by setting the SITEURL and SITENAME.

Edit the file /etc/apache2/sites-available/geonode and change the following directive from:

WSGIScriptAlias / /var/www/geonode/wsgi/geonode.wsgi

to:

WSGIScriptAlias / /path/to/my_geonode/my_geonode/wsgi.py

To avoid having to grant apache permissions (i.e. www-data user and group) to your home dir where you likely setup the geonode-project; you may want to instead copy the wsgi.py file next to geonode.wsgi and replace the file name instead of the entire path.

$ cp /path/to/my_geonode/my_geonode/wsgi.py /var/www/geonode/wsgi/wsgi.py

Add the "Directory" directive for your folder like the following example:

<Directory "/home/vagrant/my_geonode/my_geonode/">

Order allow,deny

Options Indexes FollowSymLinks

Allow from all

Require all granted

IndexOptions FancyIndexing

</Directory>

Restart apache:

$ sudo service apache2 restart

Edit the templates in my_geonode/templates, the css and images to match your needs.

In the my_geonode folder run:

$ python manage.py collectstatic

Backup & Restore

The admin command to backup and restore GeoNode, allows to extract consistently the GeoNode and GeoServer data models in a serializable meta-format which is being interpreted later by the restore procedure in order to exactly rebuild the whole structure.

Before running a GeoNode backup / restore, it is necessary to ensure everything is correctly configured and setup.

Double check the b&r filters from the afg/br/settings_afg.ini file; B&R settings docuemntation is available from official GeoNode docs [here](https://docs.geonode.org/en/master/intermediate/backup/index.html#settings).

Run a backup on the source instance through:

SOURCE_URL=https://disasterrisk.af TARGET_URL=https://stage1.disasterrisk.af sudo afg/br/backup.sh

The Bakcup ZIP Archive will be stored into the /data/backup_restore/ folder.

Run a restore on the target instance through:

SOURCE_URL=https://disasterrisk.af TARGET_URL=https://stage1.disasterrisk.af afg/br/restore.sh

The Bakcup ZIP Archive will be read from the /data/backup_restore/ folder.

Github Considerations

While it is helpful to recommit your django project wrapper back to a distributed version control repository. * It is also important to remember that production instances will store security information in the local_settings.py * Admin/Devs should always remember to exclude this file in the .gitignore file in the same folder as the .git:

$ nano .gitignore

/{project}/local_settings.py

save, make sure the file is also removed from git cache:

$ git rm -f --cache //local_settings.py

$ git status

confirm the file is no longer staged for the next commit or that if it is as "removed"

geonode-afghanistan's Issues

Some layers do not download

Speaking of layer downloads, i noticed unfortunately that even as an admin, I'm not able to download one of the layers the consultant is interested in: Earthquake Shaking - PGA in g, 2500y return period . When selecting the gtiff download, i get the following exception report in xml (attached). Any ideas on how to get this to work?

Audit loading times of all elements of disasterrisk.af

There is potentially a need to create offline syncing geonodes as well as a "light" online interface.

We need to have an audit/report to understand what are the current loading times and bandwidth bottlenecks of the current geonode. Once the limitations are understood, we are requesting geosolutions to provide us a proposal on how to create a lighter loading interface, and for example improve the transactional speed on get map calls & caching .

Thumbnail view / zoom level

before the last troubleshooting of issues the thumbnails of layers were set to a closer extent which actually showed the features. Now it's as if the thumbnails were reset to "maximum" extent of the layer, which means that in most cases, it looks like there is actually no thumbnail at all, as the features are lost among a mostly white thumbnail.

Create Sync Mechanism Between Two GeoNodes (used to be Proposal)

Related to to #12, we need a proposal to develop and implement the following two options:

• Mono-directional sync between the local (editable) and the online instances (read-only). In this scenario, changes are only allowed in the local instance, and pushed asynchronously over a limited-capacity internet connection to the online instance.

• Bi-directional sync between the local and online instances, where changes are allowed on both. Syncing happen asynchronously over the same limited-capacity internet connection. This scenario requires options to manage versions and conflicts.

Make a GNIP on GeoNode for batch permissions

Currently, there is a management command allowing a sys admin to modify the permissions to the resources in batch mode.

It would be good to have a gui on the GeoNode admin dashboard allowing also a super user to run the command from the web interface.

Upgrade the disasterrisk instance and risk modules to GeoNode 2.10.x

Currently, the "disasterrisk" instance, along with the disaster management risk tools, are based on GeoNode 2.8.2.

We would like to move those apps to GeoNode 2.10.x

• Make an estimation
• Port the apps to GeoNode 2.10.x

Add analytics module to disasterrisk.af

Giving an entire group the ability to download layers

I made an account for a consultant for the project (kcoates) and added her to a new group i made, called "consultants". I gave the group permission to view all layers, but cannot find the permission that allows the group also to see the metadata and download the layers. I know admins can do this, but I want to give this permission to that group, and not give her any admin access (will be useful also for ongoing trainings!)

All 1291 layers are visible in the public version

Before the last troubleshooting of issues, only about 100 layers were visible to the 'non-authenticated" public. Now unfortunately all 1291 issues are visible to everyone all the time. Can this issue be resolved and only the layers that were flagged to be public be shown to the public? This was the case a few months ago.

Printing maps does not work

Tested on a few different maps, the printing button does not trigger any action

Assist GeoCenter at MRRD in Afghanistan in developing an offline GeoNode

The Ministry of Rural Rehabilitation and Development of the Government of Afghanistan is developing a Geospatial resource Center, which will have an offline GeoNode. Development monitors is developing the geocenter and there is dedicated IT budget for the development of this offline solution.

Assistance from Geosolutions is sought for:

1. Creating a quick reference sheet for identifying problems and possible solutions to having a bi-directionally syncing offline version of disasterrisk.af that syncs up with the online version every night.
2. Possibly identifying areas for development - for example if scripts have to be created to do the syncing.
3. Provide support to the Development Monitors team installing and developing the offline geonode at MRRD.

Layers "pending approval"

A number of layers on Disasterrisk.af show a "pending approval" flag on the main page. Giovanni sent me some text to use on the Django shell to "approve" all of them at once. I don't know how to access the Django shell. Looking for info on how to do that. I'm happy to do this myself i just need info on how to access the django shell which is presumably through a vpn or fsecure connection or somethign to the machine hosting the server.

Installation of disasterrisk at MRRD Kabul

Support Development Monitors in the successful installation of Disasterrisk offline at MRRD and set up to be used on the intranet.

Add sub-menu pages to the "About" section

We will need to expand on the "about" section to contain information specific to the Afghanistan project.

We will request the following support:

1. Add a "Project Information" sub-menu under the "About" section.
2. Group the "people", "groups" and "group categories" under a sub-heading titled "Users"
3. develop and host the page/s for "Project Information" using a template that has the look and feel of the AF geonode.
4. Support in adding text, images and videos to the page created. # #

Proposal for Lighter Interface and Improved Map Transactional Speed