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 is 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. AqueousChemicalAnalysis-BasicData contains fields for information used to discover and retrieve chemical analyses meeting various criteria, and to evaluate the reported results. These fields would be reported along with a collection of analytes from the different suites proposed on the suites table.

This is a content model for features representing 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.

This information exchange specifies content elements for an interchange format for linear spatial features representing contour (isoline) data. These lines connect locations registering the same value for some variable. Examples include structure contour maps that represent lines of constant elevation on some surface, or gravity anomaly contours that represent lines of constant anomaly value. Fields in the content model will become XML elements in interchange documents for WFS simple features served by geothermal data web services.

THIS CONTENT MODEL HAS BEEN SUPERSEDED. PLEASE USE THE WELL TESTS CONTENT MODEL. 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.

This workbook documents a content model for exchange of information about fluid fluxes into or out of a well. A generic model is intended to allow for oil, gas, or water injection (negative flow). The focus of this observation type is on injection (any fluid flowed into well) or disposal. Because of the wide variety of possible flow measurements (commodities, aggregation type), the model adopts a thin approach, which may result in many records being returned for a single well. Thus most data about the well is linked through the HeaderURI instead of included inline to keep the redundant data volume down.

The ShearDisplacementStructure tab of this workbook indicates the content for Geologic Fault features. The entirety of the workbook is an information exchange workbook for GeoSciML-Portrayal, in which three features for WFS implementation are described (see alsohttp://schemas.usgin.org/models/#geosciml-portrayal-contacts and http://schemas.usgin.org/models/#geosciml-portrayal-units). 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.

The GeologicUnitView Feature tab of this workbook indicates the content for Geologic Unit features. The entirety of the workbook is an information exchange workbook for GeoSciML-Portrayal, in which three features for WFS implementation are described (see alsohttp://schemas.usgin.org/models/#geosciml-portrayal-contacts and http://schemas.usgin.org/models/#geosciml-portrayal-faults). 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.

**PLEASE NOTE:**

This content model has been superseded by Well Fluid Production content model. Please use that or the Fluid Flux Injection Disposal content models for future fluid production data.

This workbook documents a content model for exchange of information about fluid fluxes into or out of a geothermal well. A generic model is intended to allow for oil, gas, or water fluid transfer. Oil and gas facilities may include off-shore platforms, whereas water facilities may include geothermal power plants. Because of the wide variety of possible flow measurements (commodities, aggregation type), the model adopts a thin approach, which may result in many records being returned for a single well. Thus most data about the well is linked through the HeaderURI instead of included inline to keep the redundant data volume down.

This information exchange indicates 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.

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.

This information exchange is an aid for compiling data for delivery as hydraulic property observations for the National Geothermal Data System. The HydraulicPropertyObservation worksheet specifies content elements for an interchange format for data obtained from boreholes. Fields in that spreadsheet will become XML elements in interchange documents for WFS simple features/geothermal data web services. Typically hydraulic properties are collected during pump testing and/or laboratory analysis, and this information will be provided through a hydraulic property 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.

This workbook documents a content model for basic data characterizing a physical sample. The content model is based on consideration of content requested for SESAR, EarthTime, GeoSciML, Storet, ISO19115. Focus is on terrestrial (land based) samples. Content model includes sufficient information for SESAR registration (see http://www.geosamples.org/), but is not complete with all possible content in the SESAR sample data model.

Specific liquid and gas analyte suites in this workbook have been tailored for use in the analysis formulated by Powell and Cummings, 2010. Analytes reported with this content model match those in the Powell and Cummings, 2010 spreadsheets and can be directly inputted into their model, which creates numerous ternary diagrams and other Excel graphics to create a geothermomerty report. Citation: Powell, Tom and Cumming, William 2010. Spreadsheets for Geothermal Water and Gas Geochemistry. Thirty-Fifth Workshop on Geothermal Reservoir Engineering Stanford University, Stanford, California, February 1-3, 2010. SGP-TR-188. Access the paper and spreadsheets (to generate report) here: http://repository.stategeothermaldata.org/repository/resource/9e15e1a59b....

This workbook documents a content model for interchange documents with data from measurements of Radiogenic Heat Production based on analysis of individual rock samples. Calculation of heat production is based on measured U, Th, and K content, which may derive from chemical analysis, gamma ray spectral analysis or other techniques. Measurement procedures, including instruments used, standards used to calibrate calculation of U, Th, and K, assumptions in calculation of heat production from radiogenic element concentrations, etc. should be carefully described in the Measurement procedure field.

This spreadsheet indicates the content requested for features representing Seismic event hypocenter observations. Design is focused on hypocenters portrayed as points with an associated depth. Hypocenter data for geothermal data system is intended as a tool to identify seismically active areas that are often associated with hydrothermal activity, thus the content model does not include detailed information that would be important for seismological analysis; such information should be accessed by including related resource links. As such data should be restricted to records for known or suspected seismic events.

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.

This workbook documents a content model for exchange of information about fluid production for a given well. A generic model is intended to allow for a variety of flows from a well including oil, gas, and water as well as steam production. Because of the wide variety of possible flow measurements (commodities, aggregation type), the model adopts a thin approach, which may result in many records being returned for a single well. Thus most data about the well is linked through the HeaderURI instead of included inline to keep the redundant data volume down.

This template defines the content model for a service that delivers well fluid production observations. Many of these will be a standard map location and production volume, but other information may be delivered. The well fluid production content model is designed to be used for data compilation from publications, reports, and databases. This content model is intended to present key information necessary to query a well fluid production observation service and to evaluate the reported data.

This workbook describes a content model for well log observation features. These will be point features that locate the well origin for a well bore from which a well log is available. The well log observation record describes the log (type, top and bottom of logged interval) and provides links to representations of the actual log data, which typically will be either a paper copy, scanned image, or LAS file. In some cases the log may be represented in an Excel Spreadsheet. The content model includes basic information describing the well and well bore from which the log was obtained for use in search and filtering to discover logs of interest. Each row in the WellLogObservationContent sheet in this workbook will correspond to an individual log from a borehole; thus there may be multiple rows per well. For logs that are scanned or digitized and available as online resources, Scanned File URLs will be provided. The WellBoreURI for the logged well bore is the cross-referencing link (foreign key) used to associate the header record, well log records, temperature measurements, and other information from a particular borehole.