Define the monitoring area
Search a U.S. ZIP code or address and set a radius to monitor reported incidents alongside official weather-related hazard areas.
Open the incident map ↗SEVERE WEATHER. OPERATIONAL VISIBILITY.
A shared incident picture for emergency managers, public works teams, and operations coordinators. Map user-reported impacts alongside public weather alerts to monitor severe-weather events and track the incidents that need attention.
View the incident picture without signing in. Sign in to submit reports; authorized roles manage review and response.
FROM EVENT MONITORING TO INCIDENT ACCOUNTABILITY
Monitor an area of responsibility, assess reported impacts, and maintain visibility into review and response as conditions develop.
Search a U.S. ZIP code or address and set a radius to monitor reported incidents alongside official weather-related hazard areas.
Open the incident map ↗Distinguish public weather alerts from user-submitted incident reports. Read source records, timestamps, and review histories before making operational decisions.
About our sources ↗Submit an incident with a factual description and location. Authorized reviewers can assess reports, assign response teams, and track progress through resolution.
BUILT FOR INCIDENT OVERSIGHT
User submissions capture reported conditions on the ground. Public weather alerts provide hazard context. Authorized teams review incidents and record assignment progress in a shared workspace.
MONITORING & DATA COVERAGE
Flood Finder is designed for people responsible for monitoring severe-weather impacts and accounting for incidents, including emergency management, public works, and response coordination teams. The map is publicly viewable; reporting requires an account, and operational actions require authorized roles.
Public National Weather Service alerts are labeled as official hazard areas. User submissions appear as incident reports and start unverified. Review status and activity history show work recorded within Flood Finder; they do not imply independent confirmation by an outside authority.
No. Reports depend on submissions and public-provider coverage. Incidents may be missing, reports may be outdated, and feeds may be unavailable. An empty map does not establish that no incidents occurred or that an area is safe.
No. Flood Finder is not an emergency dispatch service. For immediate danger, contact local emergency services. Never enter or drive through floodwater.
ABOUT FLOOD FINDER
Flood Finder gives teams responsible for severe-weather incident oversight a shared map of user-reported impacts and public weather-related hazard areas, with clear source distinctions.
During severe-weather events, teams need to understand where impacts are being reported and which incidents remain unresolved. Flood Finder brings reports of flooding, blocked roads, utility outages, storm debris, and related needs into a map-based monitoring workflow.
Active National Weather Service warnings, watches, advisories, and relevant statements appear as shaded areas when usable boundaries are available. These areas can be broader than the actual hazard. Read the issuing agency’s instructions.
Pins represent user submissions. Reports begin as unverified; review and response activity appear in their history. An app review does not imply government endorsement or outside verification.
Users submit incident observations. Administrators review reports, set priorities, and assign response teams. Assigned team leads record progress through completion, preserving an incident history for oversight. Creating an account does not grant response or administrator privileges.
Official coverage is weather-related and U.S.-focused. Flood Finder does not detect every emergency, verify road safety, or replace emergency services. No returned reports or alerts does not establish safe conditions.
Open the monitoring map ↗ Read the guidePRIVACY & YOUR DATA
Public reports are public information. Share observations about conditions, and keep personal details out of your submissions.
The service stores your name, email address, password hash, account role, and session records. Passwords are hashed, and sign-in uses an HTTP-only session cookie. Authorized administrators can access the user directory.
Report titles, descriptions, addresses, coordinates, timestamps, statuses, and operational histories are accessible to people using the service. Avoid names, contact details, medical information, and private locations you do not want to disclose.
The browser requests map tiles from OpenStreetMap. That provider receives normal connection information such as your IP address. Server-side address searches use Photon, the U.S. Census geocoder, and Zippopotam.us; weather and hazard requests use National Weather Service services. Search text or coordinates are sent as needed, but report descriptions and account credentials are not included in those lookups.
Device location is optional and requires your permission. Signing out clears your session cookie. Account and report records remain on the service, and backups may retain records. This version does not offer self-service account deletion or password recovery.
SAFETY & RESPONSIBLE USE
Contact local emergency services. Submitting a report does not request or guarantee emergency assistance. Never drive through floodwater or enter a hazardous area to document it.
Report what you observed, describe the location accurately, and avoid speculation. Do not submit harassment, private personal information, deliberately false reports, or content you do not have permission to share.
Community reports may be inaccurate or outdated. Official alert boundaries are approximate, and provider outages or coverage gaps may hide relevant hazards. Follow local authorities and the instructions of the issuing agency.
Routing tools do not establish that a road is open or flood-safe. Follow closures and verified official navigation. Do not rely on Flood Finder as your only source of safety information.
How to use Flood Finder ↗Local disruptions. Clearly sourced.
Official source: National Weather Service. Boundaries may cover a larger area than the actual hazard. No returned reports or alerts does not establish safe conditions. Map tiles © OpenStreetMap contributors.
Verify reports, prioritize needs, assign crews and track dispatch progress.
Assign responder access to crew leads. Only administrators can grant admin privileges.
Assigned team leads can acknowledge, travel to, and complete dispatches.
Define a monitoring area, review public hazard data, and record reported impacts with clear sources and status histories.
Enter a five-digit ZIP (ZIP+4 also works) or a full U.S. street address and select Locate, then choose a radius. Or pan the map and select Search this map. The dashed circle marks your search area. Panning alone does not change the search.
Shaded regions come from National Weather Service warnings, watches, advisories, and statements. Click one for issuer text, timing, and instructions. A dashed boundary represents an affected zone, which may be broader than the actual hazard. A shape is not a claim that every street inside it is damaged.
When the provider has no usable boundary, a relevant notice stays in the list without an invented pin. No returned alert does not establish safety.
Community pins describe flooding, access issues, outages, debris, shelter needs, and safety concerns people have submitted. New reports are unverified. Click a pin or list item to read the user submission, its original record link, and review history. No external citation is attached to community submissions. Safety guidance links offer general advice, not proof of that event.
This app does not automatically detect every emergency or turn a temperature/rain reading into a disaster report.
Switch between All sources, Official, and Community. The official-type filter applies to official hazards. Community type buttons can be combined; Community status, priority, sorting, and Only my reports apply to submissions. Text search can match either source. The reset arrow clears filters, while keeping your area and radius.
Sign in and select Report a situation. Choose the type and severity, write a factual title and description, and enter a full street address. Publish resolves the address before submitting—no map click is required. If several addresses match, choose the right one.
The address goes to the U.S. Census geocoder; your account and report description do not. Report content and locations are public. Avoid personal names, phone numbers, and medical details.
For an addressless situation or a correction, expand the optional map section. Place/drag a marker, type coordinates, or use your device location with permission. Editing the address clears old coordinates. After submission, the search centers on your report.
Administrators use Command center to review community incidents, manage roles, create teams, select leads, and dispatch work. Team leads use My assignments: Acknowledged, En route, On scene, then Completed. Rejected incidents cancel active work. Reopening with the same team creates a fresh assignment.
Official alerts are read-only source records. Community administration does not edit them.
Reports update live and periodically. Official hazards refresh about every two minutes while visible. Partial coverage means some areas could not load; Unavailable means the feed failed or coverage is unsupported. Refresh can reuse a recent cached response.
NWS coverage is weather-related and point/state scoped; nearby cross-state alerts can be missed. It does not automatically provide every closure, outage, fire, or other local emergency.
For immediate danger, contact local emergency services. Community reports, official areas, and estimated routes are not proof a road is safe. Never drive through floodwater.