Has anyone here moved daily as-builts from prism shots and paper logs to an RTK GNSS and ArcGIS Field Maps setup? After three decades with a field book, I’m piloting a Trimble R12i with a shared geodatabase and a short Python QC script to flag outliers, and I’d love hard-learned tips on training techs and keeping the model clean for downstream Civil 3D work. Goal is to set our younger staff up for model-based delivery as this becomes the norm.
Lock Field Maps down with domains/contingent values that mirror your Civil 3D codes, and have your Python QC only pass points with ‘RTK Fixed’, RMS < 0.03 m, and tilt below a threshold from the R12i — , fat-fingered attributes were our biggest mess. We also write to a raw feature layer and run a nightly append to a clean model view so the shared geodatabase stays tidy for Civil 3D; if you haven’t already, enable GNSS metadata so you can filter by PDOP/correction age (https://doc.arcgis.com/en/field-maps/android/help/configure-location.htm). Do your crews do a quick control check at start/end of day?
Biggest win for us was a belt‑and‑suspenders preflight: a start/end control‑check layer plus a hard “no fixed, no record” rule, with an Arcade attribute rule that blocks submits without a benchmark ID and auto‑prompts a second shot if tilt >3°. Pair that with per‑crew branch versions in the enterprise geodatabase — crews sync to their own version, your QC reconciles/posts only clean features to a staging class that your C3D import reads — so bad edits never hit production. @OP do you have two reliable control points near the work each day, or are you planning a quick site localization?
With the R12i, lock a device profile that auto-stamps epoch, PDOP, correction age, firmware, and antenna/rod height to each point so your “short Python QC” and downstream CAD filters don’t chase ghosts. For training, have each tech record a 10‑minute golden sample on known marks and review the stats dashboard together before they hit the site. @chloe_ngu31’s quality gates are solid, but I’d also turn on raw logging for a PPK backstop — are you capturing that?