Configuring the Spatial Portal

Introduction

We try to describe some extra steps in order to customize and adapt the Spatial service, like changing the menu items, base layers, WMS servers, and the skin.

Some settings

Map area

The preferred way to change the spatial bounding box area in using the la-toolkit, but if you prefer to do it manually:

• open config in /data/spatial-hub/config/spatial-hub-config.yml
• see the default_areas section and specify your own coordinates, name, etc. These can be configured via some ansible var. Then service tomcat7 restart (or 8 or 9). You can see the result by clicking on "Tools -> Add area report".

Custom WMS services

Add your own WMS servers - (see presetWMSServers in the config in /data/spatial-hub/config/spatial-hub-config.yml) If your json request ends with a 401-Unauthorized error, add your server host to the allowproxy line in spatial-hub-config.yml:

allowProxy:
        server:"spatial.l-a.site;data.auscover.org.au;data.auscover.org.au:80;geoserver.imos.org.au;www.ga.gov.au/gis;geofabric.bom.gov.au"

Skinning

• create a custom version of portal.gsp (as portal-yoursite.gsp)
• put that custom skin file in /data/spatial-hub/views/layouts/portal-yoursite.gsp
• point to that file in /data/spatial-hub/config/spatial-hub-config.yml with eg. skin.layout=portal-yoursite
• restart spatial and see how looks like

See the spatial-hub README for skinning options for the Spatial Portal.

change the support email in the i18n messages

Some messages in spatial-hub hava [email protected] on them. You can overwrite them adding to /var/opt/atlas/i18n/spatial-hub/messages.properties:

292=Please send feedback to <a href="mailto:[email protected]">[email protected]</a>
540=An error occurred. Please try again and if the same error occurs, send an email to [email protected] and include the URL to this page, the error message and what steps you performed that triggered this error.

And to other languages, like: /var/opt/atlas/i18n/spatial-hub/messages_es.properties:

292=Por favor, envíe sus comentarios a <a href\="mailto\:[email protected]">[email protected]</a>
540=Se ha producido un error. Por favor, inténtelo de nuevo y si ocurre el mismo error, envíe un correo electrónico a [email protected] e incluya la URL a esta página, el mensaje de error y los pasos que realizó y que desencadenaron este error.

Customize the Area report

The area report can be customized as described on the README of spatial-service in other to translate it, or to change the header and footer,...

But to make some queries work you need to setup your portal species lists in order to work properly, like threatened species, invasive species, iconic species and migratory species, and add the drID of the list to the `AreaReportDetails.json'.

gazetteer

The nearest location tool needs a layer with your local place names. And setup the layer in the gaz_field ansible variable. But we need some extra info about this layer to make it work like in the ALA portal.