Turn raw field data into CAD-ready coordinates in your browser.
Drop a JobXML, RW5, RXL, or point CSV file, localize ground-to-grid, transform to State Plane or UTM, validate on a live map, and export LandXML. Local processing requires no upload. Nothing to install.
Parsing, projection, validation, and export all run on this device.
Projections use the Krüger n-series (GeographicLib-equivalent, sub-nanometre) and Snyder Lambert Conformal Conic, with zone parameters transcribed from EPSG v11.022.
Saved jobs live in your browser. Open workspace to resume one.
Supported survey formats
FieldToCAD parses Trimble JobXML (.jxl), Carlson RW5 (.rw5), Trimble RXL (.rxl), and point-list CSV/TSV files. Binary collector formats (.job, .dc) are rejected. Export text from your data collector.
- JobXML to LandXML
Convert Trimble Access JobXML (.jxl) files to LandXML for Civil 3D. Client-side ground-to-grid local…
- RW5 to State Plane
Transform Carlson Survey RW5 field files to NAD83 State Plane coordinates in the browser. Ground-to-…
- RXL conversion
Parse Trimble RXL alignment and survey files, localize to State Plane, and export LandXML with clien…
- CSV point import
Import point-list CSV or TSV files with point id, easting, northing, elevation, and code columns. Re…
State Plane and UTM targets
Preview common targets for localized survey coordinates. The native catalog includes official NAD83(2011) SPCS, NAD83 UTM 13N, and WGS84 UTM global targets; specialized CRS and SPCS2022/NATRF2022 preliminary references stay blocked until final validated engines are available.
- Colorado North (NAD83(2011), ftUS)NAD83(2011) · Lambert
- Colorado Central (NAD83(2011), ftUS)NAD83(2011) · Lambert
- Colorado South (NAD83(2011), ftUS)NAD83(2011) · Lambert
- UTM Zone 13N (NAD83(2011), m)NAD83(2011) · Transverse Mercator
- Colorado Statewide (SPCS2022 / NATRF2022, m) - ReferenceNATRF2022 · LambertReference
How it works
Four steps from raw field file to Civil 3D-ready LandXML, with a visual sanity check at every parameter change.
- Step 1
Drop file
- Step 2
Localize
- Step 3
Transform
- Step 4
Export
Active Armor catches a mislabeled grid before it reaches CAD
When a file arrives as already-reduced grid coordinates, FieldToCAD inverse-projects the coordinate centroid back to latitude and longitude and checks it against the source zone's guard envelope. If a job tagged “Polska 2000/18” actually falls inside a Colorado State Plane zone — or a localization would double-scale coordinates that are already on the grid — export and scale tools stay in Inspect Only until you confirm the CRS.
No coordinate leaves your browser to make this decision. The guard runs locally on the same projection math used for export.
- Inverse-projects the reduced-grid centroid through the matched zone's Transverse Mercator or Lambert Conformal Conic math.
- Tests the resulting latitude/longitude against a per-zone guard envelope sampled from NGS fixtures (0.35° margin).
- Rescales metric ↔ US survey feet before the check, so a unit mismatch can't quietly false-pass.
- Runs again on the target zone using the localized centroid, and keeps export plus the combined scale factor locked until both pass.
Features
100% client-side
Files are read into browser memory with the FileReader API. No survey data ever leaves your machine, so there is no B2B security review to pass.
See it before you export
A live canvas redraws as you change rotation, scale, or zone. A wrong parameter visibly distorts the map before it ever reaches Civil 3D.
Ground-to-grid reduction
4-parameter conformal localization with combined scale factor, plus Krüger-series Transverse Mercator and Snyder Lambert Conformal Conic projections. Auto-CSF from elevation and geoid separation.
Recent projects, on your disk
Jobs persist locally via OPFS / IndexedDB. Close the tab, reopen, and your session is restored with zero server calls.
Who it's for
Office technicians and surveyors who manually rotate, scale, and shift raw field points into State Plane before importing to Civil 3D and want a faster, visual, private alternative to spreadsheets.
Frequently asked questions
- Does FieldToCAD upload my survey coordinates?
- No. Parsing, localization, projection, and visualization run entirely in your browser. Survey coordinates are read from your file into browser memory and never sent to our servers. Optional cloud features (saved localization presets and billing) store only metadata, not coordinates.
- What file formats does FieldToCAD support?
- FieldToCAD supports Trimble JobXML (.jxl), Carlson RW5 (.rw5), Trimble RXL (.rxl), and point-list CSV/TSV imports. Binary formats like .job and .dc are not supported. Export a text-based file from your data collector instead.
- How does ground-to-grid localization work?
- FieldToCAD applies a 4-parameter 2D conformal (similarity) transform: scale, rotation, and east/north shifts. This is the standard Helmert localization used by survey crews to reconcile a localized ground grid with an official coordinate reference system.
- What is a combined scale factor (CSF)?
- The combined scale factor is the product of the grid scale factor (from your State Plane or UTM projection) and the elevation factor (from your project height above the ellipsoid). It is the scale value s in your localization that reconciles ground distances with grid coordinates.
- Does FieldToCAD support SPCS2022 and NATRF2022?
- Yes, as a clearly labeled preliminary reference only. SPCS2022 and NATRF2022 are NGS preliminary products as of 2026 and are not yet officially adopted, so production export is disabled until final definitions and transformations are implemented.
SPCS2022 / NATRF2022 support is included as a clearly labeled preliminary reference, tracking the NGS preliminary definitions. Production export is disabled for these targets; production work defaults to official NAD83(2011) State Plane.
Free to start. Pro at $79/mo or $699/yr.
Parse, localize, and validate for free. A Pro seat unlocks unlimited LandXML / .fbk export for production work.
View pricing →