Archaeology
Compare before you cut.
Set today's lines against last season's magnetics before you open a trench, move a flag, or talk yourself into digging the wrong patch of soil.
ter·ra·scry · noun
Terra, earth. Scry, to perceive what is hidden. TERRASCRY is the field app that redraws the interpretation while the next trace is still hitting your screen — not a week later at a desk, when the missed edge of the feature has already cost you a trip.
Live streams, prior surveys, and outside datasets all live in the same working view. Pathfinder and HIRT plug straight in. They are not the limit.
Who it's for
Different disciplines, same hard moment: you need the next decision before the day is gone, and you need it to hold up once you're back indoors.
Archaeology
Set today's lines against last season's magnetics before you open a trench, move a flag, or talk yourself into digging the wrong patch of soil.
Forensics
Every pass folds into the same interpretation, so you can narrow, shift, or call it off without treating each dataset as its own case file.
UXO and recovery
Pull current data, older site work, and whatever outside layers you can get before you put people into bad ground.
Why it exists
Most surveys still work in two halves. You walk the grid, pack up, and drive home. A week later, at a desk, you realize you missed the edge of the feature, or spaced the lines wrong, or ran past the interesting thing without noticing. The software got its patience. You lost ground truth.
The data is not the problem. The fragmentation is. Live feeds live in one tool. Prior surveys live on a thumb drive. A neighbouring team's GPR from two years ago lives in a PDF someone emailed you. You stitch them together by memory, screenshots, and luck, usually while you are already in the mud.
And the call still has to be fast. You need to decide where the next line goes, or whether to drill, in the time it takes someone to change a battery. But the decision has to hold up later, in a report, in a review, in court. Speed and rigor usually get treated as a trade. They should not be.
Workflow
TERRASCRY keeps the interpretation moving with the fieldwork.
Step 01
Drop in prior surveys, outside datasets, and anything you are already pulling live. Put the site's history on the table before you add another line.
Step 02
Live traces roll in over satellite maps and imported surveys. Pin anomalies, drop notes, and argue with yourself while the instrument is still in your hands.
Step 03
Another Pathfinder pass. A HIRT setup between boreholes. A different modality. Tighter spacing. Or nothing — because you already have what you came for.
Step 04
Position, notes, targets, and raw data travel together. When the campaign ends you hand over a record that actually holds up, not a zip file of guesses.
System
Pathfinder and HIRT plug straight in. So does whatever else you dragged out of the truck — other people's mag data, somebody's GPR, a resistivity line from last year. If it has coordinates and values, it belongs on the map.
Pathfinder
Strap it on and walk. Pathfinder finds the edges of an anomaly in a hurry, so you are not dragging high-resolution gear across empty dirt.
HIRT
Once you know roughly where the target is, HIRT drops between boreholes and gives you the sharp subsurface picture no surface pass can touch.
TERRASCRY
Pathfinder, HIRT, other people's instruments, a dusty CSV from a decade ago — they all live in the same interpretive loop instead of three separate windows.
Principles
TERRASCRY is open source. The code, the hardware, the workflow — all of it is inspectable. If you don't trust how we filter the data, open the repo and look. If a method matters, you should be allowed to look at it.
It has to be affordable enough that a university lab or a two-person consultancy can actually use it, not just a well-funded agency. Budgets should go to time in the field, not to licenses that expire when you cancel.
And it has to survive the dirt. Mud, brush, weather, short setup windows, bad light, muddy gloves, cold hands — these are the normal conditions, not edge cases. The app is built to act like it knows that.
The point is to help the person holding the instrument decide what to do next — not to generate something pretty for a slide deck after the campaign is over. You drive the interpretation. The app hands you the raw signal and stays out of your way.
We don't care what the signal came from. Radar, magnetics, resistivity, EM, gravity, someone else's borehole log. If it helps answer the question, it belongs on the map. The interpretation has to stay modality-agnostic or it is not actually open.
Underneath all of that, the workflow answers to real physics, not to images that happen to look convincing. Coordinates close. Assumptions are explicit. The answer you give in the field is the same answer you can defend in a report.
Figure out what you're standing on before you leave the site.
Talk to us