Australian NADC

1st August 2010

Kim Finney (Manager, Australian Antarctic Data Centre & Chief Officer, SCAR

Standing Committee on Antarctic Data Management)

• Miles Jordan; Andy Townsend; Dave Watts; Kim Finney• Ben Raymond; Henk Brolsma; David Smith; Ursula Harris; Dave Connell;

Angela Bender; Matt McKellar-Spence, Mark Morffew

Data Navigator Go to http://data.aad.gov.au/aadc/navigator/

What Is Data Navigator ?

• A generic tool to “discover”, “review/download” and “map” data.

• Will replace many existing applications:– Easier for users,– Puts data into a spatial framework,– View datasets in context of other datasets,– Less maintenance for AADC staff,– Uses OGC and other standards that provide

interoperability with other systems.

Types of Content

STRUCTURED DATA

UNSTRUCTURED DATA

download data

KML

WMS

map datafilter

migrate more data

CSV

ArchitectureArchitecture

OracleExcel,CSV,GIS

Excel,CSV,Other

CAASMMetadata

GeoServer

Uploaded

to

Registered

in

Registered in

webserver

Data Navigator Application

(ColdFusion 8, Open Layers, Javascript, HTML)

ConfigTable

request

response

Look-up

Request data

Registered as layers in

Registered in

PostGIS

Export to

Registered in

Links back to

Links back to

Version 1.2• Taste of things to come:

– Much more content made available,– Import external datasets (in web map service

and CSV format) and display on map with AADC-sourced data.

New REST_Based Semantic Feature Catalogue Service

Motivation: Move from Application To Service Based System

• Capture information on Community Profiles (i.e. agreed suites of feature-types, their attributes - their units of measure and datums, feature-type relationships and classification schemes used, all linked to a specific user community or use by a computer-based tool);

• Assign one or more spatio-temporal geometries to a feature-type,• List Classification Schemes and Themes that feature-types might be

associated with, and • Exercise the feature association component of the ISO model to

record information about relationships between features (both internal and external to the catalogue).

Chose to create RESTful (Representational State Transfer) Services

• A typical REST StreamlinedCatalogueService query looks like:

/StreamlinedCatalogueService/Profiles/1/FeatureTypes/10/Format/XML

3 types of service to meet different use-cases

Profile

Feature-Type

Symbology

UoM & Datum

Classification Scheme Assignment

Relationship

Geometry

Attribute

ThemeClassification Scheme

A client is able to:•Get all features for profile n•Get all features for all profiles•Get feature n in profile n•Get a description of classification scheme n•Get all classification schemes

StreamlinedCatalogueService Service Type - Delivers more information in one hit versus an iterative drilldown

IterativeCatalogueService Service Type - Delivers via progressive drilldown through a profile

Profiles/n/ Get information for profile with ID=n

Profiles/ if no value after this switch, then all profiles are returned

Profiles/n/FeatureTypes/ if no value after this switch, then all feature-types are returned that are associated with profile with ID=n

Profiles/n/FeatureTypes/10/ Get information for feature type ID=10

Format=xml (default) Output formats that will become available (with possible additional values of: html owl or skos)

ComponentCatalogueService Service Type - gets the components of the Feature Catalogue (Feature Type, Geometry, Attribute, UoM, Datum or Relationship )

FeatureType/n Get information for FeatureType with ID=n

Geometry/n Get information for spatiotemporal geometry with ID=n

Attribute/n Get information for attribute with ID=n

UoM/n Get information for UoM with ID=n

UoM Get information for all UoMs

Relationship/n Get information for relationship with ID=n