Below you can find the rules for filling in the file templates to insert your data.

For detailed information on data insertion, please consult this guide: H+ database guide

Time format

For time, please use the format: hh:mm:ss:ms with the milliseconds in the format mmm. (e.g. 10:00:00:500).

Limits of detection

When a value is below the detection limit of the device, it is not possible to insert “<LD” instead. The convention in the database is to insert “NaN” and specify the limit of detection of the device if it is available, in the associated field.

An example of file content :

Depths (relative z)

The saved depths in the various files are indicated in a column “relative_z”.

Three columns must always be present in a given file regarding the depth:

• relative_z definition: free text indicating what reference point was used to estimate the depth registered in the column “relative_z”. For instance: top of the well
• reference for the relative_z definition: the French NGF altitude in meters of the point used to define the depths in the column “relative_z definition”
• relative_z: depth where the measurement is done in meters, measured in curvilinear way along the borehole, from the reference point. This measurement is in positive values.

Piezometric level

• raw data: original file of the sensor, in which the data are given with respect to a reference level that may be different in various files.
• relative depth corrected: piezometric data, validated, with the z reference indicated in the column ” relative_z definition”.
• relative depth corrected NGF: piezometric data with the reference to the mean sea level

Pumping flow rates

The pumping flow rates are expressed as follows:

• Positive if the water is injected in the borehole
• Negative if the water is pumped out of the borehole

Hydraulic and chemical tests

We consider 4 types of tests:

• Tracer tests: the test is described in the file experiment.csv; the injected tracer concentrations are saved in the file tracer_measurements.csv
• Flowmeter tests: the test is described in the file experiment.csv; the values of flow and speed are registered in the file borehole_flow_profile.csv
• Pumping tests: the test is described in the file experiment.csv; the values of injected or pumped volumes (and temperature if the device indicates it) are registered in the file tested_borehole_during_pumping_tests.csv (see example below)
• Slugs (hydraulic hits): the test is described in the file experiment.csv; the values of injected volume and level of the perturbation are registered in the tested_borehole_during_slug_tests.csv

There is an additional optional information (experiment name) in the templates for piezometric level or in situ measurements to indicate that there is an on-going experiment for these values.

For the pumped or injected volumes, one line must be created in the file for every flow rate change. A line with a flow rate 0 indicates the end of the injection or of the pumping.

An example of inserted data files for the pumping test:

Packers description

• relative_z upper packer: upper limit of the chamber between the packers (in which the flow rate is controlled) If there is no packer, let this box empty.
• relative_z lower packer: lower limit of the chamber between the packers

Technical description of the boreholes

The technical descriptions of the boreholes are in the file named technical log.xls 

One should use the following conventions: there should be a line for every tube. The indicated relative_z corresponds to the depth at which there is the change. For instance, if the well has an external pre tube from 0 to 10m and an internal tube from 8 to 15m, there will be 4 lines in the file  technical log for every depth where there is a change (relative z =[0,8,10,15]).

The nature of the tube is in the list “tube materials”.

Geological logs

The data selection allows extracting measurements using the geological log of a borehole (for instance, you can extract all the measurements concerning the limestone part from a borehole).

The experimental measurements can be linked to the geological logs if they are registered with the same depths.

Conventions: the file “geological log” has a line for every change of the geology in the borehole. The relative_z corresponds to the depth where there is a change.

For instance, if in the well there is vegetal soil from 0 to 10m and a limestone from 8 to 15m, there will be 4 lines in the file  geological log for every depth where there is a change (relative z =[0,8,10,15]).

Therefore all log_geological files have in the first line a relative z = 0 with the geology of the top of the borehole.

Integration of raw data and interpreted data

In situ measurement, hydraulics or flow rates measurements are obtained with measurement devices, so the raw data should be inserted. The abnormal values can be suppressed.

For the deformation measurements, we:

• keep the raw data with the timeline of the modifications and change of instruments
• have “clean data” useable by hydrogeologists (without abnormal values, with corrected values), a correct calibration and the correction for the seatides.

Therefore, for tiltmeter measurements of different structures, different templates have been created:

• for the Blums, there is a template with the raw data, the calibrated data and the corrected data
• for the longue bases, there are 2 templates:

1. raw data for each pot
2. treated and corrected data for the inclinometer

This solution ensures the best transmission of data for hydrogeologists. In addition, every operation should also be described in the correct lines/columns.

Spatialized data

The best way to access the spatialized data is to use the Google Earth file created for each site. When integrating spatialized data (map, cross section and 3D block), the image of the interpreted or raw data and the coordinates of the image print at surface are asked to allow data to be displayed on Google Earth. Raw data have to be inserted in a zip file. It is also recommended to join the interpreted or inversed data in this file. A pdf description file of the set up and the data have to be inserted to allow users to understand and use the data. As the data format can differ according to the contributor and the using device, it is recommended to indicate the software used for reading and inversing the data in this description file.