Key takeaways
- A municipality buying one aerial capture a year is buying a time series, and the time series is worth more than any single flight in it.
- One flight normally serves several departments at once: public works, planning and development, asset management, and whoever reports on the gravel pit.
- A recurring capture is usually an operating expense rather than a capital one, which is a different approval path and a different line in the budget. Confirm the treatment with your CAO before it goes to council.
- Comparability is a design decision made before the first flight: same vertical datum, same ground control, same altitude and overlap, same deliverable list, every year.
- Two captures a year, after spring breakup and before freeze-up, suits most municipalities. One, flown at a consistent time of year, is enough to start.
- Decide before the first flight who owns the data, who inside the organisation can release it, and what goes on the public map. That is a FOIP and policy question, not a drone question.
- An aerial capture is not a legal survey and does not replace a professional surveyor for boundaries, nor an engineer for structural assessment.
Most municipal drone work in Alberta is incident-driven. A gravel pit needs a volume for year end, a culvert fails, a developer disputes a grade, a council member asks how much of the ditch program actually got done. Each one becomes a separate little procurement, a separate flight, a separate file that lives on one person's laptop.
The alternative is to buy one capture a year on a schedule, treat it as a municipal record rather than a project deliverable, and let every department draw on the same dataset. The individual flights cost the same. What changes is that after three years you have something no single flight can give you, which is a dated, measurable, consistent record of the whole municipality over time.
The uses that pay for it
A single annual capture of a town or county's developed area and its own facilities feeds several budgets at once. The ones that come up most often in Alberta:
- Gravel pit volumes. A municipal pit needs a stock figure for reporting, for royalty or levy reconciliation, and for planning next year's crushing. A drone survey produces it without shutting the pit or sending someone up the pile, and the method is set out in drone stockpile measurement. Reconciling it against hauled tonnage is covered in volume versus scale-house tonnage.
- Road and ditch condition. An orthomosaic of the road network at a consistent resolution shows surface condition, shoulder loss, standing water, ditch blockage and where last year's program was actually built. It is a defensible basis for next year's priority list, and it is the same record a councillor can be shown in a meeting.
- Asset inventory and condition evidence. Culverts, approaches, signage, lagoon cells, yards, pads, reservoirs, arena and shop roofs. Grant and funding programs increasingly want to see an asset management plan with condition evidence behind it, and dated imagery is evidence. Confirm the current documentation requirement with whoever administers the program you are applying to.
- Development monitoring. A dated capture settles whether a subdivision was built as approved, whether a stripped site was stripped past its permit, how far a lot grading plan got, and when a condition was satisfied. It is cheaper than an argument.
- Pre-event baseline. After a flood, fire, washout or wind event, the question is always what it looked like before. A municipality with last spring's capture can answer that. One without it cannot, at any price.
- Public works record keeping. Pre-construction and post-construction captures of a capital project become part of the project file and the as-built record, which is the subject of comparing an as-built against a design surface.
No single one of those usually justifies a program on its own. Together they generally do, because the marginal cost of a second department using the same capture is zero.
Why a program beats five one-off flights
Three reasons, and the third is the one that matters most.
The first is price. One mobilization covering a planned area beats five separate call-outs, each with its own travel, setup and minimum.
The second is administration. A single scope approved once a year replaces five small procurements, five scope conversations and five invoices, each of which consumes staff time that nobody budgets for.
The third is comparability. Two captures flown by different methods, to different accuracy, on different control, with different vertical datums, cannot be reliably differenced. If the ditch looks shallower this year, you cannot tell whether it silted in or whether the datum moved. A program flown the same way each year produces a measurable change, and a measurable change is the thing a municipality actually wants: how much material moved, how much the berm settled, how much of the program got built.
Where it sits in the budget
This is where most municipal aerial programs die, so it is worth getting the mechanics right before the idea reaches council.
A recurring annual capture behaves like an operating expense. It buys a service and a record consumed in the year, it recurs, and it does not create a capital asset. That usually puts it in the operating budget under public works, planning or administration, depending on which department sponsors it. A one-time baseline capture tied to a specific capital project is a different case and often rides that project's capital budget instead. Which treatment applies to your municipality is a question for the CAO or the director of finance, and it is worth asking before writing the request, because the two follow different approval paths and different reserve rules.
Alberta municipalities adopt a budget annually and maintain multi-year operating and capital plans alongside it under the Municipal Government Act, so an annual recurring service is easier to defend than it looks: it is a predictable, fixed, repeating line rather than a surprise. Confirm the current plan requirements and timelines with your CAO, since the Act and the funding programs around it change.
Two practical notes on getting it approved. Present it against the line it displaces rather than as new spending, which is the framing set out in where a drone survey fits in a project budget: the pit survey you were buying anyway, the consultant trip you will not need, the staff days spent walking ditches. And handle the procurement once. A multi-year standing offer or a term agreement under your purchasing policy, rather than an annual re-tender, keeps the method and the vendor consistent, which is precisely what the comparability argument requires. Your purchasing policy and thresholds govern whether that is available.
Designing the program so year two is comparable to year one
Comparability is not something you can add later. It is a set of decisions made before the first flight, and written into the scope so that every subsequent year inherits them:
- Fix the coordinate system and the vertical datum, and name them. They have to match whatever your engineering drawings and GIS already use. Choosing wrongly produces a dataset that appears shifted against everything else you own, as explained in which coordinate system your drone survey should be in and vertical datum and geoid.
- Establish permanent ground control. Surveyed, marked, reusable points that the same crew re-occupies every year. This is the single biggest contributor to a difference you can trust, and it gets cheaper every year after the first.
- Fix the capture specification. Same flight altitude and overlap, so the ground sample distance is the same every year, which is what GSD controls.
- Fix the deliverable list and the formats. Decide once what you receive and in which formats, matched to the software your staff actually have, which is the subject of who on your team can open the deliverable. A format nobody can open is not a record.
- Fix the time of year. A June capture and an October capture of the same ditch differ in vegetation, water level and shadow before anything physical has changed.
- Name an owner inside the organisation. One person responsible for where the data lives, who gets access, and that it is still there in five years. A program without a custodian becomes a folder nobody can find.
How often to fly
For most municipalities, two captures a year is the natural rhythm. The first comes after spring breakup, when the roads and ditches show what winter and runoff did, which is also the capture that supports the construction season's priority list. The second comes before freeze-up, covering what was built during the season and closing out the gravel pit year.
One capture a year, flown consistently at the same time of year, is a perfectly reasonable start and is better than three captures flown at random times. Specific assets may need their own cadence on top of the municipal-wide flight, and the reasoning for setting one is in how often you should re-fly a site. Note that seasonal access, road bans and the short winter daylight window all affect which dates are actually available.
What to settle before the first flight
Three items that are policy questions rather than technical ones, and all three are easier to answer before there is imagery than after.
Data ownership and retention. Who owns the raw imagery and the processed products, how long they are kept, and what happens if you change vendors. A municipality building a time series cannot afford to lose the earlier years, and the handover requirements are set out in switching drone contractors and data ownership and retention.
Access and release. A municipal aerial capture includes private property. Who inside the organisation can view it, who can release it, what happens when a resident or a developer asks for a copy, and whether any of it goes on the public map are questions governed by your FOIP obligations and your own policies. Settle them with your FOIP coordinator. The related question of notification and privacy expectations when flying over adjacent land is covered in do you need the neighbours' permission to fly.
Enforcement use. If imagery will be used in bylaw or development compliance, decide that deliberately and with advice, because it changes how the capture is documented and how it has to be handled. What makes a dated capture defensible is a records question as much as a flying one.
What the program does not replace
Being clear about this up front protects the program from the first person who tries to use it for the wrong thing. An aerial capture is not a legal survey and establishes nothing about a property boundary; that is a professional surveyor's work, and the division of responsibility is set out in who signs off drone survey data. It sees the surface only, so it says nothing about pipe condition, subsurface utilities, structural capacity or what is under water. And it is a record of one date, so anything that changed the day after the flight is not in it. The honest list of limits is in what a drone survey cannot tell you.
Within those limits, a municipality that has flown the same ground the same way for three years has something most of its neighbours do not: an answer, with a date on it, to the question of what changed.