CONTACT  |  LOGIN  |  NEW USER?

Data Interchange Content Models

Each feature or observation type that is prioritized for delivery using a community data interchange format has an associated content model that defines the information contained in interoperable interchange documents that deliver data from the data system servers to client users. The content model in its simplest form is a statement that some particular entity (feature or observation) will have some list of properties. For example a content model for a record describing a book feature might include: title, author, publisher, publication date, publication place, number of pages, and an ISBN number (a URI).

To document these content models, we are using MS Excel workbooks. Each workbook includes a description of the entity type, a list of the elements (fields, attributes) in a data instance for that entity presented both as a table and a list, and lists of vocabulary terms meant as a start or example for the kinds of vocabularies that will be required in the long run for semantic interoperability. Use of the terms in these example vocabularies will facilitate migration to formal vocabularies later.

In order to actually use the content models, they must be implemented using some computer-friendly encoding scheme. The AASG project is currently using eXtensible Markup Language (XML) to implement the content models, but in view of the rate of technology evolution, other schemes may be adopted as the system matures. The important thing is that the information is encoded consistently in a structured, well documented format. This enables computer programs to parse the interchange documents and extract the desired information, and as newer encodings are adopted, conversion between formats can be automated using software.

These content models are being developed under the auspices of the AASG geothermal data project, but they are being submitted for review and adoption for use by other project partners in the NGDS and broader USGIN community. Models that have been reviewed by the DOE NGDS Technical Working group and elevated to the NGDS website public documents section have links to forums there for comments. Please post any discussion, review, change requests to those forums.

Titlesort descending Summary Most recent version Most recent update
Active Fault/Quaternary Fault

This content model includes data elements that are in the content model for Geologic Map/faults, as well as elements providing information specific to Quaternary faults relating to slip rates, time since most recent activity.   Faults are typically represented on maps by the linear outcrop trace where the fault intersects the Earth Surface. Thus the feature service for fault uses a line feature class for the geometry. This linear geometry can not simply be represented in a spreadsheet, so a template for service deployment is  provides as an ESRI personal geodatabase (which is a Microsoft Access .mdb file). In addition, for consistency with point-based content models, an Excel Workbook is provided with work sheets for the data provider metadata, description of fields in the template, and vocabularies recommended for use in interchange documents. For those that do not have software that will work with the geodatabase file, a zip archive containing a shape file feature class is included. The shape file truncates field names and text values that are strings longer than 255 characters. If some field contain text longer than 255 characters, fault descriptions should be loaded into the excel worksheet included with the shape file. In that case, be sure that there is a key to uniquely join the shape field information with the fault description information.

 

1.500 Feb 6 2012
Aqueous Chemistry

This is a data interchange content model for an observation of the chemical composition of an aqueous fluid. A header content model for sample characterization, location, and analysis metadata is included to assist users finding analyses for specific samples, locations, time intervals, etc. Typically water temperature at the time of sampling are recorded along with sample data.  Several 'suites' of analytes representing common analysis results are defined, with the intention that an implementation of the content model would offer several observation feature types, each of which consists of the header fields combined with the analytes for a suite. A content type for reporting results for a single analyte is also proposed, with an abbreviated header; this could be implemented for services similar to the EPA storet data services. In this approach a single analysis result is delivered as a collection of observation records, each with the same AnalysisURI and reporting single analyte.

1.900 Feb 6 2012
Borehole Temperature Observation Feature

This is a data interchange content model for a subsurface temperature measurement made in a borehole. Header content that characterizes the borehole sampling feature is included with each observation to assist users finding measurements based on location, depth, particular borehole, etc. This information will be provided through a borehole temperature observation service. The HeaderURI for a particular borehole (well for simple wells) is the cross-referencing link (foreign key) used to associate the header record, well logs, temperature measurements, and other information from a particular borehole.

1.600 Feb 6 2012
Direct Use Feature

Direct use features describe facilities that utilize geothermal energy directly without transformation to electricity. See the NREL Geothermal Direct Use web page for more information. The template here is based on the Direct Use Site spreadsheet provided by the GeoHeat center at the Oregon Institute of Technology.

1.520 Apr 25 2012
Drill Stem Test Observations

This spreadsheet defines the schema used for the interchange of drill stem test observation results by the AASG geothermal data project for the National Geothermal Data System.   The HeaderURI for a particular borehole (well for simple wells) is the cross-referencing link (foreign key) used to associate the header record, well logs, temperature measurements, and other information from a particular borehole. At minimum the data will report Observation URI, Well Header URI, Well Name, API No, DST Name, DST Operator, Lat Degree, Long Degree, SRS, DST Target Formation, Depth Top Open Zone, Depth Bottom Open Zone, Pressure Initial Shut In, Pressure Final Shut in, Hydrostatic Pressure, Source, and Information Source.

1.920 Mar 9 2012
Fault Feature

This spreadsheet indicates the content for fault features. The model is from the IUGS CGI interoperability working group. See https://www.seegrid.csiro.au/wiki/bin/view/CGIModel/GeoSciMLThematicView.... This schema is a view of GeoSciML data that denormalizes the data and concatenates complex property values into single, human-readable, labels and returns single, representative, values from controlled vocabularies for multi-valued properties that can be used when generating thematic maps, or portrayals, of the data. It is separate to, but harmonized with, GeoSciML and conforms to the level 0 of the Simple Features Profile for GML (link). Labels will be 'free-text' fields that will be, in robust services, well-structured summaries of complex GeoSciML data, while the representative thematic properties will be URIs of concepts in a controlled vocabulary. There may also be links, via identifier URIs, to full GeoSciML representations of the geologic features.

1.000 Feb 6 2012
Geologic Contact Feature

This spreadsheet indicates the content for contact features. The model is based on the IUGS CGI interoperability working group. See https://www.seegrid.csiro.au/wiki/bin/view/CGIModel/GeoSciMLThematicView.... This schema is a view of GeoSciML data that denormalizes the data and concatenates complex property values into single, human-readable, labels and returns single, representative values from controlled vocabularies for multi-valued properties that can be used when generating thematic maps, or portrayals, of the data. It is separate to, but harmonized with, GeoSciML and conforms to the level 0 of the Simple Features Profile for GML (link). Labels, will be 'free-text' fields that will be, in robust services, well-structured summaries of complex GeoSciML data, while the representative thematic properties will be URIs of concepts in a controlled vocabulary. There may also be links, via identifier URIs, to full GeoSciML representations of the geologic features.

1.300 Feb 6 2012
Geologic Unit Feature

This spreadsheet indicates the content for Geologic Unit features. The model is based on the IUGS CGI interoperability working group. See https://www.seegrid.csiro.au/wiki/bin/view/CGIModel/GeoSciMLThematicView.... This schema is a view of GeoSciML data that denormalizes the data and concatenates complex property values into single, human-readable, labels and returns single, representative values from controlled vocabularies for multi-valued properties that can be used when generating thematic maps, or portrayals, of the data. It is separate to, but harmonized with, GeoSciML and conforms to the level 0 of the Simple Features Profile for GML (link). Labels will be 'free-text' fields that will be, in robust services, well-structured summaries of complex GeoSciML data, while the representative thematic properties will be URIs of concepts in a controlled vocabulary. There may also be links, via identifier URIs, to full GeoSciML representations of the geologic features. The geologic unit feature content also conforms closely to the content in the USGS-AASG NCGMP09 database design for a description of map units. These features are essentially geographically located descriptions of outcrop to map scale units of rock--including lithologic composition, age, internal structure (bedding, foliation etc.) and genesis. The content model might be associated with map units on a geologic map, individual polygons (on a map) or borehole intervals (in a stratigraphic log), or with point locations to describe outcrops in field data. For descriptions associated with maps or polygons (outcrop areas), location uncertainty properties are not included.

2.400 Feb 6 2012
Geothermal Area

This package contains both an Excel spreadsheet and an accompanying personal geodatabase (PGD) for data delivery of a Geothermal Area dataset (polygons). Design is focused on providing characteristics of sites identified as having geothermal potential. Geothermal area content for the state geothermal data system is intended as a tool to identify areas that may be associated with geothermal resource potential. Thus, the content model does not include specific measurements/data collection information that would be important for analysis; such information should be accessed by querying other related data sets in the area of interest such as borehole temperature observation services, thermal conductivity services, and published reports.

The deliverable is the personal geodatabase containing the geometry information.

0.500 Mar 21 2012
Geothermal Fluid Production

This spreadsheet contains the content requested for records representing Fluid Production reports and observations. Design is focused on production/injection wells associated with Power Plant facilities, portrayed as geospatial points with an associated production interval date. This dataset for the geothermal data system is intended as a tool to identify records associated with geothermal plants in production (or injection) or other facilities that may be of interest for coproduction of geothermal fluid. The content model does not include detailed geologic information that would be important for an analysis; such information should be accessed by included related resource links.

**PLEASE NOTE:**

This spreadsheet is still under review so you might want to wait for upates or contact us before using it.

0.100 Mar 21 2012
Geothermal Power Plant

This spreadsheet contains content requested for features representing Geothermal Power Plant locations. Design is focused on power plants portrayed as geospatial points with an associated plant type, capacity in megawatts, and use application. Power plant data for the geothermal data system is intended as a tool to identify sites with existing power plants. Thus, the content model may not include detailed information that would be important for determining geothermal potential; such information should be accessed by including related resource links. As such, data should be restricted to records for existing facilities.

0.200 Mar 21 2012
Heat Flow

This spreadsheet indicates the content requested for observation features representing Heat Flow measurements. The content model is based on specifications gathered from the SMU Heat Flow database, and has been extended to include the specifics of Heat Flow data from other parties.

Minimal required features include Observation URI, Well Name, Header URI, Label, County, State, Latitude and Longitude Degrees, Source, Driller Depth, Interval, Thermal Conductivity, Gradient, Heat Flow, and Heat Flow Method.

1.150 Apr 20 2012
Heat Pump Facility

This spreadsheet indicates the content requested for features representing heat pump facility locations. Design is focused on sites/facilities portrayed as geospatial points with associated facility type, use application, and operational date. Heat Pump facility data for the geothermal data system is intended as a tool to identify information related to facility construction and location, thus the content model may not include detailed information. Such information should be accessed by including related resource links. As such, data is intended to be restricted to records for existing heat pump facilities.

0.700 Mar 21 2012
Lithology Interval Log Feature

This spreadsheet specifies the content elements requested for AASG geothermal data interoperable web services for description of lithology log intervals associated with a borehole. Each interval has a top and a bottom, measured from the ground surface (convention for interoperability). Each interval has a geologic unit description that will be identical with the content associated with polygons on a geologic map.

0.920 Feb 6 2012
Metadata

This template is for use in compiling metadata content in a structured tabular format that can be automatically transformed into any of several metadata encoding and content schemes.  The content is based on the USGIN Recommended Metadata Model. The goal of this template is to make metadata creation easier while still complying to metadata requirements for the:

  • National Geothermal Data System (NGDS) project
  • OGC Catalog Service for the Web (CSW) protocol
  • ISO 19139 (international geospatial metadata) standard
  • FGDC CSDGM (federal geospatial metadata) standard

This spreadsheet is somewhat different from other templates in that the column names in the spreadsheet are not precisely the same as xml elements in the interchange document used to transport the metadata content. Metadata is being encoding for the NGDS using ISO19139 xml encoding of ISO 19115 content. This is a complex XML schema that can not be fully represented in the flat table format offered by a spreadsheet. Column names in the spreadsheet correspond to element names in the XML loosely.

See also:

USGIN content recommendations for geoscience information resources.

USGIN full ISO 19139 metadata profile (ISO 19115 and ISO 19119). Not for the faint of heart.

1.340 Aug 27 2011
Seismic Event Hypocenter

This template defines the content model for a service that delivers seismic event hypocenter observations. Many of these will be standard map location and IDs, but other information may be delivered. Much of the variation will concern procedures used to recorded events, citations, and possible other collected data that may be useful for geothermal resource research. The seismic event hypocenter template should be used when compiling geo data from maps and field data. The content model presented here is intended to present key information necessary to query a seismic event hypocenter observation service and to evaluate the reported activity and potentially related features (faults).

1.700 Apr 26 2012
Thermal Conductivity

This spreadsheet indicates the content requested for features representing thermal conductivity observations. Design is focused on thermal conductivity measurements/observations portrayed as geospatial points with an associated depth, TC value, headerURI, construction information, and related resources. Thermal Conductivity data for the geothermal data system is intended as a tool to identify areas that may be favorable for geothermal energy production.  Each record should contain measurement values, location, measurement type, and citations for the data.

2.010 Mar 29 2012
Thermal/Hot Spring Feature

This spreadsheet indicates the content requested for basic data characterizing a hot spring feature for the AASG geothermal data project. Typically, water temperatures are recorded with other information such as water quality or chemical analysis from a particular spring. The temperature and flow rate reported here are meant to be generalized characterization. Other observation services should be used to report time series of temperature or flow measurements.  Chemical analytical data is also reported by a separate observation service. This sheet may be used to compile multiple temperature or flow rate observations for individual springs as well.

1.600 Feb 6 2012
Volcanic Vents

This spreadsheet indicates the content requested for features representing active volcanic vent data. This simple content model is intended to identify recently active volcanic vents that may indicate areas of active hydrothermal systems. Detailed geophysical or geodetic information related to active magma movement and prediction of eruptive activity are out of scope.

1.420 Jun 13 2011
Well Header

A well is a facility defined by its function to extract fluids from within the earth. A well may be a simple hole in the ground (generally not the kind of wells we're interested in here...), but in general will consist of a dug shaft or drilled borehole. Drilled wells may include one or more boreholes (well bores) that are accessed from the surface at an origin collar, which defines the origin of the well. Individual boreholes in the well my have origin points (collars) that are located within existing boreholes in the well (e.g. sidetracks). The most common situation, especially for water wells, is a well consisting of a single borehole with a collar that is coincident with the well origin.

Well header features represent individual wells, and are the anchor for a variety of observations and other features.

1.700 Feb 6 2012

Pages

X
Enter your State Geothermal Data username.
Enter the password that accompanies your username.
Loading