Geoscience Data Standard
Overview
The GDR's geoscience data standard focuses on machine readability, reusability, and reproducibility. Rather than focusing on specific file formats, it defines a few recommended formats that are open access, and the specific raw, processed, and supporting data products expected for each geoscience data type. It specifies preferred units and required documentation of collection and analysis methods. It also provides guidance on supporting materials, such as field notes, QC reports, and contractor survey reports.
General Tips
To ensure your geoscience data are standardized, follow these tips:
- Use open-source, machine-readable data formats whenever possible.
- Document the coordinate reference system (CRS) for all geospatial datasets, using an EPSG code whenever possible. Projected systems (e.g., UTM, EPSG:326xx/327xx) are often preferred for project- or site-scale data, since they preserve distances and areas in meters; geographic systems (e.g., NAD83 EPSG:4269, WGS84 EPSG:4326) are more appropriate for regional or nationwide visualization.
- For 3D data, also document the vertical reference (e.g., NAVD88, a specific geoid model, or ellipsoidal height) used.
- Document units thoroughly. SI units are preferred.
- Provide both raw and processed data.
- Provide detailed information on data collection and analysis methods applied to datasets:
- Project objectives, comprehensive metadata describing survey design and deployment strategy, station locations with a documented CRS, overlaid on topography or geological maps if available.
- Instrumentation used and its specifications.
- Data acquisition procedures and protocols.
- Quality assurance and quality control (QA/QC) procedures applied throughout the project (e.g., noise analysis, state-of-health monitoring).
- Discussion of data limitations, dominant noise sources, and any challenges encountered.
- Summary of key findings, including maps, plots, and initial interpretations.
- Environmental observations, relevant field activities, and any other information that would be helpful for someone working with the dataset.
- List tools or provide code used to process data.
- In general, plots can be a helpful addition, but the primary focus should be on the digitized, machine-readable data products.
The GDR Geoscience Data Standard
The GDR Geoscience Data Standard | Data Type | Preferred Units | Raw Data | Processed Data | Maps & Plots | QC & Ancillary Data |
Report |
|---|---|---|---|---|---|---|
|
AirborneAeromagnetic Data
|
|
|
|
Maps of residual magnetic anomaly (map view); flight line and tie line location maps; profile plots comparing raw and processed data along selected lines; DTM/terrain maps. | Data quality report, including tie-line leveling statistics (crossover error analysis) and base station monitoring records; metadata files describing CRS, acquisition parameters, processing steps, and data lineage. | Flight report covering survey parameters, acquisition, instrumentation, processing methods (diurnal correction, IGRF removal, leveling), QC, and results overview. |
|
Ground GeophysicsPassive Seismic Data
|
|
|
|
Map-view and cross-section plots of processed data; station location maps; noise characterization maps; event location maps. | Data availability reports (recovery rates, loss periods); metadata files conforming to relevant FDSN standards (e.g., StationXML for station/instrument metadata and miniSEED for waveform data), describing CRS (i.e., projection, datum), acquisition parameters, processing steps, and data lineage. | Survey report covering objectives, array design/deployment, instrumentation, acquisition procedures, processing methodology (time series prep, noise analysis, event detection/location, tomographic inversion), QA/QC, limitations, and summary of findings. |
|
AirborneLiDAR Data
|
|
|
|
Hillshade/relief maps derived from the DEM; flight line coverage and point density maps; before/after classification comparison images for representative tiles. | Accuracy assessment report (vertical/horizontal, RMSE vs. ground control); metadata files (ISO 19115/FGDC); project extent and tile index maps. | Survey report covering objectives, flight plan, instrumentation, acquisition parameters (altitude, speed, pulse rate, scan angle), ground control/base station setup, processing methodology (georeferencing, calibration, classification, product derivation), QA/QC, limitations, and final product specs/compliance. |
|
Ground GeophysicsGravity Data
|
|
|
|
Grids of Free-Air, Bouguer, and Total Bouguer anomaly (GeoTIFF, Surfer GRD, NetCDF, CSV; CRS defined) optionally residual/derivative grids. Plots of raw, drift-corrected, Bouguer anomaly, and interpreted data; station location maps; free-air and Bouguer anomaly maps; terrain correction maps. | Data quality/repeatability report, including loop closure statistics and base station tie results; metadata files describing CRS, acquisition parameters, corrections applied (tidal model, free-air gradient, Bouguer reduction density, terrain correction methodology), and data lineage. | Survey report detailing project objectives, survey design (station spacing, loop design, base station network), instrumentation and specifications, acquisition procedures (including base station ties and drift monitoring), data processing methodology (drift, tide, free-air, and Bouguer corrections; terrain correction approach), QA/QC procedures, discussion of data limitations and challenges encountered, and a summary of results. |
|
Ground GeophysicsMagnetotelluric (MT) Data
|
|
|
|
Apparent resistivity and phase curves for all four impedance tensor elements vs. period; MT phase tensors (ellipses) and induction vectors/tippers vs. period; map and cross-section plots of resistivity models at relevant depths/orientations. | Metadata files (CRS, acquisition parameters, processing/inversion steps, lineage); processing and inversion parameter files (robust-processing and 3D inversion settings). | Survey report covering objectives, site layout, instrumentation, acquisition procedures, processing methodology (robust estimation, noise removal, software), inversion methodology (algorithm, starting model, regularization, software), QA/QC, data-quality discussion, and results summary. |
|
BoreholeTemperature Gradient Data
|
|
|
|
Temperature-depth plots; temperature gradient-depth plots; borehole location map(s). | Documented in field notes or logs | Digital copy of the Contractor's Logging Report. |
|
GeochemistryGeochemical Data
|
|
|
|
Sample location maps (CRS-referenced, tied to well names where applicable); geochemical plots as applicable (e.g., Piper diagrams, geothermometry plots, time-series trend plots). | Documentation of sampling methods and any assumptions made; laboratory QA/QC procedures (standards, blanks, duplicates, detection limits); documentation of any issues (e.g., contamination, degassing, holding-time exceedances) that could impact results. | Laboratory analytical report detailing analytical methods, instrumentation, QA/QC procedures (standards, blanks, duplicates), detection limits, and any deviations or issues encountered during analysis. |
|
GeochemistryTracer Data
|
|
|
|
Well and tracer-test location maps tied to well names; breakthrough curve plots (concentration vs. time) for each monitoring point. | Documentation of sampling methods, tracer type used, and any assumptions made; documentation of any issues (e.g., background tracer levels, interference, incomplete recovery) that could impact results. | Tracer test report detailing test design (injection and monitoring locations, tracer type and mass), injection and sampling methodology, analytical methods, interpretation approach (e.g., breakthrough curve analysis), and QA/QC procedures. |
|
ModelsGeologic Models
|
|
|
|
Map-view and cross-section plots of the model at relevant depths and orientations, illustrating key structural features and geologic units. | Documentation of assumptions made and software used to produce the model; discussion of model uncertainty or confidence, where available. | Model construction report describing software used, workflow and modeling approach, input datasets and how they were integrated, key assumptions and interpretive decisions, and any known limitations or areas of uncertainty in the model. |