| The Australian National Groundwater Data Transfer Standard | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
3.13 The RESULT entity
Each recorded measurement, observation or interpretation of a parameter is called a result. Table 3.15 Attributes of the result entity
A result is linked to its relevant parameter via the combination of event_feature_identifier, event_number and parameter_number. This allows the measurements to be related to information such as the property that was measured, the equipment that was used and the inherent detection limits and error margins. The result can also be linked to the relevant sample using the additional feature_identifier and sample_number attributes. Hence, the result of a laboratory analysis result can be referred back to the actual groundwater sample that was lodged with the laboratory. Each result can be defined as a numerical value or textual description relating to a particular parameter. A reliability may be attached to the value, indicating how the numerical value should be treated (eg. ‘LT’ for ‘less than’). Additional information about a result can also be stored in the qualifier attribute. In the case of the colour parameter the qualifier stores the colour intensity. There can also be different types of results as you can record the mean value, maximum value, the constantly maintained value etc. A general indication of the level of confidence placed on the result can also be added. A result can be defined in terms of both space and time. For example, a log consists of a series of observations assigned to discrete intervals along the length of a groundwater_feature. Each interval is defined by the interval_from and interval_to attributes. The datum_number as recorded for the sample (ie. the entire length down hole that was logged) is used to define the origin. Many observations or measurements can be made for each individual interval. For example, the colour, grain size and lithology of the host rock within the log interval can be described. For the same interval, the drill sample recovery rate or the penetration rate may be recorded. The actual observation relating to the interval within the log can be stored as a number in the value attribute. This is appropriate for geophysical log data. Alternatively, the observation can be recorded as a text string in the description attribute. This is appropriate for lithological or stratigraphic logs. Components or fractions of the interval can be individually described if necessary. For example, the lithology of an interval can consist of a major fraction of grey lignitic silts and a minor fraction of yellow ferruginous medium grained sands. Each component can be uniquely defined by a fraction_number and described separately. A fraction may be of a particular fraction_type. In the case of groundwater samples, the soluble fraction derived after filtration is the focus of analysis. The time interval that the result relates to may be more critical than the spatial interval. This is the case for water levels and flow measurements measured through time during a pump test. The time_from and time_to attributes define the span of time that a result relates to, relative to the sample_start_date for the sample. This time interval may be very short (eg. practically instantaneous water level measurements from a data logger) or relatively long (eg. pumping that is maintained at a constant rate for the duration of an aquifer test). There is a degree of flexibility in terms of where space/time attributes of measurements are recorded within the data model. In the case of a single sample with multiple parameters measured (such as a groundwater sample collected for detailed chemical analysis) it would be more appropriate and efficient to record when and where within the groundwater_feature the sample is from, in the sample entity. For the reverse situation where a single parameter is measured over a sequence of down hole intervals (eg. a lithological log) then the spatial definition (eg. depth intervals) would be more appropriately stored in the result entity. An extensive domain of codes used to define the results of different properties has been developed for the data standards. Table 3.16 provides a listing of the geological, hydrogeological and geotechnical properties for which codes are currently available. In terms of stratigraphy, the Australian Stratigraphic Names Database (Lenz et al, 1996), formerly called GEODX, is the national authority database on stratigraphic names and is maintained at the Australian Geological Survey Organisation (AGSO). In addition to the traditional function of a national register of stratigraphic names, it is also an Internet-accessible stratigraphic lexicon. Included in the database are more than 28,000 stratigraphic names, their rank (member, formation, group), usage, history, currency, geological province, time range, parent unit, underlying and overlying units, boundary relations, geographic locations and bibliographic references. Each stratigraphic name is defined nationally by a unique stratno number. Table 3.16 Code-type domains available for the result entity
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|
|
|
Copyright
© 1999 Commonwealth
of Australia
Last updated 1
July 1999
contact brs-webmaster