View on GitHub

Oak Ridges Moraine Groundwater Program - Database Manual

ORMGP Database Manual

Section 2.3.3 Grain Size Data (Example)

A number of tables are utilized to store the results of a lab-based, soil-sample grain size analysis.

Figure 2.3.3.1 Grain Size Analysis - data and table/field listing Figure 2.3.3.1 Grain Size Analysis - data and table/field listing

The above example has a number of data points that can be entered into the database, namely:

The following information needs to be captured in the data entry:

Combining the information that would reside in D_INTERVAL_TEMPORAL 1A/1B, the input data, then, would have the following approximate form.

Figure 2.3.3.2 Grain Size Data - data record Figure 2.3.3.2 Grain Size Data - data record

Note that there are four rows of data, dependent upon the reading name code, and they are all tied back to a single soil sample. This information, upon entry into the database, would then populate one record in the D_INTERVAL_TEMPORAL_1A table (including the sample name and sample date) and four records in the D_INTERVAL_TEMPORAL_1B table (the actual parameter data). The two tables would be linked based upon an imposed (randomly assigned) key (SAM_ID). Refer to Section 2.3.4 for a breakdown of fields affected in D_INTERVAL_TEMPORAL_1A and D_INTERVAL_TEMPORAL_1B upon data import.

Note also, that in the D_INTERVAL_TEMPORAL_1A table, there are additional fields that can be used to track information regarding the laboratory that performed the analyses including the laboratories sample numbering (through SAM_LAB_SAMPLE_ID), its internal job number (through SAM_LAB_JOB_NUMBER) and analysis date (through SAM_ANALYSIS_DATE). This allows one to go back to the original laboratory report or the laboratory itself to check the data entry (or possible analysis error) should a problem with the data be discovered in the future.