Skip to content
Leigh Gordon edited this page Sep 19, 2016 · 10 revisions

This is a walk through guide to get your portal serving data once you have it installed.

Adding a GeoNetwork

The AODN portal needs a GeoNetwork instance to provide search functionality.

We recommend using the IMOS version of GeoNetwork. You can find the latest version on our public S3 bucket. Download geonetwork.war and deploy it to a tomcat instance.

nb. Our GeoNetwork build contains all the necessary schema plugins.

You will also need to install our thesauri. Please download the following SKOS vocabulary files:

Parameter vocabulary

Platform vocabulary

Import these into geonetwork via the geonetwork admin interface.

Your portal will need to know where to find a GeoNetwork. You configure this by adding a line to your Portal.groovy file. For example:

geonetwork.url = "https://catalogue-123.aodn.org.au/geonetwork"

Restart tomcat after you've changed the file and you should see any public metadata records in step one of the portal.

Adding Metadata

The AODN portal depends on metadata from GeoNetwork that conforms to the ISO19115-MCP standard. The portal uses online resources defined in the metadata (such as web map and data download services) to provide visualization, filtering, and download functionality.

Documentation describing how to configure your metadata is available here.

Adding A Server

The AODN portal will not use untrusted WMS and WFS servers. You must configure a white list in your portal.groovy file.