Burned area
satellite only1,282ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 19 Feb 2017 – 19 Feb 2017
+− cross-check
No official record is matched to this page to compare it with.
CN · China ·
Mile City fire, 19 February 2017 弥勒市 · Mile City
Out · last measured on 19 Feb 2017
The fire started on 19 February 2017 in Mile City, China, and satellites saw it burning for 1 day. Copernicus’s global GWIS system rebuilt a burnt perimeter of 1,282 hectares from heat detections, spread across a single municipality.
It is the 114th largest in Yunnan Province since 2016 (of 196 with a page). Number 152 in China in 2017, of 243.
Use this data
Fire page data · version 2026-10-24matches the official recordwith caveatssatellite onlymodel
When copying, the sentence is
Tick the figures you want: they make up the lede and the CSV.
Duration by satellite
satellite only1day
19 Feb 2017 to 19 Feb 2017: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 19 Feb 2017 – 19 Feb 2017
+− cross-check
Satellites pass a few times a day and cloud or smoke can hide the fire: a lack of detections is not an official extinction. Each country’s emergency service declares a fire contained or out.
Start
satellite only19 Feb 2017
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 19 Feb 2017
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Danger at the start
model11.2FWI · moderate
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 8.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 19 Feb 2017, local noon
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
This is an index computed from weather model data, not a measurement of the fire nor an official warning. Danger warnings are issued by each country’s authority. Emergency number and official warnings
Weather during the fire
model23.6°C · 29% RH
High of 23.6 °C and minimum humidity of 29% on 19 February 2017; gusts of 53 km/h on 19 February 2017.
- Source
- weather model at the fire’s grid cell
- Date
- 19 Feb 2017 – 19 Feb 2017
- Model
- ERA5 0,25° (ECMWF · Copernicus C3S) · Open-Meteo.com
+− cross-check
These are model values for a cell of about 25 km, not from a weather station: they may differ from what was measured on the ground.
This page’s change log has been kept since 24 October 2026: every night what it publishes is compared and the difference is logged. Anything earlier is reconstructed from each source’s date and marked as reconstructed.
Show
-
· reconstructed weatherWeather and FWI computed from the ERA5 reanalysis
-
· reconstructed GHSLPopulation and built-up area computed
What was saved on 24 October 2026
Every night a snapshot of what the page shows is saved. If anything changes, it appears in the list as a log entry.
- Area
- 1,282 ha
- Dates
- 19 Feb 2017 – 19 Feb 2017
- Name
- Mile City
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/mile-city-2017-02-3?v=2026-10-24A version keeps the area, dates, name and official record; the area as it was logged (changes under 2% are not logged). The map, hotspots and weather always show today’s data.
Citation
A lede of about 60 words figures only, no adjectives
CSV for this fire mile-city-2017-02-3.csv · daily, no individual hotspots
| fecha | focos_viirs | frp_mw | tmax_c | tmin_c | hr_min_pct | viento_max_kmh | racha_max_kmh | precip_mm | fwi | clase_fwi | dentro_del_incendio |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2017-02-19 | 0 | 0 | 23.6 | 8.5 | 29 | 21.4 | 53.3 | 0 | 11.2 | bajo | 1 |
| 2017-02-20 | 0 | 0 | 22.5 | 8.4 | 31 | 25.8 | 63.7 | 0 | 17.2 | moderado | 0 |
| 2017-02-21 | 0 | 0 | 22.9 | 12.5 | 26 | 25.2 | 70.2 | 0 | 19.7 | moderado | 0 |
| 2017-02-22 | 0 | 0 | 24.8 | 11 | 23 | 25.4 | 65.2 | 0 | 19.1 | moderado | 0 |
| 2017-02-23 | 0 | 0 | 23.1 | 10.1 | 27 | 25.9 | 65.9 | 0.1 | 11.5 | moderado | 0 |
| 2017-02-24 | 0 | 0 | 16.1 | 5.2 | 55 | 12.7 | 34.6 | 1 | 3.1 | muy_bajo | 0 |
It is generated in your browser from this page’s data: one file per fire, aggregated by day and without individual hotspots.
Live widget for your story
It updates itself while the fire is still active and links to this page. Free, with the attribution shown at the bottom.
Sources for this page: GWIS (Copernicus), NASA FIRMS (VIIRS), ERA5 (ECMWF/Copernicus C3S) · Open-Meteo.com (CC BY 4.0), GHSL (JRC). Open-Meteo.com · How we build fire pages: methodology
We have the GWIS perimeter for this fire, but the VIIRS sensors did not capture it in enough detail: no day-by-day evolution, but the split by municipality is there.
- Burnt area
- 1,282ha
- GWIS perimeter (Copernicus)
- Duration
- 1day
- 19 Feb 2017 – 19 Feb 2017
- Municipalities hit
- 1
- counties
- Started on
- 19 Feb
- 2017
- Danger at start
- 11
- Moderate · FWI index
Where it burned
The weather it burned in
24°high
53km/h · peak gust
29%lowest humidity
It had gone 8 days without rain (1 mm or more) when it started. Rain came after the fire: 1.0 mm on 24 Feb.
This area had burned before
No earlier perimeters overlap this fire since 2016, when the satellite record begins.
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.0).
Beijing (Dongcheng and Xicheng) boundary: geoBoundaries · Lee Beryman, OpenStreetMap · © OpenStreetMap contributors (ODbL 1.0).
Paris boundary: geoBoundaries · Institut national de l'information géographique et forestière (IGN-F) (Etalab Open License 2.0).
Madrid boundary: geoBoundaries · Open Data ESRI, IGN Central Registry of Cartography Area (CC BY 4.0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
1,286 ha0.3 %
Burnt area inside each municipality, from crossing the GWIS perimeter with administrative boundaries. The distance runs from the point marking the centre of each area to the nearest fire: staying a kilometre away does not mean it reached the houses.
People and buildings inside the perimeter
GHSL 2015Built-up area0.15 ha
Residents< 20
Inside the perimeter there were about 0.15 hectares of built-up land and almost nobody lived there (GHSL 2015, satellite-based estimate).
This is an estimate on 100 m cells, made from satellite imagery and census data: it does not mean that homes burned or that anyone was harmed. The perimeter also contains land that never burned.
Source: Global Human Settlement Layer (GHS-BUILT-S and GHS-POP R2023A), European Commission Joint Research Centre (JRC), © European Union, CC BY 4.0. Sum inside the perimeter computed by WorldFires. human-settlement.emergency.copernicus.eu
The weather day by day
ECMWF ERA5 reanalysis at the fire location, the standard reference for past weather, and the Canadian Fire Weather Index (the same system Copernicus uses), computed by WorldFires from that data. Days after the fire run until the first rain.
Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
Started with Strong wind: 24 % of the area in China
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 19 Feb | 23.6 °C | 29 % | 53 km/h | 0.0 mm | Low 11 |
| 20 Feb after | 22.5 °C | 31 % | 64 km/h | 0.0 mm | Moderate 17 |
| 21 Feb after | 22.9 °C | 26 % | 70 km/h | 0.0 mm | Moderate 20 |
| 22 Feb after | 24.8 °C | 23 % | 65 km/h | 0.0 mm | Moderate 19 |
| 23 Feb after | 23.1 °C | 27 % | 66 km/h | 0.1 mm | Moderate 12 |
| 24 Feb after | 16.1 °C | 55 % | 35 km/h | 1.0 mm | Very low 3 |
Its twins: fires that started in the same weather
It started with an FWI of 11.2, a minimum humidity of 29% and 8 days without rain. Fires in the area that started in weather like this since 2016: 21.
FWI at the start
11.2
Minimum humidity
29 %
Days without rain
8
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Mile City fire, 19 February 2017
1,282 ha
1 day
FWI 11.2
Min. humidity 29 %
Xinping Yi and Dai Autonomous County fire, February 2019
1,617 ha
3 days
FWI 10.4
Min. humidity 31 %
133 km away, in 2019
First rain (1 mm or more) after it ended: 2.5 mm on 17 Feb.
Xinping Yi and Dai Autonomous County fire, February 2019
1,017 ha
2 days
FWI 10.5
Min. humidity 31 %
146 km away, in 2019
First rain (1 mm or more) after it ended: 2.5 mm on 17 Feb.
Shiping County fire, February 2024
1,094 ha
5 days
FWI 10.1
Min. humidity 26 %
96 km away, in 2024
First rain (1 mm or more) after it ended: 1.0 mm on 1 Mar.
Shiping County fire, November 2022
1,137 ha
1 day
FWI 13.2
Min. humidity 30 %
111 km away, in 2022
First rain (1 mm or more) after it ended: 12.8 mm on 2 Dec.
Yanshan County fire, March 2021
1,723 ha
4 days
FWI 10.2
Min. humidity 32 %
148 km away, in 2021
First rain (1 mm or more) after it ended: 39.2 mm on 4 Apr.
What happened to them
- 3 days
- median duration
- 1,617 ha
- median area
- 95 %
- went past 1,000 ha
- 2.5 mm
- rain at the end (median; 21 of 21 had it)
It burned an area similar to its twins (1,282 ha against a median of 1,617 ha) and lasted 1 day, against 3 days.
All of them had rain in the ten days after the end: the first rainy day brought a median of 2.5 mm.
This is a bank of analogues: it shows what usually happens, not what will happen. With fewer than 15 twins we give no figures. How we calculate it
How it ended
1.0 mmfirst rain
24 Feb5 days after it ended
53km/h · max. gust
It was considered over on 19 Feb, and on 24 Feb 1.0 mm fell. We do not know whether the rain or the firefighters put it out. Twins with rain when they ended: 21 of 21, with a median of 2.5 mm.
Weather on this page: Open-Meteo.com (CC BY 4.0) · Copernicus Climate Change Service (ERA5)
How a twin is chosen
- Same area: fires that have already ended, less than 250 km from this one, since 2016.
- Same start: we compare the FWI on the first day, the minimum humidity that day and the run of days without rain before it. The slider sets how much they may differ.
- Only pages with final weather data (ERA5 reanalysis) calculated in the same way as this fire’s; agricultural and grass burns and pages with data under review are left out.
- Fires burning at the same time as this one (a week before or after) are left out: they share the same spell of weather and do not count as a precedent.
- They are sorted by similarity, and the outlines of the first five are drawn.
Before and after, from space
Drag the line to compare the same ground before the fire and after it.
↔
Before · 12 Feb 2017
After · 26 Feb 2017
Sentinel-2 did not pass over on that day. Try another date, or use false colour, which is daily.
If the day is cloudy, change the date: each satellite passes once a day. In false colour the burnt ground looks brown or red.
Other fires nearby
Frequently asked questions
- How long did the Mile City fire last?
- GWIS (Copernicus) dates it between 19 February 2017 and 19 February 2017: 1 day between the first and last heat detection of the perimeter.
- How much area did it burn?
- The perimeter GWIS (Copernicus) rebuilt from heat detections is 1,282 hectares (12.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Mile City (1,286 ha, 0.3 %).
- What was the weather like?
- During the fire the temperature reached 23.6 °C, humidity dropped to 29 % and gusts hit 53 km/h. The fire danger index (FWI) reached 11, class Moderate.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of China (geoBoundaries). It is not an official report.
- How did the fires that started in similar weather in this area end?
- Fires less than 250 km away that started since 2016 with a similar FWI, humidity and dry spell: 21. Their median duration was 3 days and their median area 1,617 ha; 95 % went past 1,000 ha. All of them had rain in the ten days after the end: the first rainy day brought a median of 2.5 mm.
Where to verify it
A satellite detection is not an official report. Final figures and the fire’s status are published by each country’s emergency service.
Emergency number: 119 · Emergency number and official warnings
Satellite cross-check
History of this page Changes in area, dates, name, official record or merged pages, compared every night since 24 October 2026.
No changes since 24 October 2026.
RSS Changes to this page With cross-checks and a citable version
Does something look wrong on this page?
This page is built from satellite data and official records, and it sometimes gets things wrong: the wrong dates, the wrong town, two fires merged into one, or something that was not a wildfire at all. If you know this fire first-hand (you live nearby, saw it, fought it or reported on it), tell us what really happened and we will check it.
Report an error
How we know this
- Perimeter: GWIS (Copernicus), rebuilt from heat detections rather than mapped on imagery.
- Dates from the perimeter: the VIIRS detections inside it did not change them. No Suomi-NPP VIIRS detections on those dates.
- We have not matched this page with any official record.
- Weather: Copernicus ERA5 reanalysis at the fire location, in cells of about 25 km.
- Built-up area and population come from the JRC Global Human Settlement Layer (epoch 2015, 100 m cells), summed inside the perimeter: an estimate of what was there, not a damage count.
Where this data comes from
The perimeter comes from the Copernicus Global Wildfire Information System (GWIS), which rebuilds it from MODIS and VIIRS heat detections and publishes it under CC BY 4.0. It is not measured on imagery as in Europe, so it is an estimate. Heat detections come from the VIIRS sensors aboard Suomi-NPP and NOAA-20, distributed by NASA FIRMS at 375 m resolution. Municipal boundaries come from geoBoundaries ADM3 (Open Data Commons Open Database License 1.0). The area per municipality is computed by WorldFires by crossing the perimeter with those boundaries, so it may differ from each country’s official figure.