Any name you like — it just labels the job on your job history page and in downloads. It doesn't need to match anything in your files.
A CSV file (comma-delimited) with one row per boring. Only these columns are read: boring_id,
easting_m, northing_m, crs, and,
optionally, ground_surface_elev_ft. Extra columns (like total_depth_ft,
push_date, and notes in the example below) are
ignored.
The ground_surface_elev_ft column is optional, and its
values aren't used in any output yet: depths are measured from each
boring's own ground surface, and the 3D view, 2D view and volumes
treat the ground as flat. If you include it, its values must be
numbers or blank.
crs names the coordinate reference system your
easting_m/northing_m values are in, as an
EPSG code in the form EPSG:#### — it must be a real,
projected CRS (not latitude/longitude) whose units
are meters, such as a State Plane zone or a UTM zone. Every row in
the file must use the same CRS — a job can't mix
coordinates from two different systems. Not sure of your survey's
EPSG code? Look it up at the official
EPSG Geodetic Parameter Dataset registry.
| boring_id | easting_m | northing_m | crs | ground_surface_elev_ft | total_depth_ft | push_date | notes |
|---|---|---|---|---|---|---|---|
| SB-01 | 421406.71 | 1206859.74 | EPSG:6396 | 652.8 | 24.0 | 2026-03-11 | site perimeter, background (NW) |
| SB-02 | 421430.48 | 1206845.72 | EPSG:6396 | 651.6 | 28.0 | 2026-03-11 | source-area push, LNAPL smear zone expected near water table |
| SB-03 | 421427.43 | 1206825.91 | EPSG:6396 | 651.0 | 20.0 | 2026-03-11 | downgradient push, rod-connection gap ~10-11.5 ft bgs |
| SB-04 | 421454.25 | 1206857.91 | EPSG:6396 | 653.1 | 22.0 | 2026-03-11 | site perimeter, background (NE) |
| SB-05 | 421402.44 | 1206809.14 | EPSG:6396 | 650.4 | 23.0 | 2026-03-12 | site perimeter, background (SW) |
| SB-06 | 421459.13 | 1206814.63 | EPSG:6396 | 650.9 | 21.5 | 2026-03-12 | site perimeter, background (SE) |
| SB-07 | 421434.14 | 1206864.62 | EPSG:6396 | 652.9 | 25.0 | 2026-03-12 | site perimeter, background (N) |
| SB-08 | 421433.53 | 1206803.05 | EPSG:6396 | 650.6 | 22.5 | 2026-03-12 | site perimeter, background (S) |
| SB-09 | 421435.05 | 1206835.97 | EPSG:6396 | 651.3 | 26.0 | 2026-03-13 | interior push, near-source transitional response |
| SB-10 | 421428.96 | 1206815.24 | EPSG:6396 | 650.7 | 24.0 | 2026-03-13 | interior push, far-downgradient trace response near plume edge |
Example CSV format. Only the required columns listed above are read, others are ignored.
One CSV file (comma-delimited) per boring. Name each file to match
its Boring ID in the coordinates CSV above (e.g. SB-01.txt
for boring SB-01), exactly, including upper/lower case.
Every log file needs a row in the coordinates CSV, and every row
needs a log file; an upload where they don't pair up is rejected
with a list of the names that don't match. Only these columns are read:
depth_ft, pct_re, ch1_pct,
ch2_pct, ch3_pct, ch4_pct.
depth_ft is depth below ground surface in feet.
pct_re is the total %RE, and ch1_pct to
ch4_pct are each channel's own %RE, so the four add up
to pct_re.
Extra columns (like rate_ft_min, ec_depth_ft,
ec_ms_m, and hammer_bpf in the example below)
are ignored.
| depth_ft | pct_re | ch1_pct | ch2_pct | ch3_pct | ch4_pct | rate_ft_min | ec_depth_ft | ec_ms_m | hammer_bpf |
|---|---|---|---|---|---|---|---|---|---|
| 0.0 | 3.35 | 0.69 | 1.89 | 0.44 | 0.33 | 2.36 | 0.15 | 7.2 | 10.6 |
| 0.05 | 3.82 | 0.66 | 1.44 | 1.55 | 0.18 | 2.15 | 0.2 | 18.3 | 7.1 |
| 0.1 | 3.33 | 0.76 | 1.22 | 1.06 | 0.28 | 2.22 | 0.25 | 14.9 | 20.5 |
| 0.15 | 1.7 | 0.15 | 1.08 | 0.25 | 0.21 | 2.2 | 0.3 | 5.5 | 11.8 |
| 0.2 | 3.91 | 1.06 | 2.26 | 0.26 | 0.32 | 2.22 | 0.35 | 16.6 | 8.7 |
| 0.25 | 3.45 | 0.68 | 1.76 | 0.74 | 0.26 | 2.29 | 0.4 | 5.9 | 17.6 |
| 0.3 | 2.46 | 0.82 | 0.73 | 0.76 | 0.16 | 1.98 | 0.45 | 20.6 | 7.9 |
| ... | ... | ... | ... | ... | ... | ... | ... | ... | ... |
Example CSV format. Only the required columns listed above are read, others are ignored.
A georeferenced site image (e.g. a satellite photo or site plan), shown as a ground-level reference layer in the 3D view and under the 2D view. Any coordinate reference system is fine, it's reprojected automatically into whichever CRS your coordinates file above declares. Up to 250 MB; large images are downsampled for display. Not required for job submission. Cannot be added to jobs after they have been run.
Either upload a georeferenced TIFF/GeoTIFF on its own, or select a
JPG, PNG or TIFF together with the GIS files that come with it: its
world file (e.g. site.jgw for site.jpg) and
its site.jpg.aux.xml or site.prj, which
says which coordinate system it's in. Keep the names your GIS gave
them, since they're matched by name. An ArcGIS metadata file
(site.jpg.xml) can be included and is ignored.
For UVOST logs exported from Dakota Technologies' OST software,
choose Dakota OST export in the Template picker and
upload each boring's .lif.dat.txt file as it is, with
or without its header row. The boring ID is the part of the file
name before .lif.dat.txt (e.g.
UV-01.lif.dat.txt for boring UV-01), and
it must match a row in the coordinates CSV, which uses the same
layout as the Default template above.
These exports don't record whether depth is in feet or meters, so
the form asks for the depth unit. To have it checked, also select
each boring's .lif.raw.bin file along with the logs:
its header records the unit the logs were taken in, and an upload
where it doesn't match the unit you chose is rejected. The
.lif.raw.bin files are only read for that check.
Total %RE comes from the Signal column, and the four channels from Ch1 to Ch4. The EC and hammer columns aren't read, since the export writes zeros in them when no EC probe or hammer was logged.
The Default and Dakota OST templates above cover the standard file layouts for boring logs, coordinates, and a site image. If your organization's own files use a different layout, we can build a custom template matched to your exact format, covering all three file types together. Once set up, it appears as an additional option in the Template picker on the upload form.
Custom templates are available directly from lif-viz — contact us to have one built for your organization.