Perspective ·
Wildlife monitoring's bottleneck isn't the camera
Cameras and recognition models keep getting better. The weak link is the chain from field footage to a record you can still trust after several seasons.
It's tempting to think wildlife monitoring is solved. Cameras are cheap and everywhere, recognition models label species automatically, and every season brings more footage than the last. But a park or a research group doesn't need a pile of labelled images. It needs a monitoring record it owns, one that can be compared across sites and seasons and still makes sense after the people who built it have moved on. That record is the part that's still immature. The sensors have moved ahead of the system around them.
Good tools do exist
To be fair, plenty exists. There are research platforms for managing camera-trap studies, detectors that reliably find an animal in a frame, and an open standard, Camtrap DP, for moving data between them. What's usually missing is the whole chain run as one layer that an organisation owns, from intake and effort to review, provenance and export, and that keeps working when people and seasons change. Most existing tools are built for research, tied to one vendor, or assume someone technical will glue the steps together by hand.
More cameras don't make better management
A camera is a sensor. A monitoring programme is an operation. The sensor keeps improving, with higher resolution, faster triggering and detection on the device. The operation has barely been built as a product. It means getting footage in reliably, keeping it organised, noticing when a camera goes quiet, checking the uncertain calls, and turning it into numbers that hold up over years. Most of that still happens by hand, on someone's laptop, in a spreadsheet only they understand. More cameras make the pile bigger. They don't make the record better.
Where the chain breaks
Ask people who run camera-trap programmes where their time goes and it's rarely the cameras. It goes into data management, meaning sorting images, archiving and quality control, the work that seldom shows up in a paper or report. The same problems come up again and again.
- Backlog. Collection outpaces processing. Drives fill up and a comparable record never forms.
- Lock-in. Footage lives in a manufacturer's app or a closed cloud, in a format that's hard to get out of. Change tools and the history stays behind.
- Missing effort. The counts get recorded, but the survey effort behind them often doesn't. Which cameras were out, and for how long? Without that, numbers can't be compared honestly.
- Weak export. What comes out is a CSV layout a vendor made up, not something another tool or a national repository can read.
- Seasons that don't connect. Each campaign stands on its own. Staff change, the method drifts, and year three can't be lined up against year one.
In Europe it's more fragmented still. Monitoring schemes differ by country, and raw data is often not standardised or easy to reach. That's part of why the camera-trap community settled on open formats like Camtrap DP. Standards tend to appear while a field is still sorting itself out.
What a mature setup would look like
A mature setup wouldn't be exotic. It would just do the dull things reliably.
- Footage arrives without someone collecting it, and you notice when a camera stops sending.
- It's organised by site and time, not by whoever downloaded it.
- Uncertain identifications get a human check, and the correction stays with the record.
- Survey effort travels with the counts, so seasons can be compared.
- For each detection you can see whether a person confirmed it and what the model said originally.
- You can export everything in an open format whenever you want, because it's yours.
None of that is a research breakthrough. It's plumbing, and most of it is still missing.
Where we fit
That gap is what Untamed Data is built for. We're the operational layer between the field and the systems you report into. Footage comes in over FTP or FTPS, or by upload in the browser, and is organised by project and location. You get an email when a camera goes quiet and a review queue for the uncertain detections. Deployments record the survey effort, and the exports include Camtrap DP. You choose the cameras, and the data stays under your organisation's control, hosted on servers in the Netherlands (EU). Recognition is one normal step in that chain. It's software for real monitoring programmes, and you don't have to join a network to use it.
The cameras are the easy part. The work that's left is building a record that still means something after the grant ends and the team changes. That's what we're working on.