"Seegrid will be due for a migration to confluence on the 1st of August. Any update on or after the 1st of August will NOT be migrated"

Australian Water Data Infrastructure

Scratch pad for AWDIP documentation, Dec 2007

Table of Contents

Deployment Requirements

This document is now included in the SVN controlled geoserver config directory.

Status

as at 4/8/2008

Service URL FeatureTypes AWDI vocab Outstanding issues
BoM   4/4 yes sample data only - need sites found in stats to be available in timeseries
SA   3/4 yes?

update config to get fix for last sampling feature

update config from CVS to gettest queries using AWDI vocabs

WA ? 0/4 ? config supplied. status unknown, waiting on data for vocab updates
TAS   3/4 ? Oracle date handling workaround supplied, not installed yet
NSW   2/4 ? EC only determinand?
Qld   2/4 no waiting data management.
NT       Installation to be confirmed.

Resources

RobA has posted model, schemas, geoserver configuration, geoserver "build" (compiled application) and updated source code and tests to geotools and geoserver.

The configuration posted has been validated against sample data from: * SA, loaded into MS SQLServer, as per the SA configuration. * BOM, postgres * Qld, tables from Hydstra dump tool, loaded into postgres

(requirements 2.2.1, 2.2.2, 4.2, 2.3 against the AWDIP work plan)

Geoserver is published at:

https://www.seegrid.csiro.au/twiki/bin/view/Infosrvices/GeoserverCommunitySchemasDownloads

(note this should have the jtds driver to talk to MS.SQLServer - you may need to add oracle ojdbc14.jar)

The geoserver configuration has been tested against provided sample data for each jurisdiction.

Configuration is at https://www.seegrid.csiro.au/subversion/xmml/AWDIP/trunk/geoserver_conf/

sample queries for each agency's data is in the /demo directory, and visible through the http://my.org/geoserver/demoRequest.do in-build test harness.

This configuration needs to be completed to handle the summary statistics information for each jurisdiction. The SQL statements in the feature types should be self explanatory - the main thing is to agree at the project level on the vocabularies and groupings - eg "Flow" etc.
Topic attachments
I Attachment Action Size Date Who Comment
AWDIP_config_package.zipzip AWDIP_config_package.zip manage 426.6 K 06 Feb 2007 - 16:21 SimonCox Don NOT USE - original AWDIP (interim) - implementation experiment
Topic revision: r10 - 15 Oct 2010, UnknownUser
 

Current license: All material on this collaboration platform is licensed under a Creative Commons Attribution 3.0 Australia Licence (CC BY 3.0).