[Historical Document]

Offerings at this site:

• About us: The UCB partnership with JPL
• The ESIP Federation:
• About the Federation
• The Federation Inter-operability Group
• White-papers:
• Overview of the issues facing ESIP Interoperability Catalogs
• MS Word 6 format or HTML format

The UCB partnership with JPL

Using this technology, we shall be offering our scientific results -- data-sets, not just white-papers -- to the Earth Science community. Our work here is just beginning, and it is our goal to present to you here sufficient means for others to not just browse our collections and ask for copies of it, but to fully participate and benefit from all our work, including the functional processes by which we turn raw data into information. We do this by presenting a sufficiently rich set of meta-data -- data about the data -- in a straight-forward and comprehensible way. We shall offer a publication database, a Java API and perhaps some applications which know how to browse and visualize our data.

About the Earth Science Information Partner Federation

About the Federation Inter-Operability Group

(Note: Please send me a note to help "flesh out" the following entries! Thanks.)

 Kenn Gardels, Chairman,

• Helen Conover, Michael Goodwin, Sara Graves
• Yonsook Enloe
• James Gallagher
• Kenn Gardels
• Richard Chinman
• Ethan Davis
• Jim Harville
• Matt Schwaller
• Doug Kliman, Dwight Brimhall,
• Michael Keeler,
• Dick Muntz, Silvia Nittel
• Howard Burrow
• Menas Kafatos
• Matt Schwaller
• Richard Troy, Co-Investigator, Ocean ESIP
• Heather M. Weir

Catalog Attributes, HTML, or MS Word format.
Access Method Attributes, HTML, or MS Word format.
 

ESIP Inter-Operability Desired Features & Attributes

The following are the ESIP Federation Inter-Operability catalog function descriptions.

Catalog Features and Attributes

1. Work with multiple formats, including standards-based and proprietary image, vector, and database files

 
2. Work with existing data without prior conversion

 
3. Provide concurrent access to multiple map/image servers

 
4. Minimize changes to existing data

 
5. Minimize changes to current processing techniques

 
6. Minimize additional cost to maintain data and system

 
7. Describe data provider tasks cogently and completely

 
8. Interface with user-developed programs for reading the data

 
9. Interface with COTS software

 
10. Enable data browsing in conjunction with catalog

 
11. Provide an interface and viewing capability for analytical applications (or enable same)

 
12. Support data integration or fusion, including:

• format translation

• spatial reference system (projection & coordinate system) transformation

• attribute manipulation

• symbology

1. Support coordinate and attribute query

Miscellaneous Access Specifications

1. Protocol

 
2. Source availability

 
3. Platforms supported

 
4. License costs

 
5. Current usage

 
6. Standards used

 
7. Language

 
8. DCE

 
9. Data model(s)

 
10. Data access method (file access, dbms, API, etc)

 
11. Data types

Catalog Features and Attributes

1. Provide for local and network-based discovery (browsing) of on-line or off-line geospatial information resources in a distributed heterogeneous computing environment.

 
2. Provide operations for creating and maintaining catalogs and catalog entries.

 
3. Provide operations for discovering the content and structure of geospatial resources.

 
4. Allow use of metadata entities, elements, and sections:

• defined in FGDC CSDGM plus CGMD, for both collection (series) and inventory records.

• extending (ie creating user defined) metadata.

• D ocumenting processing history or lineage

1. Provide for query (or selection) operations supporting discovery and access:

• querying metadata elements having spatial, temporal, text, and/or numeric values,

• use of metadata element names and values (e.g., spatial, temporal, numeric, keyword, and other types) in the query predicate,

• use of Boolean operations (e.g., and, or, not) between search terms in the query predicate,

• use of spatial query operations (e.g., intersect, contains, contained by, within, beyond, etc.) as predicates of a query expression (as search terms in the query predicate),

• returning complex data structures and/or objects,

• delivering identity of resources (e.g., catalogs and feature collections) as a result of query.

1. Provide access operations for retrieval of complete or partial forms of geodata resources, including:

• geospatial datasets,

• feature collections,

• features,

• metadata sets,

• metadata entities.

1. Provide operations for creating and maintaining collections of geospatial datasets, including a metadata set and metadata entities associated with each stored dataset.

 
2. Provide operations for recording and checking the accessibility and retrieval status of geospatial datasets.

 
3. Allow the use of multibyte character sets for all interfaces (ISO/IEC 10646-1, Universal Multiple-Octet Coded Character Set (UCS))

 
4. Facilitate ordering of data on or offline

 
5. Minimize re-creation of existing catalogs/metadata stores and mangement tools

 
6. Utilize available COTS/GOTS solutions where possible

 
7. Enable concurrent interrogation of multiple, distributed catalogs using a single query

 
8. Support aggregation and ranking of results

 
9. Provide searching by data type and specificity

1. Protocol

 
2. Source availability

 
3. Platforms supported

 
4. License costs

 
5. Current useage

 
6. Standards used

 
7. Language

 
8. DCE

 
9. Catalogfile format

1. Efficiency and performance

 
2. Cost of implementation

 
3. Timeliness of implementation

 
4. Adequacy of documentation

 
5. Integration into existing systems

 
6. Accessibility to users:

• NASA Researchers

• other ESIP sites

• General public users

1. Security

 
System Evaluations
 
 

Section Coordinator: Richard Troy