GEO Architecture and Data Committee Task AR Architecture Implementation Pilot Access Services: Products, Sensors, Models WG Access Services Co-Chairs: Glenn Rutledge, NOAA Hervé Caumont, ERDAS Luis Bermudez, SURA Terence Van Zyl, CSIR ESIP Winter Meeting January 8th, 2009

Data Product Access 23 Primary responses: CIESIN, CNES, EPA, ESA, GEO-Ukraine, ICAN, ICT4EO, IP3, ISPRA, JAXA, Mines Paris Tech, NASA World Wind, NOAA IOOS, NOAA NCDC GOSIC, NOAA NCDC NEXRAD, NOAA NCDC NIDIS, NOAA NCDC NOMADS, NOAA/NASA GOES-R and GMU CSISS, Northrop Grumman, SURA/NIMSAT/GoMOOS, Spot Image, USGS, Washington Univ St. Louis 15 Contributing responses: ACRF, Caribbean Flood Team, ERDAS, ESIP AQ Cluster, ESRI, ESRI Canada, NOAA SNAAP

Data Product Access Topics Services: WMS, WCS and WFS Broker Services: access OGC Web services, THREDDS/OPeNDAP, Encodings Formats : NetCDF/CF, GRIB, KML, GML, JPEG2000, PNGs, GeoTIFF, MrSID, Geolocated JPEGs, CADRG, CIB, Shapefile EO Data: Radar, Optical, Weather, Precipitation, TRMM flash flood potential ALOS Imagery: Panchromatic, Near IR, SAR General Circulation Models High-frequency radar in situ oceanographic data Coastal Web Atlas holdings Multistandard platform (MapServer, ArcIms Server, SDE, etc) SPIDR web services IP3 ENM Species Distribution Analysis service SoDa W*S is already a Special Argmt THREDDS

Sensors and Models Access 8 Primary responses: GEO-Ukraine, ICT4EO, IP3, NOAA IOOS NOAA NCDC NOMADS, Northrop Grumman, Spot Image, SURA/NIMSAT/GoMOOS 4 Contributing responses: Caribbean Flood Team,Compusult, NASA World Wind, NCDC NEXRAD, Noblis

Goal, audience, and usage of the 'Use cases' Use Cases are provided to model the interactions of a (sub) system under study with its environment (actors are a user interface or other system) –Co-authored by systems analysts and end users –A starting point for tests design Use Cases are developed by the AIP Transverse Technology WG Scenarios are developed by the AIP Community WG Both support AI Pilot storyboards, to test & demonstrate inter- operability among online persistent systems and services –Running a scenario over several systems –Activating systems functions as described in the use cases

The Access WG provides coordination and guidance to achieve interoperable Access Services to products, sensors and models. This relies on the AIP-2 particapants offerings and contributions to the pilot. There are two priority use cases being developed by the Access WG: - Publish Component and Services - Interact with service(s) Access WG Charter

Template for Access Use Cases

Simple example

Publish & Interact NameDescriptionWorking GroupPreconditionPostcondition Deploy Components and Services Develop and deploy a component with associated services Access Organizational capability to host a service network- accessible offerings Interact with Services Interactions between client and services for datasets, sensors, models, workflows Access User request for a client to access a service or alert Client received information from the service or alert 9 A key goal is to reduce the complexity when it is not needed. This means that an “Interaction” should be similar for products, sensors, models and for workflows.

AIP-2 Initial Access To succeed – initially, AIP aims to reduce the variations arising from different communities. At first cut “Bind” will be the same for everyone, then advance to a dialog on what few things need to be the same so that everything else can be different. To the larger communities WFS, WCS, SOS, etc. are more alike than they are different. Data Access Services – OGC WCS/WMS Discovery Metadata – OGC CSW and ISO 19115/ISO Together this allows users to find and access data 10

ACCESS WG Contact Information Working Group Leads : Glenn Rutledge, Hervé Caumont, Luis Bermudez, Terence Van Zyl, Hans Peter Plag, Anwar Vahed, Getting to the Access WG Web page: – Subscribing to the Access WG Mailing List: – Access WG weekly telecons to discuss issues arising and new use cases that need to be addressed –Announcements through Access WG mailing list