← All mission packages
About these mission packages
A short guide to the wildfire packages on this server.
Life safety: Use Genasys, the county sheriff, and ODF for evacuation decisions.
These packages are situational awareness for ATAK and TAK. They can lag live conditions.
What is a mission package?
A mission package is a public download for one wildfire. It collects the perimeter, the origin, evacuation polygons, satellite hotspots, and official incident maps into files ATAK can import. Each fire has its own page under Mission packages.
The list covers major wildfires within about 60 miles of Grants Pass, Oregon. A fire is included when it is at least 100 acres, or when it is a Type 1, 2, or 3 incident of at least 10 acres. Prescribed fires are not included.
What is in each package?
Every fire page has the same kinds of files:
- ATAK priority load. A small zip of KMZ layers: the WFIGS fire perimeter, the incident origin, Oregon OEM evacuation polygons, NASA FIRMS hotspots from the last 24 hours, and the latest infrared KMZ when NIFC has published one.
- Official NIFC maps. A zip of the incident’s ops maps, briefing maps, incident action plans, and infrared products from ftp.wildfire.gov.
- Full package. The data tree plus those official maps.
- Browse. The same layers as KML, GeoJSON, and CSV, plus the official map folders and the latest briefing PDFs.
A layer can be empty. That means the source feed had nothing for that fire at the last update, not that the file failed.
How do I use one?
- Open the fire’s page and download ATAK Priority load if you want the map layers on a phone or tablet.
- In ATAK, open Import Manager and pick the zip, or pick a single KMZ from the priority list on the page.
- Download Official NIFC maps or open the briefing PDFs when you want the incident’s own ops, brief, and IAP maps.
- Use CloudTAK if you want the server map in a browser.
- Check Genasys Protect, the sheriff, and ODF before you act on an evacuation line drawn in the package.
How often are they updated?
Twice a day, at 6:30 and 18:30 Pacific. Each run refreshes acres, containment, the perimeter, the origin, evacuation polygons, and hotspots.
New official maps are downloaded while a fire is still open, when a fire is new, and the first time a fire’s map folder is collected. After a fire is 100% contained and those maps are already saved, later runs keep the live layers current and do not download the whole map folder again.
What happens at the end of the year?
On the first update after January 1, the finished year is compressed into one zip and published for download:
/missions/archives/YYYY-mission-packages.zip
That zip is listed on the mission packages page under Yearly archives. It is built once. The individual fire pages stay on the site, and their own downloads stay available.
A new year starts when NIFC publishes the next Oregon incident folder. Fires from that year are added here. The previous year stays listed, with its pages and its zip.
Where does the data come from?
- NIFC WFIGS, for the perimeter, origin, size, and containment
- Oregon OEM, for evacuation polygons
- NASA FIRMS VIIRS NOAA-20, for hotspots in the last 24 hours
- NIFC incident maps on ftp.wildfire.gov, for ops, briefing, IAP, and infrared products
← All mission packages