How to build a daily imagery log for a named airfield

If you're watching one airfield instead of a whole country, the job stops being about finding imagery and starts being about not losing track of what you found yesterday. A single missed pass, a cloud-out day, or a sloppy filename convention and you've lost the thread on whether that line of fighters on the north apron moved, or whether it's just a new tile angle making three aircraft look like four.
A daily imagery log is the fix. It's a dated record, one entry per collection, that tracks what's parked where, what's under construction, and what's changed since the last clean look. Here's a method that holds up over months, not just for one week of heightened interest.
Set your baseline before you start counting
Before the log means anything, you need a reference pass. Pick a recent, clear, low-off-nadir image of the field and treat it as day zero. Mark the apron sections, the revetments or hardened shelters, and anything mid-construction, a new taxiway stub, a shelter with a roof but no doors yet, a runway segment that's been resurfaced. Compare every later entry back against that reference, not only against the previous day's entry. Day-to-day comparison alone lets slow changes sneak past you, because nothing looks different from 24 hours ago even though the field looks completely different from 60 days ago.
Write down the sensor and approximate resolution for the baseline too. If you're pulling from more than one archive, a 50cm pass and a 30cm pass of the same ramp will show different aircraft counts just from pixel detail, and that's worth a note in the log rather than a mystery six weeks later.
Decide what the log actually records
A log that just says "activity observed" is worthless by week three. Each entry needs to answer the same fixed set of questions every time:
- Date and time of the pass, plus sun angle or shadow length if you're trying to catch nighttime positioning changes
- Aircraft counts by type and by location (apron, revetment, taxiway hold)
- Any aircraft in a position inconsistent with the prior entry
- Shelter or hangar construction status, including doors, roofing, and apparent occupancy
- Runway and taxiway condition, markings, resurfacing, or debris
- Confidence note where the image quality makes a count uncertain
Keep the format rigid. A spreadsheet row or a fixed-template text entry works better than freeform notes, because six months in you'll want to search the log for "first revetment with a roof" and free text won't give that back to you cleanly.
Keep the comparison honest
Catching the false positive is the hardest part of a running log, harder than the collection itself. Shadows lengthen across a season and make revetment counts look different. A tile seam or compression artifact can read as a new structure if you're tired and moving fast. Before you log something as a change, pull the two images side by side at the same zoom and the same rough sun angle if you can manage it. If the two passes are weeks apart with very different lighting, flag the entry as lower confidence rather than calling it a confirmed change.
This is also where paging through an archive tile by tile starts to cost real time. Finding the last clean pass, lining it up against today's, and re-counting the apron by eye is manageable for one field over one week. Over a dozen fields and a few months it turns into the bulk of your day, which is exactly the gap Airfield Activity is built to close, holding the daily counts and the shelter and runway tracking in one running log instead of a folder of screenshots.
Build the habit first, even by hand. Once the log format earns its keep, you'll know exactly what you want automated and why.
Ready to stop rebuilding this log yourself? Have a look at what a running log for your named airfield could look like.