North-Central Section - 39th Annual Meeting (May 19–20, 2005)

Paper No. 2
Presentation Time: 8:20 AM


FILS, Douglas1, BOHLING, Geoff2, CERVATO, Cinzia3, DIVER, Pat4, GREER, Doug5, LOEPP, Christian6, REED, Josh A.7, TANG, Xiaoyun3 and TAYLOR, Tyson6, (1)Geological & Atmospheric Sciences, Iowa State Univ, 253 Science I, Ames, IA 50011, (2)Kansas Geological Survey, 1930 Constant Ave, Lawrence, KS 66047, (3)Dept. of Geological and Atmospheric Sciences, Iowa State Univ, 253 Science I, Ames, IA 50011, (4)DivDat Consulting, 3302 Mulberry Hill Lane, Houston, TX 77084, (5)San Diego Supercomputer Center, Univ of California, San Diego, 12201 Sunrise Valley Drive, La Jolla, CA 92093-0505, (6)Geospatial Research Facility, Department of Geosciences, Boise State Univ, Boise, ID 83725, (7)Dept. Electrical and Computer Engineering, Iowa State Univ, 2215 Coover, Ames, IA 50011,

The CHRONOS System uses a services-oriented architecture. Services are abstracted in SOAP and ReST (Representative State Transfer) connections for use by the community and on the CHRONOS sites. Extending this model to address the data layer, the CHRONOS System is developing in collaboration with others the ability to address collections of data as "Data Services". These individual chunks of data can be identified by a globally unique ID (GUID) system and referenced and passed into services workflows or other data consumers.

The Data Services can be serialized into any local format that a site wishes to use. Utilization of XML (eXtensible Markup Language) format allows for easy creation of transforms via XSL (eXtensible Stylesheet Language) that can cast these data sets into other formats. Combined with the creation of a set of community XML schemas, the design allows for the querying of results based on data, metadata, or GUID assignments across the network and across heterogeneous system architectures. The resulting data can then be resolved to a common interchange format.

A description of the architecture developed for this data services flow and an example implementation of this design on the CHRONOS System will be presented together with a description of how it can interact with other geoinformatics projects.