— StrataLogic Blog
Field-to-finish, written down.
Notes on coordinate-reference systems, the cost of the re-visit, and how PointScout + FieldIntel actually work in production. New posts roughly weekly.
How Much Does It Cost to Forget?
A survey firm's real asset isn't its trucks or its instruments -- it's the forty years of plats, field books, and deeds in the back room. That archive is also the firm's most expensive liability, because the moment you need it, the answer is buried in a filing cabinet or in the head of someone who retired last spring. Here is what forgetting actually costs a firm, why 'just search it' has never worked on this kind of data, and what it takes to make decades of records answer a question in seconds.
The Agreement That Went Silent
The parcel that blows a right-of-way schedule is almost never the one you're fighting over. It's the easy one that went quiet -- an offer went out, the owner didn't sign, nobody was counting the days, and three weeks quietly became three months. Here's why the silent stall is the most expensive failure mode in ROW acquisition, why a line list can't see it coming, and what it takes to catch it before it costs you the in-service date.
What FERC's Data-Center Orders Mean for the Land-Rights Desk
On June 19 FERC issued six orders telling the country's regional grid operators to write new rules for how data centers plug into the grid. Read quickly, they look like procedural homework for grid engineers. Read closely, they are about three things -- cost, accountability, and documentation -- and all three eventually land on the desk of the people who acquire the land a transmission line has to cross. Here is what the orders say, and why the right-of-way workload behind the data-center buildout just got more scrutinized, not less.
Why We Replaced 'Extract' With 'Transcribe' (And Got 7x More Data)
FieldIntel ingests handwritten field books by asking a local vision-language model to read each page. The original prompt asked the model to extract and organize what it saw -- and produced confident hallucinations on roughly half the regions we tested. Replacing 'extract and organize' with 'transcribe verbatim' lifted total entity extraction by 6.7x on the same model, same hardware, same input. Here's the test, the failure mode, and the one-line config change that shipped in v1.2.2.
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.
What 2.2 GW Means for Land Rights
AWS announced an Indiana data center campus that needs 2.2 gigawatts -- roughly half the electricity all Indiana households use combined. That power has to come from somewhere, and it has to travel over wires that don't exist yet. Behind the data-center buildout sits a transmission expansion of historic scale, and behind that sits a less-talked-about bottleneck: every mile of new line requires parcel-by-parcel land rights work. The shape of the market that's about to need ROW software is not the shape the incumbents were built for.
Field-Side QC vs Office-Side QC: Why Catching Errors at the Truck Beats Catching Them in CAD
The traditional surveying QC model puts the heavy lift in the office, after the crew has packed up and gone home. There's a better-shaped split: real-time, automatic checks at the truck for the predictable busts; office-side review for the subtle and the legal. Here's the specific QC menu worth running on the field side, why it earns its keep, and what's still office-only.
The Hidden Cost of the Re-Visit: A Math Walkthrough
A re-visit is not just the half-day a crew spends back at the site. It's the surveyor's time, the truck, the schedule slip, the customer relationship, and the job that didn't get done that afternoon because everyone was at the wrong site. Here's the math on a typical 10-person firm and where the cost actually concentrates.
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.
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.
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.
Get new posts in your inbox
Roughly weekly. No filler. Unsubscribe with one click.