← Latest papers
💻 computer science

RAPID: A Reproducible Multi-Agent Pipeline for Interpretable Disaster Damage Assessment from Satellite and Street-View Imagery

This paper introduces RAPID, a reproducible multi-agent pipeline that leverages zero-shot reasoning across satellite and street-view imagery to provide interpretable, fine-grained disaster damage assessments and actionable recovery reports without requiring task-specific fine-tuning.

Original authors: Yifan Yang, Wenjing Gong, Kaili Zhang, Lei Zou, Zhengzhong Tu, Hao Li, Zongrong Li, Xinyue Ye

Published 2026-06-23
📖 5 min read🧠 Deep dive

Original authors: Yifan Yang, Wenjing Gong, Kaili Zhang, Lei Zou, Zhengzhong Tu, Hao Li, Zongrong Li, Xinyue Ye

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine a team of specialized detectives working together to figure out exactly what happened after a massive storm, earthquake, or fire. Instead of relying on one super-smart detective who tries to do everything at once, this paper introduces RAPID, a "team of agents" that works together to assess disaster damage using photos taken from space (satellites) and from the ground (street views).

Here is how RAPID works, broken down into simple steps using everyday analogies:

The Problem: The "One-Size-Fits-All" Trap

Usually, computer programs used to check for disaster damage are like students who have memorized answers for a specific test. If the test changes (a different type of storm, a different city, or a new camera angle), they get confused. They also often need a teacher to manually show them thousands of examples before they can learn anything. This is too slow when a disaster just happened and we need answers now.

The Solution: The RAPID Detective Squad

RAPID is different. It doesn't need to be retrained for every new disaster. Instead, it uses four specialized "agents" (AI assistants) that pass the work down a line, like a relay race.

1. The Scout (Disaster Perception Agent)

  • What it does: This agent looks at the incoming photos and asks, "What kind of disaster is this? Is it a hurricane, a flood, or an earthquake? And do we need to clean up these blurry photos first?"
  • The Analogy: Think of this as the team leader who walks into a messy crime scene, identifies the type of crime, and decides which tools the rest of the team needs. It can tell the difference between a flood and a fire just by looking, even if it has never seen that specific flood before.

2. The Restorer (Image Restoration Agent)

  • What it does: Disaster photos are often dark, foggy, or blurry. This agent tries to sharpen them up. But here's the catch: it's careful. It tries three different ways to fix the picture and only keeps the version that actually looks clearer without inventing fake details.
  • The Analogy: Imagine a photo editor who tries three different filters to fix a blurry photo. They pick the one that makes the details pop but stops if a filter starts making the sky look purple or the trees look like they are melting. They only pass on the "cleanest" version of the truth.

3. The Inspector (Damage Recognition Agent)

  • What it does: Now that the photos are clear, this agent looks for specific damage. It counts broken windows, fallen trees, and downed power lines. It also gives a "severity score" (e.g., "mild damage" vs. "destroyed").
  • The Analogy: This is the insurance adjuster walking through the house with a clipboard. They don't just say "it's broken"; they say, "The roof has a hole, the tree is on the car, and the power is out." They can look at a satellite view and a street view at the same time to get the full picture.

4. The Reporter (Disaster Reasoning Agent)

  • What it does: This agent takes all the facts from the previous steps and writes a report. It explains why the damage happened and suggests what to do next (like "clear the debris" or "check the building's safety").
  • The Analogy: This is the press secretary or emergency coordinator. They take the inspector's notes and turn them into a clear story for the mayor or the public: "Here is what happened, here is the damage, and here are the first steps we should take."

How They Tested It

The researchers tested this team on real disasters like hurricanes, wildfires, and floods. They used a mix of "before and after" street photos and satellite images.

  • The Results: The team was very good at identifying what kind of disaster happened (about 92% accuracy).
  • The Limits: They were good at spotting damage, but sometimes they struggled to say exactly how bad the damage was on a precise scale (getting about 60% accuracy on severity). Also, while the "Reporter" agent was great at describing the facts, it sometimes struggled to come up with specific, practical solutions for how to fix things, because that requires deep local knowledge that a computer might not have.

The Bottom Line

RAPID is like a fast, reliable, and transparent early-warning system. It doesn't replace human experts or official inspectors. Instead, it acts as a powerful assistant that can quickly scan a huge area, clean up the photos, spot the obvious damage, and write a draft report for humans to review.

The paper emphasizes that this system is reproducible (you can run it again and get the same steps) and interpretable (you can see exactly which agent made which decision, so you know where the system might have made a mistake). It's designed to get emergency responders a head start when time is running out.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →