Skip to content
worldfires
ET · Ethiopia · SNNPR

Wildfires in Gurafereda

Gurafereda, Ethiopia, has had 14 large fires recorded by GWIS since 2016: 61,523 hectares burned inside its boundaries, 25% of its area. Fire danger today: very low (FWI 3).

Only fires of 2,000 ha or more get an entry: smaller ones are not in the lists or the totals on this page.

Fire danger, today and the coming days

FWI computed from the Open-Meteo forecast
  1. Thu 29 Very low 30° · 44 % · 29 km/h
  2. Fri 30 Very low 31° · 38 % · 22 km/h
  3. Sat 31 Low 32° · 34 % · 26 km/h
  4. Sun 1 Low 33° · 26 % · 25 km/h
  5. Mon 2 Moderate 34° · 22 % · 26 km/h
  6. Tue 3 Moderate 34° · 26 % · 25 km/h
  7. Wed 4 Moderate 35° · 22 % · 35 km/h
  8. Thu 5 Moderate 36° · 20 % · 36 km/h

Canadian Fire Weather Index, the same system Copernicus uses, computed by WorldFires from the weather forecast and two months of past weather for fuel state. It is an estimate per municipality, not an official warning: warnings are issued by each country’s emergency service.

The municipality and its fires

Since 2016

61,523
hectares burned
25 %
of its area
14
fires
2,495
km²

How many times has Gurafereda burned?

Gurafereda has burned 14 times since 2016, in 3 years: 2016, 2017 and 2019. The most recent: Gurafereda fire, 24 January 2019, with 625 hectares inside the municipality. Together they add up to 61,523 hectares burned inside the municipality, but the distinct burned area is 50,636 hectares, 20 % of its surface: part of it burned more than once.

  1. 3× 16
  2. 6× 17
  3.   18
  4. 5× 19
  5.   20
  6.   21
  7.   22
  8.   23
  9.   24
  10.   25
  11.   26
14
fires
3
years with fire
61,523
cumulative ha
50,636
distinct ha

Fires larger than 2,000 hectares with a perimeter since 2016 that reached the municipality, even partly. Cumulative hectares add up every fire; the distinct area counts land that burned several times only once. Perimeters and boundaries overlaid by WorldFires.

Where it has burned most often in Ethiopia →

Fires that entered Gurafereda

  1. 625 ha Gurafereda fire, 24 January 2019 where it started 0.2% of the municipality · 4,143 ha in total · 9 days
  2. 3,994 ha Gurafereda fire, 19 January 2019 where it started 1.6% of the municipality · 3,966 ha in total · 13 days
  3. 2,773 ha Gurafereda fire, 19 January 2019 where it started 1.1% of the municipality · 2,756 ha in total · 11 days
  4. 2,267 ha Dima fire, 10 January 2019 0.9% of the municipality · 2,459 ha in total · 6 days
  5. 2,088 ha Gurafereda fire, 6 January 2019 where it started 0.8% of the municipality · 2,075 ha in total · 8 days
  6. 2,739 ha Gurafereda fire, 16 January 2017 where it started 1.1% of the municipality · 2,720 ha in total · 13 days
  7. 52 ha Dima fire, 12 January 2017 0.0% of the municipality · 7,100 ha in total · 9 days
  8. 2,477 ha Gurafereda fire, 4 January 2017 where it started 1.0% of the municipality · 2,702 ha in total · 12 days
  9. 5,278 ha Gurafereda fire, 3 January 2017 where it started 2.1% of the municipality · 5,360 ha in total · 21 days
  10. 10,208 ha Gurafereda fire, 1 January 2017 where it started 4.1% of the municipality · 10,963 ha in total · 19 days
  11. 15,214 ha Gurafereda fire, 1 January 2017 where it started 6.1% of the municipality · 15,140 ha in total · 24 days
  12. 9,255 ha Gurafereda fire, 3 December 2016 where it started 3.7% of the municipality · 9,294 ha in total · 6 days
  13. 2,029 ha Gurafereda fire, 2 December 2016 where it started 0.8% of the municipality · 2,017 ha in total · 5 days
  14. 2,525 ha Gurafereda fire, February 2016 where it started 1.0% of the municipality · 2,507 ha in total · 10 days

Where this data comes from

Perimeters come from GWIS (Copernicus, CC BY 4.0), rebuilt from heat detections, and municipal boundaries from geoBoundaries/Open Africa, Code for Ethiopia (Open Data Commons Open Database License 1.0). The area per municipality is computed by WorldFires by crossing both. The forecast is from Open-Meteo (CC BY 4.0).

Tell me what burns here

New fires in this area by RSS: paste the link into your reader, no email needed.