Field documentation, former Elk Point equipment yard, Nov 4, 2026

Field logs and photos from the Nov 4, 2026 sampling day: soil borings at the former Elk Point equipment yard and sediment stations in Elk Point Creek below the SR 354 storm drain outfall. Each photo is tied to a boring or station by GPS position or timestamp, the logs are checked against the Sampling and Analysis Plan (SAP), and everything is written to the original Excel templates. Six errors and four warnings need to be resolved before the logs and the chain of custody go out.

Field app: 14 logs, 38 samples, 64 photosElk Point, Nevada · equipment yard and Elk Point Creek at SR 354NAD83(2011) Nevada State Plane West Zone (2703), US survey ft · NAVD 88Prepared Nov 5, 2026

Summary

Location · SB-07

SB-07 was drilled 37 ft from its planned location

The RTK survey and the five photos taken at the boring place it 37.3 ft south of the SAP location, outside the former diesel UST pit it was meant to bound. The SAP requires a documented reason for any offset over 5 ft (SAP Rev B, p. 6), and the boring log has none.

Action: add a step-out boring at the south edge of the pit, or document the reason for the move.

Depths · 3 samples

Three sample intervals don't fit the boring or the core

SB-04-3 (6.0–7.0 ft bgs) is below refusal at 6.0 ft, SB-02-2 and SB-02-3 overlap by 0.5 ft, and sediment sample SED-02-2 (4–8 in.) runs past the 5.5 in. of recovery. Without the check, the intervals would have gone into the template as entered.

Action: confirm the intervals with the field geologist and correct the logs before export.

Chain of custody · 2 mismatches

The highest PID sample of the day is not on the COC

SB-05-2 (2.0–4.0 ft bgs, 48.0 ppm, strong petroleum odor) is marked N on the boring log and missing from the chain of custody, although the SAP calls for analysis of any sample above 10 ppm or with odor (SAP Rev B, p. 9). The COC also lists SB-10-4, which is not on any log.

Action: ask the lab to add SB-05-2 within holding time and void SB-10-4.

Borings, photos and field logs

The site plan shows surveyed borings and sediment stations, SAP locations and photo positions with camera heading. Select a location for its log, photos and issues, or a photo for its EXIF data and how it was tied. The timeline below the plan shows when each location was sampled and when each photo was taken. The Export tab shows how the logs land in the original templates.

Show
Layers
0
0
0
0Errors / warnings
Soil boring Sediment station SAP location Photo with heading Error Warning

Field day timeline

Bars show sampling time per location, ticks show photos.

Tied by GPS position Tied by timestamp Needs a location Overview photo

    Sources and method

    Sources

    • FieldApp_Export_2026-11-04.jsonDigital boring logs (10) and sediment sampling logs (4) with times, depths and field descriptions14 logs, 38 samples
    • Field_Photos_2026-11-04.zipPhotos with EXIF time, GPS position and heading from the rig tablet and the sediment crew phone64 photos
    • SAP_Elk_Point_Equipment_Yard_RevB.pdfSampling and Analysis Plan: planned locations and coordinates, offset tolerance, sample selection for analysis14 pages
    • RTK_Survey_2026-11-04.csvRTK GNSS survey of borings and sediment stations14 points
    • Boring_Log_Template_v3.xlsx, Sediment_Sampling_Log_Template_v2.xlsxOriginal log templates, with a photo log sheet in the boring log template2 files
    • Chain_of_Custody_2026-11-04.pdfHandwritten chain of custody to the lab, scanned2 pages, 18 samples

    Method

    1. Read each log from the field app and checked every sample: required fields, intervals within total depth or core recovery, no overlapping intervals at a location, and a groundwater depth whenever a sample is logged as wet.
    2. Compared each surveyed location with the SAP coordinates. An offset over 5.0 ft without a reason on the log is an error.
    3. Tied each photo to the nearest location within 25 ft. Photos without a GPS position were tied by timestamp to the location the device was logging at the time. A photo taken between two locations needs a manual pick.
    4. Compared samples above 10 ppm PID or with odor against the chain of custody, and checked the COC line by line against the logs.
    5. Wrote the logs into the templates without changing their columns or header rows. Issues are highlighted in the cells.

    Assumptions and limitations

    • Coordinates are in US survey feet (EPSG:6523), a common working unit in Nevada. The statutory unit for the Nevada Coordinate System of 1983 is the meter (NRS 327.030), so deliverables to an agency may need meters.
    • Photo GPS is good to roughly 10–15 ft and the RTK survey to about 0.1 ft. Photos confirm a location; they are not used to measure it.
    • Timestamp matching assumes the device clocks are right. The rig tablet was within 1 second of GNSS time at start-up.
    • Soil descriptions are field classifications per ASTM D2488 (visual-manual procedure) and have not been checked against lab classification.
    • The check does not evaluate analytical results or NDEP action levels, only whether the right samples were submitted.