We’re kicking off a 2,500 m RC plus 500 m core program in late January in the Pilbara, bouncing between ridge-top pads, and I need rugged offline GIS and geologic mapping templates that won’t lag behind daily collar moves. If you’ve got field-tested workflows for tablet mapping/structure logging and a simple sample-tracking setup that stays synced with the drill, I’ll trade our 1:5,000 mapping sheets and the drill pad planning checklist that saved us two days last season.
And ran a 2,500 m RC + 500 m core ridge-top shuffle last Jan in the Pilbara; QField + Mergin kept collars current offline with MBTiles, no lag on a Tab Active3. We built one QField form for structure and samples (domains for fabric/attitude, From–To, HoleID), QR-tagged bags, and mirrored it in ODK Collect to sync when the ute hit signal. > that stays synced with the drill, I’ll trade our 1:5,000 mapping sheets and the drill pad planning checklist that Agree — if you’re locked into ESRI, Field Maps works, but it chews battery compared to QField.
Ran 3 km RC+core last wet in the Pilbara; Mappt + one GeoPackage with coded domains kept mapping snappy, and Resilio Sync pushed the driller’s end‑of‑shift collar CSV to tablets so a ‘Collars_live’ layer never lagged. For structure, FieldMove exports to CSV we append nightly; only caveat — fix everything to GDA2020 and use lightweight MBTiles or your Tab Active3 will stutter. @lucas7932’s QField/Mergin is solid, but this setup has zero account overhead when you’re bouncing ridge‑top pads.