← All posts

— Tag

#crs

5 posts tagged crs.

#landledger (7) #crs (5) #fieldintel (5) #transmission (5) #data-centers (4) #market (4) #pointscout (4) #row (4) #ai (3) #gotchas (3) #mobile (3) #workforce (3) #field-workflow (2) #institutional-memory (2) #qc (2) #state-plane (2) #theo (2) #android (1) #archive (1) #audit-report (1) #bidding (1) #cost-and-roi (1) #data-quality (1) #datum (1) #deliverables (1) #easements (1) #eminent-domain (1) #epsg (1) #feedback-loop (1) #ferc (1) #field (1) #field-crews (1) #field-to-finish (1) #heath (1) #indiana (1) #ingest (1) #ios (1) #leverage (1) #local-grid (1) #monument-recovery (1) #pnezd (1) #product-tour (1) #project-management (1) #prompt-engineering (1) #quality-control (1) #re-visit (1) #records (1) #right-of-way (1) #survey (1) #utilities (1) #verification (1) #vlm (1)
— crs

One Digit, Half a State

Indiana's state-plane family is four EPSG codes that sit one digit apart: 2965, 2966, 2967, 2968. Two of them differ by half a state; two of them differ by tenths of a foot. Mislabel a file with the wrong one and you get either an error so loud somebody 'fixes' it wrong, or one so quiet nobody notices until a corner will not check. Here is how the family fits together, the two ways it fails, and the ten-minute habit that catches both.

August 2026 · 5 min read
— crs

Reading a CRS Verification Report: A 3-Minute Walkthrough

When a customer hands over an archive sample for FieldIntel profiling, the deliverable on Day 7 is a four-page PDF with a status breakdown, a basemap-overlaid cohort, a per-point table, and a caveats section. Here's how to read each part of it -- what each status means, where to look for systematic problems, and how to know whether the configuration is ready to deploy.

June 2026 · 7 min read
— crs

Datum-Free PNEZD: When the Numbers Look Like State Plane But Aren't Declared

A PNEZD CSV lands on your desk. The northings are in the 500,000s. The eastings are in the 1,800,000s. It looks like a clean state-plane file -- except nobody declared which state plane, which datum, or which units. Picking 'looks about right' from a dropdown can put your final coordinates 30 to 100 feet off the truth. Here's how to read the file before you import it, what assumptions you can and can't make from the magnitudes alone, and when to pick up the phone instead of guessing.

May 2026 · 9 min read
— crs

Local-Grid Coordinates: When 'Northing 5000, Easting 5000' Means Nothing

Older boundary surveys often use an arbitrary office origin instead of a real coordinate datum. The PNEZD looks fine. The numbers add up. But there's no way to put those points on a map without a ground-truth anchor. Here's how to recognize a local-grid archive, what you can and can't do with it, and how to pull it into a real CRS when you have to.

May 2026 · 7 min read
— crs

When 'State Plane' Isn't State Plane: The Custom-Scale-Factor Trap

Some surveying firms apply a custom scale factor or rotation to their state-plane work to align with a local monument. The PNEZD output looks like normal state plane to any downstream tool -- but verification points land 5 to 50 feet off. Here's how to spot it, diagnose it, and fix it.

May 2026 · 6 min read

Get new posts in your inbox

Roughly weekly. No filler. Unsubscribe with one click.