Poles, towers and conductors, detected and matched to your register.
Sub-10cm drone or aerial imagery in, a list of what stands in the field against what your GIS says, out.
- GSD
- UAV, under 10 cm
- Cadence
- Annual, on your flight schedule
- Platform
- Drone or crewed aircraft
- Spectral
- RGB
- Export
- Shapefile or geodatabase
- Delivery unit
- One flight area
Files in the delivery
| No. | File | Format | What's in it |
|---|---|---|---|
| 01 | Detected structure layer | Shapefile / geodatabase feature class | One point per pole or tower the imagery shows, with a structure type and a match status against your register. It comes as a file for your own import process. |
| 02 | Conductor runs | Shapefile / geodatabase line feature class | Lines drawn between detected structures where the wire can be seen in the imagery. One line per span, joined to the structures at each end. |
| 03 | Match report | CSV | Every detected structure and every register record, each marked matched or unmatched, with the register ID where there is one. This is the list your technician works through. |
| 04 | Unmatched list | CSV | Only the exceptions: detected structures with no register record, and register records with nothing detected at their location. It can go to the crew doing field verification. |
| 05 | Flight coverage layer | Shapefile / geodatabase polygon feature class | The footprint the imagery actually covered, so a register record outside it reads as not flown rather than missing. |
How it works
01In
Supply your AOI and register
Send the flight area as a boundary and your register extract with structure IDs and coordinates, as a shapefile or geodatabase export.
02Process
Capture
A drone or aerial pass over the AOI at under 10 cm. If you already have imagery from your own flight, say so before anything is booked.
03Process
Detection
Poles, towers and conductors are detected in the imagery and given a location and a type.
04Out
Reconciliation and delivery
The detected set is matched against your register. You get the files above for your own import process.
Limits
| Condition | Effect on the output |
|---|---|
| Resolution floor | Under 10 cm is the useful floor for this offer. At that size a pole is only a few pixels across, enough to detect and locate but not to tell wood from composite. A conductor is thinner than a pixel, so it shows as a faint line and may break in glare or against a busy background. Coarser imagery loses small structures and most conductors. |
| Detection and counting only | The output says a structure is there, where, and what type. It does not say what shape it is in, and it reads nothing about lean, rot or corrosion. |
| Not the register | The detected set is an input to your reconciliation. Your register stays the record, and an unmatched structure is a question for your crew, not a correction to apply. |
| Point in time | The set is as current as the flight. Anything built or removed after it is invisible until the next pass. |
| Cover and clear-sky windows | Tree canopy can hide a pole, and a pole close to a building or in deep shadow may be missed. Cloud stops a crewed aircraft and wet or windy days stop a drone, so a flight can slip. |
| Attributes stay yours | Owner, pole class, installation date and the rest of your attributes are not in the imagery. The match carries them over from your register when a structure is matched. |
Why this exists
The register drifts. Replacements, storm rebuilds and contractor additions land in the field before they land in the geodatabase. Today a crew walks or drives a circuit with a printout or a tablet and checks the feature class against what stands there, or nobody looks until an outage sends a crew to a pole the map has wrong.
It covers a slice of the system per season, and the slice you skipped is the one that is out of date.
Who it's for
For
- GIS and asset data managers who maintain the pole and tower feature classes
- Teams closing out the annual register and needing to know where to send crews
- Utilities with drone or crewed-aircraft flights already scheduled, or planned
Not for
- Teams after asset condition: rot, lean, corrosion or conductor sag
- Real-time or continuous monitoring of the network
- Utilities looking for a replacement for their register or for field verification
- Imagery coarser than the resolution above
Technical and procurement questions
Does this replace field verification?
No. An unmatched structure still needs a person to confirm it. The unmatched list gives your crews somewhere to start.
Does it assess asset condition?
No. It detects and counts. It gives you no view on rot, lean, corrosion or conductor sag.
What if we don't fly at this resolution?
Detection of small structures and thin conductors gets worse as the pixel gets larger. Sub-10cm is the floor this offer is built on. Tell us what you fly and we'll say plainly whether it works.
Can the output load straight into our GIS?
It is delivered as shapefile or geodatabase for your own import process. We don't write into your geodatabase.
How do we check it against our own records?
Pick a circuit group your crews walked recently. Compare the matched and unmatched lists against what they found, and decide whether it is good enough to point a crew with.
How current is it?
As current as the flight. This is not continuous monitoring, and a structure changed after the flight will not show.
Who owns the results and the imagery?
Ownership and licence terms for the files and the imagery are written into the agreement before anything is flown. If your legal team needs to review them, ask early.
How is it priced?
We don't publish a price. Tell us the flight area and what imagery you have, and a person will come back with a quote.
Send us the flight area and your register format.
Tell us what you fly, how the register is held and how many structures are in scope. We'll say what the imagery can and can't answer.
Get started