A counter is a record on the map
The unit, where it is, and which trail it counts. The position is the thing that makes a reading mean something two years later.
Trail counters
Use data that lives with the trail
Counter readings usually end up in a spreadsheet named after the month somebody docked the unit. Here each counter is a record on the map, its readings belong to the trail it sits on, and the export is one click when a funder asks.
How it works
Dock the unit, upload the file, keep the numbers
No integration to configure and no gateway to buy. Whatever your counter's own software exports, TrailsIQ takes — and once it is in, it is attached to a place rather than to a filename.
Readings arrive by import
Dock the unit, export from its own software, upload the file. Text, CSV or tab-separated — the usual shapes a counter produces.
Overlapping files are safe
Readings are keyed by counter and timestamp, so the same reading arriving twice is stored once. Dock and import as often as you like without inflating a number.
Each import says what it added
New readings reported separately from the running total, so you can see exactly what that file contributed rather than hoping.
The shape of use, not just a total
Totals over time and how use falls across days and seasons — the pattern that tells you which trail justifies the machine time.
CSV out, for whoever is asking
Export a counter's readings to a file for a grant application, a board pack, or a spreadsheet somebody else insists on.
Why it matters
The number that ends arguments
Counter data is rarely the interesting part of a trail program and is regularly the deciding part of a funding conversation.
Evidence
Use, attached to a place
A count on its own is a number. A count against a named trail, with the trail's own condition history and maintenance record beside it, is an argument — for the resurfacing, for the second trailhead, or for leaving the quiet loop alone.
- On the trail, not in a folder The counter, its readings and the trail are one thing to open.
- Beside the work What that trail cost to maintain sits next to how many people used it.
- Kept across seasons Year-on-year is the comparison that persuades, and it needs last year to still exist.
Whatever you already own
Bring the counters you have
No gateway to buy, no subscription to a second vendor, no brand you are locked into. Dock the unit you already own, upload whatever its software gives you, and the numbers land on the trail they belong to — which is how almost every counter in the field actually gets read.
- Nothing to install on the trail Beyond the counter itself. No gateway, no repeater, no cellular plan for a box in the woods.
- Every brand, because it is a file Text, CSV or tab-separated — the usual shapes a counter produces. Mix vendors across your network and it all lands in the same place.
- The data stays yours Everything you put in comes back out as CSV, whenever a funder, a board or a spreadsheet asks.
Getting started
One counter, one import
The whole loop takes an afternoon, and the second one takes ten minutes.
01
Add the unit
Type, name and position on the map, against the trail it counts.
02
Dock and export
From the counter's own software, whatever range it gives you.
03
Upload the file
Counters → Import. Duplicate readings are dropped, and the summary tells you what was new.
04
Read and export
Totals and seasonal shape on the counter's page, CSV out when somebody asks for it.
Put your use data where the trail is
Start free, add your first counter, and stop hunting for last season's export when the grant deadline arrives.