CEEES - StEER Virtual Reconnaissance: Verifying Post-Disaster Imagery

The NSF NHERI Structural Extreme Events Reconnaissance (StEER) Network produces rapid, publicly archived engineering assessments of how buildings and infrastructure perform during natural hazard events, including earthquakes, hurricanes, tornadoes, and tsunamis. The goal of this research is to capture perishable damage data quickly after a disaster and translate it into reliable evidence that informs research, design codes and practice, and recovery decisions. These reports are published on DesignSafe, the NSF-funded cyberinfrastructure for natural hazards research.

Many StEER reports begin with virtual reconnaissance, in which a team assembles and analyzes images and videos shared by news outlets, social media users, and field contributors in the days after an event. Before this media can serve as engineering evidence, its origin, location, date, and proper attribution must be verified. Techniques include source-chain tracing, reverse image search, EXIF metadata analysis, geolocation using maps and satellite imagery, and cross-source corroboration. Python automation scripts are used to triage large media repositories and flag gaps or inconsistencies.

Students join a distributed virtual assessment team of faculty, researchers, and international partners. After initial training, they verify the provenance of media assigned to them, document their findings to the network's citation and data-integrity standards, and flag unresolved items for the report authors. Students work independently on their assignments, meet regularly with the team, and see their work contribute directly to published reconnaissance reports.

Name of research group, project, or lab
StEER Network
Why join this research group or lab?

Few research experiences are as fast-moving or as consequential as disaster reconnaissance. When a major earthquake, hurricane, tornado, or tsunami strikes, the StEER Network mobilizes within days, and students work alongside faculty, researchers, and international partners as an event’s impacts are still being understood. Each event brings new places, building types, and questions, so no two projects are the same.

This work matters because it yields systematic evidence on how the built environment performs under natural hazards. Students learn how the engineering community “learns from disasters,” and they contribute to research that has the potential to change policies and practices and reduce the toll of disasters on communities worldwide. It is very rare for students to have access to data on how real-world, as-built structures perform. Most engineering coursework relies on idealized models, while this work shows what actually happens when those structures are tested by nature.

StEER is part of a broader research portfolio at Notre Dame on hazard resilience. Related efforts include hurricane risk simulation through the NSF NHERI SimCenter, remote sensing and AI-based frameworks for post-disaster damage assessment, and interdisciplinary research on how to translate resilience measures into policy and stakeholder action. Students who join this group gain exposure to that wider ecosystem and the many career paths it opens across engineering, data science, public policy, and global development.

Since our publication is too large to upload, you can read the paper online: https://www.frontiersin.org/journals/built-environment/articles/10.3389/fbuil.2021.636197/full

Logistics Information:
Project categories
Civil & Environmental Engineering & Earth Sciences
Student ranks applicable
Sophomore
Junior
Senior
Graduate Student
Student qualifications

No specialized background is required, and students from all majors are welcome. Successful participants are detail-oriented, persistent, and comfortable working independently on assigned tasks while meeting team deadlines. Clear written communication is essential, since findings must be documented precisely enough for report authors to act on them. Students should be able to follow established procedures carefully and to flag uncertainties rather than guess.

Helpful but not required are coursework in civil or structural engineering, GIS, or computer science; basic familiarity with Python; and reading knowledge of Spanish, which can help when working with media from Latin American events. All verification techniques and tools are taught during onboarding.

There are no physical requirements. All work is computer-based and can be completed remotely or on campus. Students should be aware that disaster imagery can sometimes show severe damage or human loss. We discuss this during onboarding, and students can raise concerns with the team at any time.

Hours per week
1 credit / 3-6 hours
2 credits / 6-12 hours
Compensation
Research for Credit
Paid - General
Number of openings
4
Techniques learned
  • Media provenance verification: tracing images and videos back to their original source through reposts and shares
  • Reverse image search: using multiple search engines to find earlier or original instances of an image
  • Metadata analysis: extracting and interpreting EXIF and other embedded data to establish when, where, and how media was captured
  • Geolocation: confirming where an image was taken by matching visible features to maps, street-level imagery, and satellite imagery
  • Cross-source corroboration: checking media against news reports, official sources, and other images of the same site
  • Python scripting for data triage: running and adapting automation scripts to process large media repositories and flag gaps
  • Structural damage recognition: identifying common failure modes for different building types and hazards
  • Technical documentation: recording findings to strict citation, attribution, and data-integrity standards for published reports
  • Virtual team collaboration: coordinating with a distributed team of faculty, researchers, and international partners under tight timelines
Project start
Fall 2026 Semester
This project will use an Expectations and Structure agreement.
Expectations and Structure

 1. Purpose and Lab Overview

The Hazards Hub focuses on understanding and reducing vulnerabilities within the built environment while improving decision-making systems and promoting policies and actions that foster resilient and sustainable communities. The Hub focuses on: post-disaster reconnaissance and field assessment, natural hazard risk assessment, climate adaptation and resilience planning, housing resilience and convergence research integrating engineering, policy, and social systems. This document sets expectations for undergraduate researchers so that everyone — you and your mentors — has a shared understanding of what a successful experience looks like.

2. Time Commitment

  • Expected commitment: 5 hours per week per credit hour, at times that work best for you.
  • Time commitments may flex around travel, breaks and midterms/last week of classes.
  • If for any reason you cannot meet this expectation in a given week, please let me know as soon as you realize your workload or commitments are unusually high that week. 

3. Communication

  • Primary channel: Slack (my inbox is busy so this is the way to go). Let’s all commit to respond within 24 hours on business days (M-F).
  • I keep my calendar up to date on Google so use my scheduler to set up 1:1 meetings with me: Book Appointment or directly send me a calendar invite at a free time in my Google Calendar.
  • If you're stuck on a task for more than 2 hours, reach out rather than spinning your wheels — this is expected, not a sign of failure.

4. Meetings and Progress Reporting

  • Group: I know schedules are difficult, but we will poll the group to find a day and time to meet weekly to share updates, troubleshoot and discuss project next steps, attendance is expected unless excused in advance.
  • Keep a running research log (electronic or notebook) documenting what you did, what you found, and open questions — this protects your work and makes reporting out in group meetings much easier.
  • Come to check-ins with a short, written update: what you completed, what's blocking you, what you plan to do next.
  • You will be expected to author a summary of your efforts this semester using a template I provide; this is a minimum expectation of the College of Engineering and documentation of your credit earned. Your digital notebook with weekly updates will be invaluable in crafting this.

5. Research Conduct and Data Practices

  • Back up your work regularly: Always work on Hazards Hub's Shared Google Drive. This ensures you have regular backup and recovery options; This also makes it easier for me to review files you send me without awkward delays due to permissions. 
  • Treat data from disaster-affected communities and partner organizations as sensitive: no public sharing or posting without my explicit sign-off. 
  • Uphold academic integrity in all analysis, writing, and use of AI tools — when in doubt about what's appropriate, ask. I do not prohibit AI; I regulate its ethical and constructive use and disclose the use of it in my work. For example, I used AI to help me brainstorm what I should cover here (and it thought of some things I did not). But I was the one to prompt it, give it examples and then refine what it offered (and below I am disclosed that I used it). 

6. Training and Skill Development

  • You'll receive onboarding on relevant software/methods and data storage environments before working independently.
  • It's normal to feel behind at first — a learning curve is expected and budgeted into your timeline.
  • Take advantage of online resources: a quick search or even AI prompt can turn up rich tutorials and tips for many of the platforms we are using. The hosts of these platforms also have their own training resources. Take advantage of them. A quick query can save a lot of time.

7. Independence and Decision-Making

  • Early on, check in before making decisions that might affect data integrity. Use our group Slack to bounce ideas or DM me directly. 
  • I believe in structuring projects so you can work independently; I use tools such as standard operating procedures (SOPs) to make steps explicit and highly repeatable. 
  • When uncertain whether something deviates from the SOP, default to asking.

8. Professional Conduct

  • Treat all group members and collaborators with respect and professionalism.
  • Use data, collaboration platforms and software responsibly and only for lab-related work.

9. Recognition and Advancement

  • Authorship on papers/reports follows standard contribution norms; we'll discuss expectations for your specific project early on.
  • Opportunities to present at conferences or other meetings are based on the maturity and quality of your contribution.
  • Letters of recommendation are available after [one semester / a meaningful body of work] of engaged participation.

10. What You Can Expect from Me

  • Regular, constructive feedback on your work — not just at the end, but throughout.
  • Guidance on career paths, further research, or graduate school if you're interested.
  • Reasonably timely responses to your questions and check-in requests.
  • Advocacy for your growth: connecting you to opportunities, co-authorship where earned, and honest assessments of your progress.

11. If Things Aren't Working

Research fit isn't always immediately clear, and that's fine. If the arrangement isn't working, we'll aim for a respectful transition — in this case it should be as soon as it is clear your time or interests are no longer aligned with your research project; however, given the nature for for-credit opportunities, this must be decided no later than the drop date. 

Contact Information:
Mentor
tkijewsk@nd.edu
Professor
Name of project director or principal investigator
Tracy Kijewski-Correa
Email address of project director or principal investigator
tkijewsk@nd.edu
4 sp. | 0 appl.
Hours per week
1 credit / 3-6 hours (+1)
1 credit / 3-6 hours2 credits / 6-12 hours
Project categories
Civil & Environmental Engineering & Earth Sciences