UAS Wildland Fire Collaborative seal
UAS Wildland Fire Collaborative Recognized 501(c)(3) public charity · EIN 42-2344101
Donate

What we deliver

The same map set on every fire, free to the incident.

These maps go to the incident commander, the GIS staff and the crews on the ground, and they cost the pilot, the agency and the incident nothing. A pilot flies the fire and uploads the night's infrared data. The pipeline turns it into the standard map set and sends it back to the pilot, who approves it for the live layers those teams read.

On some teams a data specialist submits and approves the set in the pilot's place.

Get in touch See the fires
A delivered topographic infrared map sheet, 11 by 17, for the first night on Fielder Mountain: graded heat sources inside a pink heat perimeter over contours.
Topographic map · Fielder Mountain, August 15, 2026

The map set

One upload, and the whole set comes back.

Everything below comes back from a single upload, each file named the way the interagency share names it.

  • A delivered aerial infrared map sheet, 11 by 17, for East Evans Creek, Division X: pink heat sources and heat areas along the red daily fire perimeter over forest.

    Aerial map

    The same standard layout over aerial photography flown before the fire, for crews who read the ground by sight. This is the Oregon Department of Forestry South Cascade District's sheet for Division X of East Evans Creek.

    The East Evans Creek case study

  • A delivered UAS infrared daily log for the Ramsey Spot Fire, July 24, 2026, with the Oregon Department of Forestry South Cascade District seal; the names, email and phone numbers are covered.

    Infrared daily log

    One page per map set, laid out like an infrared interpreter's daily log: when it flew, the aircraft and sensor, the weather, the objective, comments on the imagery and when the set was sent. This one is from the Ramsey Spot Fire on East Evans Creek, with names and phone numbers covered.

  • The Fielder Mountain Google Earth file opened in 3D: yellow, orange and purple heat sources on a forested slope inside a cyan mop up buffer, with the red perimeter along the valley.

    Google Earth KMZ

    One file that opens with a tap, so anyone on the incident can see the heat without GIS software. Here, Fielder Mountain's file in Google Earth, heat graded high, medium and low on the slope.

    The Fielder Mountain case study

Also in every set

  • Live map layers the team pulls from, including the Intterra feed, once the pilot approves the set. Any GIS can add them.
  • Interagency standard shapefiles for any GIS.
  • A file geodatabase with the full attributed feature set.

Open a real set: Fielder Mountain Share the data

In use

From the pilot's browser to a crew's phone.

The same layers reach everyone who needs them. These are real screenshots from the 2026 season, cropped to the tool.

  • The Map a fire tool in a browser: a detection threshold slider set to 109 degrees Fahrenheit, 98 hot spots on 0.06 acres, all graded medium, beside a satellite map.

    Map a fire

    A pilot with no processing software finds the heat in a browser tab and downloads it as shapefiles. Here the pilot has set the detection threshold on a Fielder Mountain flight to 109 °F: 98 hot spots, each graded against the rest of that flight.

    Field note: from photos to a shapefile

  • ArcGIS Field Maps on a phone over aerial imagery: a blue location dot a short walk from four pink diamonds marking possible heat, a dashed cyan mop up buffer and a red perimeter line.

    Field Maps

    The live layers on a phone, on the ground. Woodrat Mountain, 3 am: the blue dot is a person on foot, the pink diamonds possible heat, the dashed line a mop up buffer.

    The Woodrat Mountain case study

  • The public data viewer on a phone: hundreds of yellow, orange and purple heat sources inside a pink heat perimeter beside Interstate 5, with a dashed cyan mop up buffer.

    The data viewer

    Open to anyone, no account. Interstate 5 as it looked on the afternoon of August 3: heat graded high in yellow, medium in orange and low in purple, inside the drone's pink heat perimeter.

    The Interstate 5 case study

Whose maps they are

Each organization's seal, on its own maps.

A map belongs to the people who flew it. Every organization that flies through the system has its own map template, chosen automatically from the pilot's profile, so the sheet that reaches the fireline carries that organization's seal beside the Collaborative's. These four flew Oregon wildfires in 2026.

  • The title block of a delivered Oregon Department of Forestry sheet for the Rosenbaum fire, with the ODF seal beside the Collaborative's.
    Oregon Department of Forestry
  • The title block of a delivered South Cascade District sheet for the Rowe Creek Complex, with the district seal beside the Collaborative's.
    ODF South Cascade District
  • The title block of a delivered Hummingbird Drones sheet for the Rowe Creek Complex West zone, with the company logo beside the Collaborative's seal.
    Hummingbird Drones
  • The title block of a delivered sheet from Rogue Reconnaissance, the founder's company, for East Evans Creek Division F, with its logo beside the Collaborative's seal.
    Rogue Reconnaissance, the founder's company

Real 2026 sheets from the public archive. Every one is on its fire's case study.

Fly with the Collaborative.

If you fly infrared on wildfires, your data can reach the incident in this format too, at no cost to you or to the agency.

Get in touch See the fires