Publish BOM Observational Data
In both the water and climate program areas of BoM, extensive observational timeseries data are available. The Australian Water Resource Information System (AWRIS) collects observations of storage level and streamflow from over 200 providers under the Water Act 2007. As well, the Australian Data Archieve for Meteorology (ADAM) hosts the official long-term climate record for Australia - a dataset of significant national importance. Both water and meteorological data timeseries' are used to generate multiple data products - e.g. a national water storage product, climate data services (Climate Data Online, The Climate Zone).
This activity will develop standardised web service access through SISS to targeted subsets of these datasets, based on an assessment of priorities taken with BOM business owners.
Workflow (Target Date : End of Mar 2012)
- Step 1 : Identify and Obtain Suitable Dataset for Publishing
- Step 2 : Identify and Obtain Suitable Community Data Models and Application Schemas for Timeseries Data
- Step 3 : Create Instance Documents Base on Identified Application Schema and Dataset
- Step 4 : Create GeoServer Configuration Files Base on the Instance Documents
- Setp 5 : Deploy GeoServer Configufation Files to BoM GeoServer Instance in Test Server
- Step 6 : GeoServer Deployment Guide
Step 1 : Identify and Obtain Suitable Dataset for Publishing
- Base on the previous work with BoM, a copy of scale down AWRIS dataset has been obtained from BoM. This dataset contains observational data from a specified data provider for a number of feature of interests on different observed property (e.g. Storage Level, Storage Volume and Percentage Volume). The same dataset has been used for SISS Workshop where it has been converted from the original MySQL to PostgreSQL database. The PostgreSQL version also comes with addition information of reservoir location (as Polygon) provided by Rob Atkinson from Water Information Models (SWIM) project group.
- Andrew Woolf, Architecture Section Manager from BoM has indicated that we can re-use the similar dataset (PostgreSQL version) for BoM observational data work here.
Step 2 : Identify and Obtain Suitable Community Data Models and Application Schemas for Timeseries Data
- Two feature type has been identified for the observational data :
- slake:SurfaceReservoir (providing the feature of interest details, e.g. feature location, provider and storage details) :
- om:OM_Observation (providing time series observations and measurements details and an uri reference back to the feature of interest)
- The best Community Data Models for the Timeseries Data has been identified as WaterML2.0 application schema (which is yet to be released).
- With Peter Taylor from CSIRO ICT Centre providing WaterML 2.0 application schema and an instance document example, GeoServer mapping work is able to proceed.
- The application schema provided by Peter Taylor has been uploaded to https://www.seegrid.csiro.au/subversion/ASRDC/BOM/SLAKE/schema/waterml/.
Step 3 : Create Instance Documents Base on Identified Application Schema and Dataset
- The final instance document example to be base on for GeoServerapplicationschema mapping :
Step 4 : Create GeoServer Configuration Files Base on the Instance Documents
Step 5 : Deploy GeoServer Configuration Files to BoM GeoServer Instance in Test Server
- While working on the GeoServer applicaton schema mapping files, a few bugs has been discovered in GeoServer and fixes has been developed and commited to the latest trunk. All the fixes required are available starting from the following GeoServer version (http://files.ivec.org/geoserver/geoserver-trunk/2012-05-04/):
- Version : 2.2-SNAPSHOT
- Subversion Revision : 17070
- Build Date : 03-May-2012 21:23
- GeoTools Version : 8-SNAPSHOT (rev 38701)
- BoM GeoServer instance in the test server being upgraded to the above version and latest configuration files being deployed to the test server.
Step 6 : GeoServer Deployment Guide
- A deployment guide is available to guide the user to install and configure GeoServer: