[ home ]

Web Services for Oceanography



DAP Web Services Specification
The purpose of this paper is to outline different web service design choices being considered by OPeNDAP, to provide a rationale for their different characteristics and to solicit comments about them.

Two classes of web services have emerged. The first type of web service system uses the REST architecture where resources are represented using URI and HTTP is used to return the current representation of that resource. These systems are based on HTTP, XML and URI. In these systems, XML is typically used to encode the representation (although for the web in general, HTML is). Such systems are also often called `network-based' because the existence of network operations is made explicit.

The second type of system follows the Remote Procedure Call model and uses the Simple Object Access Protocol (SOAP) along with other technologies such as WSDL and UDDI and builds a distributed system (where the network operations are hidden from client programs). Unlike HTTP/URI systems, using SOAP/WSDL/UDDI it is possible to build a system where clients can access machine readable interface descriptions (using WSDL records which can themselves be located using UDDI) and then use the RPCs in those descriptions to access a server.

OOSTech Mailing List

TABS SOAP Server, Part 1
Demonstration server and client programs for supplying the latest data from a single buoy. No WSDL or XML yet.

TABS SOAP Server, Part 2
Demonstration server and client programs for supplying the latest data from any number of buoys. No WSDL or XML yet.

OOS Data SOAP Server Demo
Dave Forrest's SOAP server intended to demonstrate SOAP web services for providing Ocean Observing System Data.

The home page of the OpenIOOS.org demo server.

AOOS Soap Server

"SOAP::Lite for Perl is a collection of Perl modules which provides a simple and lightweight interface to the Simple Object Access Protocol (SOAP, also known as Service Oriented Access Protocol) both on client and server side."




Grid middleware that allows scientific programs to be deployed as RESTful web services.

Javascript and SOAP

Writing SOAP Web Services
Chapter 3 from "Programming Web Services with SOAP".

SOAP Version 1.2 FAQ

Call SOAP Web Services with Ajax

A Proxy Generator to WebServices for JavaScript and Ajax

JavaScript SOAP Client

Ajax and Scripting Web Services with E4X

Using WSDL in SOAP Applications

Web Services for Bioinformatics: [ Part 1 | Part 2 | Part 3 ]

Javascript and Ajax in GIS

Build AJAX-Based Web Maps Using ka-Map
National Operational Prototype Evaluation for Katrina Mapserver
Katrina ka-Map MapServer Example
msCross Webgis: MapServer Javascript AJAX Interface
Using AJAX and MapServer to Build an Interactive Web-Mapping Client
WMS Javascript Library

Mastering Ajax


Extended UDDI Service
"To address these problems, we are designing a general purpose information system, the Fault Tolerant High Performance Information System (FTHPIS), that we are applying initially to problems in GIS information management."

Related Software


XML::Writer is a helper module for Perl programs that write an XML document.

Related Projects


Google and Mapping Hacks

Marine Metadata Interoperability (MMI)

OGC Interoperability Program

Sensor Web

Sensor Web Enablement (SWE)
Interoperability interfaces and metadata encodings that enable real-time integration of heterogeneous sensor webs into the information infrastructure.

Related Software

Related Publications

NASA EO-1 Testbed

Sensor Web Alliance


SensorGrid architecture will utilize open GIS standards and Web Services methodologies to couple data assimilation tools with real-time data. The system will use NaradaBrokering as the messaging substrate and this will allow high performance data transfer between data sources and the client applications. The Standard GIS interfaces and encodings like GML and SensorML will allow data products to be available to the larger GIS community.


Compusult List of Services


GeoRSS (Geographically Encoded Objects for RSS Feeds)

GML (Geography Markup Language)
An XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features.

"GML is a large, rich, expressive language designed to have the ability to express any geographic concept in common usage. Therefore, unless you are developing a universal, comprehensive GML parsing application, the proper way to use GML is probably not to learn the entire encoding specification right away, but to start with an application schema, or profile of GML. As explained here, "Profiles live in the GML namespaces (http://www.opengis.org/gml) and define restricted subsets of GML. Application schemas are XML vocabularies defined using GML and which live in an application-defined target namespace. Application schemas can be built on specific GML profiles or use the full GML schema set." Basically, profiles and application schemas are smaller subsets of the GML schema designed by a specific information community and tailored to a small number of uses."

NetCDF, NcML, NcML-G, NcML-GML, CSML, etc.



ESIP Available Services

OPeNDAP provides software which makes local data accessible to remote locations regardless of local storage format. OPeNDAP also provides tools for transforming existing applications into OPeNDAP clients (i.e., enabling them to remotely access OPeNDAP served data).


WPS (Web Processing Service)
A service for the exchange of raster imagery.

WCS (Web Coverage Service)
A service for the exchange of raster imagery.

WFS (Web Feature Service)
WFS allows a client to retrieve geospatial data encoded in Geography Markup Language (GML) from multiple Web Feature Services. GML is built on the standard web language XML. WFS differs from the popular Web Map Service (WMS) specification in that WFS returns a subset of the data in valid GML format, not just a graphic image of data.

WMS (Web Map Service)

Tethys2 Web Services Demo
A SOAP Web Services was created to send latest mooring data.

SSDS (Shore Side Data System)
A data management system that stores both raw and processed data (and associated metadata) for a wide variety of oceanographic platforms and instruments.

ECHO Extended Services Testbed
ECHO is a set of infrastructure services that allow the publication, discovery and access to resources that support the Earth Observation community. Those resources may include information resources (data collections, inventories of data granules and browse images), service resources (using Web Service technologies) and client resources.


Earth Science Markup Language (ESML)

WSRF (Web Services Resource Framework)

OGSA-DAI is a middleware product which supports the exposure of data resources, such as relational or XML databases, on to grids.




Flow Visualization

Python and XML
Python Software
Web Development Frameworks