Burned area
satellite only4,879ha
Perimeter published by GWIS (Copernicus).
- Source
- GWIS (Copernicus)
- Date
- 19 Feb 2020 – 23 Feb 2020
+− cross-check
No official record is matched to this page to compare it with.
ET · Ethiopia · –
Agalometi fire, February 2020 Agalometi
Out · last detection 23 Feb 2020, 22:57 UTC
The fire started on 19 February 2020 in Agalometi, Ethiopia, and satellites saw it burning for 5 days. Copernicus’s global GWIS system rebuilt a burnt perimeter of 4,879 hectares from heat detections, spread across a single municipality.
It is the 121th largest in Beneshangul Gumu since 2016 (of 635 with a page). Number 37 in Ethiopia in 2020, of 177.
Use this data
Compare with…
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 only5days
19 Feb 2020 to 23 Feb 2020: first and last day with fire on the page.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- last detection: 23 Feb 2020, 22:57 UTC
+− 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 2020
First day with fire seen by the satellites or the perimeter.
- Source
- GWIS (Copernicus) · NASA FIRMS · VIIRS
- Date
- 19 Feb 2020
+− cross-check
No official record is matched to this page, so the alert time and the cause are not known here.
Hotspots
satellite only154
VIIRS detections at 375 m. Most intense hotspot: 185 MW.
- Source
- NASA FIRMS · VIIRS (Suomi NPP)
- Date
- 19 Feb 2020 – 23 Feb 2020
+− cross-check
There is no official record to compare with. Each hotspot is a pixel detected in one satellite pass, not a separate fire.
The worst day
satellite only1,004MW
Total radiative power on 22 February 2020; hotspots that day: 36.
- Source
- NASA FIRMS · VIIRS (FRP)
- Date
- 22 Feb 2020
+− cross-check
Fire radiative power (FRP) measures the energy the fire gives off when the satellite passes. Added up by day, it compares intensity, not area.
Danger at the start
model45.1FWI · very high
Fire Weather Index (Canadian system) computed by WorldFires for the day the fire started. Consecutive days without rain before: 60.
- Source
- WorldFires calculation (Canadian FWI system)
- Date
- 19 Feb 2020, 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
model34.4°C · 10% RH
High of 34.4 °C and minimum humidity of 10% on 19 February 2020; gusts of 31 km/h on 21 February 2020.
- Source
- weather model at the fire’s grid cell
- Date
- 19 Feb 2020 – 23 Feb 2020
- 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.
Living inside
model≈ 150people
Estimated residents inside the perimeter and 0.12 ha of built-up area (100 m grid, epoch 2020).
- Source
- GHSL R2023A · JRC
- Date
- calculated on 24 October 2026
+− cross-check
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.
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
- 4,879 ha
- Dates
- 19 Feb 2020 – 23 Feb 2020
- Name
- Agalometi
- Official record
- —
Versioned permanent link
https://worldfires.org/en/fire/agalometi-2020-02?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 agalometi-2020-02.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 |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 2020-02-19 | 14 | 74 | 34.4 | 20.8 | 10 | 10.3 | 28.4 | 0 | 45.1 | muy_alto | 1 |
| 2020-02-20 | 56 | 160 | 34.3 | 17.8 | 10 | 8.3 | 27 | 0 | 46.5 | muy_alto | 1 |
| 2020-02-21 | 43 | 217 | 33.9 | 17.1 | 13 | 10.6 | 31 | 0 | 46.2 | muy_alto | 1 |
| 2020-02-22 | 36 | 1,004 | 34.2 | 18.9 | 14 | 7.3 | 22.7 | 0 | 45.8 | muy_alto | 1 |
| 2020-02-23 | 5 | 46 | 34.1 | 20.5 | 12 | 7.1 | 24.5 | 0 | 48.1 | muy_alto | 1 |
| 2020-02-24 | 0 | 0 | 34.5 | 18.8 | 11 | 11.5 | 31.7 | 0 | 46.1 | muy_alto | 0 |
| 2020-02-25 | 0 | 0 | 30.4 | 17.4 | 15 | 11.8 | 31 | 0 | 48.9 | muy_alto | 0 |
| 2020-02-26 | 0 | 0 | 33.4 | 18.8 | 18 | 6.4 | 22 | 0 | 46.2 | muy_alto | 0 |
| 2020-02-27 | 0 | 0 | 34.8 | 20.1 | 16 | 9.5 | 29.2 | 0 | 45.6 | muy_alto | 0 |
| 2020-02-28 | 0 | 0 | 34.2 | 19.2 | 18 | 11.7 | 34.6 | 0 | 47.2 | muy_alto | 0 |
| 2020-02-29 | 0 | 0 | 33.5 | 19.5 | 12 | 10.9 | 31.3 | 0 | 49.8 | muy_alto | 0 |
| 2020-03-01 | 0 | 0 | 33.8 | 19.2 | 8 | 12.3 | 34.2 | 0 | 52.9 | extremo | 0 |
| 2020-03-02 | 0 | 0 | 34 | 19.7 | 13 | 10.7 | 31.7 | 0 | 52 | extremo | 0 |
| 2020-03-03 | 0 | 0 | 34.8 | 19.4 | 11 | 13.2 | 34.2 | 0 | 50.2 | extremo | 0 |
| 2020-03-04 | 0 | 0 | 34.1 | 20 | 8 | 13 | 34.2 | 0 | 54.6 | extremo | 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
- Burnt area
- 4,879ha
- GWIS perimeter (Copernicus)
- Duration
- 5days
- 19 Feb 2020 – 23 Feb 2020
- Municipalities hit
- 1
- districts
- Started on
- 19 Feb
- 2020
- Heat detections
- 154
- in a single hotspot: 185 MW
- Danger at start
- 45
- Very high · FWI index
- Average daily power
- 300MW
- detected power per day, on average
Where it burned
HOTSPOTS BY DAY
19 Feb23 Feb
23 Feb 2020
How it evolved, day by day
19 Feb
20 Feb
21 Feb
22 Feb
23 Feb
Fire radiative power detected each day, in megawatts, and number of hotspots. The magenta bar marks the peak day.
The weather it burned in
34°high
31km/h · peak gust
10%lowest humidity
It had gone more than two months without rain (1 mm or more) when it started.
This area had burned before
91% of the perimeter overlaps earlier fires recorded since 2016: 3,814 ha in 2016, 2,596 ha in 2017, 18 ha in 2018, 1,977 ha in 2019. Part of it burned more than once, so the yearly figures add up to more than the 4,434 ha that had burned before.
- 3,790 ha Agalometi fire, January 2016 13,615 ha in total; the hectares shown are those it shares with this fire
- 1,972 ha Yaso fire, January 2019 12,814 ha in total; the hectares shown are those it shares with this fire
- 1,594 ha Agalometi fire, January 2017 9,791 ha in total; the hectares shown are those it shares with this fire
How big is it?
London boundary: geoBoundaries · Office for National Statistics (Open Government Licence v3.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).
Berlin boundary: geoBoundaries · Federal Agency for Cartography and Geodesy (dl-de/by-2-0).
This compares size, not location: both shapes are at the same scale, north up, centred on each other.
What happened to each town
-
Agalometi where it started4,909 ha reached on 19 Feb2.8 %
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 2020Built-up area0.12 ha
Residents≈ 150
Inside the perimeter there were about 0.12 hectares of built-up land and about 150 residents (GHSL 2020, 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 Very dry air: 26 % of the area in Ethiopia 60 days without rain: 37 % of the area in Ethiopia
| Day | High | Min. humidity | Peak gust | Rain | Danger (FWI) |
|---|---|---|---|---|---|
| 19 Feb | 34.4 °C | 10 % | 28 km/h | 0.0 mm | Very high 45 |
| 20 Feb | 34.3 °C | 10 % | 27 km/h | 0.0 mm | Very high 46 |
| 21 Feb | 33.9 °C | 13 % | 31 km/h | 0.0 mm | Very high 46 |
| 22 Feb | 34.2 °C | 14 % | 23 km/h | 0.0 mm | Very high 46 |
| 23 Feb | 34.1 °C | 12 % | 24 km/h | 0.0 mm | Very high 48 |
| 24 Feb after | 34.5 °C | 11 % | 32 km/h | 0.0 mm | Very high 46 |
| 25 Feb after | 30.4 °C | 15 % | 31 km/h | 0.0 mm | Very high 49 |
| 26 Feb after | 33.4 °C | 18 % | 22 km/h | 0.0 mm | Very high 46 |
| 27 Feb after | 34.8 °C | 16 % | 29 km/h | 0.0 mm | Very high 46 |
| 28 Feb after | 34.2 °C | 18 % | 35 km/h | 0.0 mm | Very high 47 |
| 29 Feb after | 33.5 °C | 12 % | 31 km/h | 0.0 mm | Very high 50 |
| 1 Mar after | 33.8 °C | 8 % | 34 km/h | 0.0 mm | Extreme 53 |
| 2 Mar after | 34.0 °C | 13 % | 32 km/h | 0.0 mm | Extreme 52 |
| 3 Mar after | 34.8 °C | 11 % | 34 km/h | 0.0 mm | Extreme 50 |
| 4 Mar after | 34.1 °C | 8 % | 34 km/h | 0.0 mm | Extreme 55 |
Its twins: fires that started in the same weather
It started with an FWI of 45.1, a minimum humidity of 10% and more than two months without rain. Fires in the area that started in weather like this since 2016: 23.
FWI at the start
45.1
Minimum humidity
10 %
Days without rain
60+
this fire
chosen twins
rest of the area
Almost identicalSimilar
Outlines of the closest twins
This fire · Agalometi fire, February 2020
4,879 ha
5 days
FWI 45.1
Min. humidity 10 %
Bio Jiganifado fire, February 2019
2,288 ha
7 days
FWI 46.1
Min. humidity 10 %
44 km away, in 2019
First rain (1 mm or more) after it ended: none in the following ten days.
Kamashi fire, January 2017
15,867 ha
18 days
FWI 47.2
Min. humidity 10 %
16 km away, in 2017
First rain (1 mm or more) after it ended: none in the following ten days.
Yaso fire, February 2016
2,493 ha
4 days
FWI 45.8
Min. humidity 11 %
25 km away, in 2016
First rain (1 mm or more) after it ended: none in the following ten days.
Kamashi fire, January 2017
3,924 ha
12 days
FWI 44.7
Min. humidity 9 %
10 km away, in 2017
First rain (1 mm or more) after it ended: none in the following ten days.
Yaso fire, March 2025
3,067 ha
3 days
FWI 45.3
Min. humidity 12 %
28 km away, in 2025
First rain (1 mm or more) after it ended: none in the following ten days.
What happened to them
- 9 days
- median duration
- 2,873 ha
- median area
- 100 %
- went past 1,000 ha
- 1.5 mm
- rain at the end (median; 1 of 23 had it)
It was 1.7 times larger than the median of its twins and lasted 5 days, against 9 days.
Only 7 of its 23 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 22 of 23, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 1.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
—first rain
—no rain in ten days
31km/h · max. gust
It was considered over on 23 Feb, and not even 1 mm fell in the following ten days: it went out without rain. Twins with rain when they ended: 1 of 23, with a median of 1.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 2020
After · 1 Mar 2020
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.
Detections table · 154Every satellite heat detection, one by one, with time, satellite, power and coordinates.
⬇ Download CSV
Times in UTC. Each detection is a 375 m pixel: a large fire yields hundreds per pass.
| Date and time | Satellite | FRP (MW) | Lat | Lon |
|---|
Other fires nearby
- 9,791 haAgalometi27 January 2017 · 15 days · 2 km away
- 8,926 haAgalometi24 January 2026 · 8 days · 4 km away
- 13,615 haAgalometi25 January 2016 · 20 days · 8 km away
- 10,580 haAgalometi19 January 2022 · 21 days · 9 km away
- 12,814 haYaso11 January 2019 · 19 days · 10 km away
- 27,728 haKamashiJanuary 2021 · 30 days · 15 km away
Frequently asked questions
- How long did the Agalometi fire last?
- GWIS (Copernicus) dates it between 19 February 2020 and 23 February 2020: 5 days 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 4,879 hectares (48.8 km²). It is an estimate: official national figures may differ.
- Which municipalities burned?
- The fire only entered Agalometi (4,909 ha, 2.8 %).
- What was the weather like?
- During the fire the temperature reached 34.4 °C, humidity dropped to 10 % and gusts hit 31 km/h. The fire danger index (FWI) reached 48, class Very high.
- Where does this data come from?
- From the GWIS (Copernicus) burnt perimeter, NASA FIRMS VIIRS hotspots and the administrative boundaries of Ethiopia (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: 23. Their median duration was 9 days and their median area 2,873 ha; 100 % went past 1,000 ha. Only 7 of its 23 twins burned more. The weather on the first day does not explain everything: the wind in the following days, the fuel and the firefighting also count. In 22 of 23, not even 1 mm fell in the ten days after the end: they went out without rain. In the rest, the first rainy day brought a median of 1.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.
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. 154 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 2020, 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.