Vertical vs oblique imagery for structural damage assessment
If you've run a post-earthquake tasking call, someone always asks why the first pass comes back straight-down instead of angled. It's a fair question. Oblique shots look more like what a person on the ground would see, and for a lot of disaster work that's exactly the point. For structural damage grading across a whole affected area, though, vertical wins, and it's worth being specific about why instead of just taking that on faith.
What nadir imagery actually gives you
Nadir, or vertical, imagery is shot looking straight down at the ground. Every structure in the frame gets measured the same way: same angle, same scale, same distortion (none, basically, once it's orthorectified). That consistency is what lets you line up a footprint against a pre-event reference and compare them. Roof collapse, pancaking, debris spread into the yard or street, partial wall loss visible from above: all of that shows up as a geometry change you can measure footprint to footprint.
It also means you can tile a whole city or district in one pass. A collapsed four-story walk-up on one block and a collapsed warehouse three kilometers away show up in the same frame of reference, at the same ground sample distance, so a coordinator can rank them against each other on one scale instead of running separate site visits to compare severity.
Where oblique earns its keep, and where it doesn't
Oblique imagery is shot at an angle, which means you're looking at the side of a building, not just the roof. For some things that's genuinely better. Facade cracking, a leaning wall, a story that's shifted sideways but hasn't dropped its roofline. Those read clearer on an oblique frame than on a straight-down one, because a vertical shot of a building that's still standing can look intact from above even if a side wall has failed below the roofline.
The tradeoff is coverage and consistency. Oblique capture covers less ground per pass, buildings near the edge of the frame get foreshortened and harder to measure, and comparing one oblique shot to another taken from a different angle is genuinely difficult. For an engineer doing a follow-up inspection on one specific structure, oblique is a useful second look. For the first read across a whole affected zone, where the job is sorting thousands of buildings into who needs a team today versus who can wait, that inconsistency is the problem, not a stylistic preference.
Why collapse grading needs the vertical read first
Search-and-rescue triage and shelter planning both run on the same early question: where is the damage worst, right now, across the whole area, so limited teams get pointed at the right blocks first. That's a sorting problem before it's an inspection problem, and sorting needs a dataset where every structure was measured the same way.
That's the case for nadir. At sub-half-meter ground sample distance, a vertical pass resolves individual rooflines, collapsed sections, and rubble footprints clearly enough to grade a structure, and it does it uniformly across the whole captured area, whether that's satellite or aerial. You get a dated, structure-by-structure read of what's down, what's partially collapsed, and what's standing, without waiting on a street-by-street ground survey to work its way through the district.
Oblique still has a role once teams are on the ground and need a facade-level look at a specific address. But as the first cut that tells a coordinator where to send crews before anyone's walked a single block, vertical VHR is the format that does the sorting job.
That's the read Building Damage Classification is built to produce: per-structure damage grades from vertical VHR imagery, delivered right after an event instead of waiting on crews to work the streets block by block.
If your next tasking call needs that first-pass structure sweep, it's worth asking whether vertical VHR is already in your plan.