Feature Catalogue Services

1st August 2010

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

Standing Committee on Antarctic Data Management)

What Are Feature TypesFeature Types: Real world objects (e.g. Bicycle, Tyre, Road, River, Airport, Mountain, CTD Observation, ARGO Float Observation)

http://ceos.org100,50,2300,75.4X=56

WMSmaps

WFSfeature data

WCScoverage data

<Roads> <Road> <gml:name>M11</gml:name> <gml:centerLineOf> <gml:LineString srsName="EPSG:4326"> <gml:coordinates> 0,5.0 20.6,10.7 80.5,60.9 </gml:coordinates> </gml:LineString> </gml:centerLineOf> <classification>motorway</classification> <number>11</number> </Road></Roads>

Used in Gazetteers

Feature_Type: RangeFeature_Type Id: 7

Feature Instance: David RangeFeature Instance Id: 3364

Gazetteer_Name: David Range

Latitude: 67° 50' 00.0" SLongitude: 62° 32' 17.0" ESCAR_Gaz Id: 3364

Feature Catalogue

• Take opportunity to enhance catalogue data model• 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

From Application To Service

• Developed 3 types of service to meet different use-cases

A typical REST Service query looks like:

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

This service returns information on Feature Type with ID=10 that belongs to Community Profile ID=1 in an XML format.

Using this particular type of service call (i.e. a StreamlinedCatalogue Service) a client is able to:

•Get all features for profile n•Get all features for all profiles•Get feature n in profile n

…/IterativeCatalogueService/Profiles/1/FeatureTypes/10/Attribute/3/Format/SKOS

This service returns information on Attribute with ID=3 associated with Feature Type with ID=10 that belongs to Community Profile ID=1 in a SKOS format.

Using this particular type of service call (i.e. a IterativeCatalogue Service) a client is able to:

• Get profile n or all profiles,• Get all features for profile n,• Get all features for all profiles,• Get feature n in profile n,• Get attribute n, or all attributes for feature type n in profile n,• Get geometry n, or all geometries for feature type n in profile n, and• Get UoM n and associated Datum, or all UoMs for attribute n in feature type n in

profile n

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