Reanalysis of the 2000 Rift Valley fever outbreak in Southwestern Arabia.

The first documented Rift Valley hemorrhagic fever outbreak in the Arabian Peninsula occurred in northwestern Yemen and southwestern Saudi Arabia from August 2000 to September 2001. This Rift Valley fever outbreak is unique because the virus was introduced into Arabia during or after the 1997-1998 East African outbreak and before August 2000, either by wind-blown infected mosquitos or by infected animals, both from East Africa. A wet period from August 2000 into 2001 resulted in a large number of amplification vector mosquitoes, these mosquitos fed on infected animals, and the outbreak occurred. More than 1,500 people were diagnosed with the disease, at least 215 died, and widespread losses of domestic animals were reported. Using a combination of satellite data products, including 2 x 2 m digital elevation images derived from commercial satellite data, we show rainfall and potential areas of inundation or water impoundment were favorable for the 2000 outbreak. However, favorable conditions for subsequent outbreaks were present in 2007 and 2013, and very favorable conditions were also present in 2016-2018. The lack of subsequent Rift Valley fever outbreaks in this area suggests that Rift Valley fever has not been established in mosquito species in Southwest Arabia, or that strict animal import inspection and quarantine procedures, medical and veterinary surveillance, and mosquito control efforts put in place in Saudi Arabia following the 2000 outbreak have been successful. Any area with Rift Valley fever amplification vector mosquitos present is a potential outbreak area unless strict animal import inspection and quarantine proceedures are in place.

Introduction

Rift Valley fever is a mosquito-borne viral hemorrhagic fever that affects domestic animals and humans. First described in 1931, the virus responsible for Rift Valley fever is in the genus Phlebovirus and the family Bunyaviridae. The first documented occurrence or epizootic of Rift Valley fever occurred in 1930–1931 near Lake Naivasha, Kenya, in the Rift Valley of East Africa, with high mortality among domestic sheep [1]. Although Rift Valley fever primarily affects domestic animals, mainly sheep, goats and cattle, it can also infect humans, causing illness and death in some cases [2]. Most human infections have resulted from bites from infected mosquitoes, through contact with infected animals, and to a lesser extent, through contact with infected animal tissue [3]. Rift Valley fever has been exclusively a disease of Africa and Madagascar, with the exception of the Southwest Arabian 2000–2001 outbreak [4, 5] (Fig 1).

Fig 1

Potential epizootic areas of Rift Valley fever in Africa and Madagascar are shown in green [4].

Four areas in Saudi Arabia and Yemen are shown in the insert where significant numbers of people were infected in the 2000–2001 outbreak were noted by the red triangles. While Rift Valley fever has largely been an African disease, there were no documented Rift Valley fever outbreaks in Arabia prior to 2000–2001 and there have been none since that time.

Rift Valley fever infections in humans are usually mild, with an incubation period of 2 to 5 days following exposure. Those infected may experience no detectable symptoms or may develop a sudden-onset influenza-like fever, headache, gastrointestinal discomfort, and general body malaise. However, these symptoms are transitory and do not persist for more than 7 days. Other patients develop symptoms that may be mistaken for meningitis: loss of appetite; vomiting; sensitivity to light; and neck stiffness. While most human Rift Valley fever infections are mild, ~4% of human infections are more severe. These more severe infections are manifested as one or more of three syndromes: ocular disease; meningoencephalitis; and/or hemorrhagic fever [2].

While death is uncommon for patients with the ocular form of Rift Valley fever, some infected patients experience a permanent loss of vision. The meningoencephalitis form of Rift Valley fever is usually manifested a few weeks after initial infection, with symptoms including convulsions, lethargy, coma, hallucinations, memory loss, and vertigo. The death rate of this form of the disease is low, although neurological complications can appear several weeks later. The hemorrhagic fever form of Rift Valley fever has a case fatality rate of ~50%. Symptoms of this form of the disease include bleeding in the gastrointestinal tract, bleeding in the skin, bleeding from the nose or gums, other hemorrhage, and severe liver impairment. Death is reported to occur 3 to 6 days after onset of symptoms of this severe form of Rift Valley fever. Fortunately, this Rift Valley fever syndrome is infrequent in infected humans [2].

There is no licensed Rift Valley fever vaccine for humans. Several effective vaccines for animals are available; however, animal immunization must occur before an outbreak starts. Thus, early warning of possible pending outbreaks several weeks in advance is extremely important, as this enables vaccination programs for animals, enables personal protection methods for humans, and enables mosquito vector control to be undertaken.

Mosquito vector ecology and population dynamics

Rift Valley fever virus transovarially infects the eggs of at least one species of the mosquito genus Aedes [6]. That is, the mosquito eggs are laid already infected with the virus. These infected eggs lie dormant in the soil of unflooded mosquito habitats in the endemic area. Following periods of prolonged rainfall, local flooding occurs and the already-infected eggs hatch and immature mosquito stages develop into infected adults. These infected mosquitoes transmit the Rift Valley fever virus to animals upon whom they feed, although usually at a very low level, because they are inefficient transmitters of the disease [7]. Among domestic animals, there is variability in susceptibility of different species and breeds with sheep, goats, and camels being the primary species affected. Although larger wild animals become infected and develop viremia, most wild animals in endemic regions exhibit minimal disease [8, 9].

Without prolonged rainfall for several weeks, any initial Rift Valley fever outbreak would be local in nature and would not be a reported outbreak. However, if excessive rainfall continues for 5 to 7 weeks duration or longer, mosquitoes of the genus Culex develop in these flooded areas, hatch, become numerous, and are very efficient transmitters of the Rift Valley fever virus (Fig 2). The Culex and Mansonia species are the amplification or expansion vectors for Rift Valley fever outbreaks. They acquire the virus from infected livestock and then efficiently infect large numbers of other animals quickly [4, 10, 11].

Fig 2

Mosquito numbers after mosquito habitats were flooded in East Africa as determined from collecting and identifying mosquito species.

Vector specimens collected from the Kamiti dambo, Kenya from November 28—December 27, 1982 [6].

Rift Valley fever has occurred intermittently over much of sub-Saharan Africa, with outbreaks reported in many countries (Fig 1). In East and Southern Africa, Rift Valley fever activity has been reported in the proximity of grassland depressions [12-15]. These depressions can flood seasonally and, when flooded, are good habitats for the development of immature Aedes and Culex mosquito species that serve as Rift Valley fever vectors [10, 11]. In dry areas of Senegal and Mauritania and in irrigated areas of Egypt, Rift Valley fever outbreaks have occured in riverine areas [16-18].

Area of study

Our area of study was the southwestern part of the Arabian Peninsula, where Saudi Arabia borders Yemen along the Red Sea (Fig 3). There are three climatic zones present in this region: the Tihama, the dry coastal plain with elevations below 400 meters above sea level and minimal precipitation, usually <150 mm/yr; a region composed of hills with elevations between 400 and 600 meters with <300 mm annual precipitation; and a mountainous region with elevations 600 meters and above with annual precipitation of 300 to 800 mm annual precipitation [19]. The Tihama is a large alluvial plain that is intensely cultivated where irrigation is possible from many dams. Periods of higher precipitation in the Sarawat Mountains result in higher runoff into ephemeral streams that flow to the Tihama. These agricultural areas and reservoirs create pools of standing water ideal for mosquito production, particularly during periods of excessive and persistent rainfall upstream.

Fig 3

The Landsat-7 NDVI difference between May/June 2000 and September 2000 shows the increase in green vegetation density from increased rainfall by September 2000 in the Sarawat Mountains for Southwest Arabia.

This in turn, resulted in more runoff to the coastal plain or Tihama that provided ideal conditions for the emergence of Rift Valley fever mosquito vectors. Specific outbreak locations occurred from Al Qunfuda, Saudi Arabia in the north to Wadi Mawr, Yemen in the south and are noted by red triangles where they were reported. This figure is from Anyamba et al. [5].

Remote sensing surveillance of Rift Valley fever is based upon: (1) Monitoring through time rainfall or a surrogate for rainfall in the Rift Valley fever endemic area (Fig 1); and (2) Identifying periods of anomalous rainfall that persist for more than 5 to 7 weeks in the Rift Valley fever endemic area. Previous work using satellite and ground data has documented and confirmed this approach for several areas [11, 12, 14, 20].

We use the satellite normalized difference vegetation index (NDVI) [21] as a surrogate for rainfall. We also introduce a new capability for mapping mosquito breeding habitats, through the use of digital elevation data derived from commercial satellite data stereo image pairs [22]. This new mapping of possible mosquito breeding areas at the 2 x 2 m scale identifies potential inundation areas.

There are two methods commonly used to monitor or infer rainfall from Rift Valley fever endemic areas: (1) Measure rainfall directly using the rain gauge network and/or use rainfall estimates from satellite data such as the Tropical Rainfall Monitoring Mission [23], geostationary MeteoSat satellites [24], or the Global Precipitation Mission [25] or (2) Use a NDVI remote sensing approach from which rainfall can be inferred [26-28]. While it would be desirable to monitor rainfall directly, the rain gauge network in much of sub-Saharan Africa is sparse and discontinuous [28] and estimates from Meteosat, the Tropical Rainfall Monitoring Mission, and the Global Precipitation Mission have only been available since the early 1990s and have a coarse spatial resolution. For these reasons, and especially for spatial specificity at the scale of tens to hundreds of meters, we use the time series NDVI-rainfall monitoring approach.

NDVI time series exist from the Advanced Very High Resolution Radiometer (AVHRR) instruments since July 1981 globally at an 8-km resolution [29]; from the Satellite Pour l’Observation de la Terre (SPOT) vegetation-PROBA V-Sentinel 3 satellite continuum and have been available globally since May 1998. SPOT vegetation data have a spatial resolution of 1 km from 1998–2013 [30] while PROBA V and Sentinel-3 data are available at 330 m from 2013 [31]; from NASA’s moderate resolution imaging spectrometer (MODIS) instruments availably globally since January 2000 at a 250 m resolution [32]; and from Landsat at 30 m since Landsat-4 was launched in 1982 [33].

The NDVI approach we employ is based upon spectral characteristics of vegetation directly related to photosynthesis in terrestrial vegetation. Green leaves in plant canopies have low red reflectance due to strong chlorophyll absorption in the red portion of the spectrum and a very high reflectance in the near infrared portion, where minimal absorption occurs. This unique spectral response of green leaves makes it possible to differentiate green vegetation from other surface constituents by remote sensing. The normalized difference vegetation index is calculated as:

Where ρnir and ρred are the surface reflectances in the near infrared and red portions of the electromagnetic spectrum, respectively [19]. Derived NDVI values range between -1 to +1, with values below zero indicating absence of green vegetation and positive values progressively showing more green leaf density. The variability of rainfall and the dynamics of vegetation in semi-arid lands are a major determinant of life cycles of animals and insects. There is a close relationship between seasonal green vegetation density and persistence, the NDVI, and breeding and upsurge patterns of particular insects, including locusts and mosquitoes [12, 13, 15, 16, 34, 35].

In addition to using NDVI data from a variety of different instruments to infer rainfall from subsequent green vegetation development, we employ digital elevation images derived from commercial satellite data along-track stereo image pairs to map the potential for inundation at the 2 x 2 m scale in Rift Valley fever outbreak areas [22]. The area of possible inundation is directly related to potential mosquito breeding density.

The Southwestern Arabian 2000 Rift Valley fever outbreak

Reports of an outbreak of an unknown disease first appeared in Saudi Arabian newspapers in early September 2000. Initial reports in mid-September 2000 were from Jazan state, in Southwestern Saudi Arabia adjacent to Yemen, and described an unknown disease infecting ~ 60 people with ~30 fatalities [36]. Disease symptoms in the affected patients were described as high fever, diarrhea, burst arteries, and renal failure. Bleeding from the mouth, nose, and ears and eye lesions were common in affected patients. Jazan state is known for its heat and humidity during the rainy season at this time of year, that makes it an excellent breeding area for mosquitoes. A spokesman for the Saudi Arabian health authority reported the disease was transmitted by sheep and a large number of domestic animals had died in Jizan state, Saudi Arabia [36]. Jazan state lies 300 km across the Red Sea from Africa and is adjacent to Yemen.

Saudi Arabian authorities in Jazan State imposed emergency measures after cases of the Rift Valley fever were confirmed in late 2000. Measures included closing schools for several weeks, intensive mosquito control spraying, and a ban on the importation of domestic animals from the Horn of Africa.

On September 20, 2000, another Rift Valley fever outbreak was reported in the Wadi Mawr area of the Huseidah region of Yemen that resulted in 50 deaths [37]. Laboratory confirmation of the disease in both Saudi Arabia and Yemen was made by the World Health Organization’s Collaborating Centre at the Centers for Disease Control and Prevention in Atlanta, Georgia [38].

By early November 2000, more than 1,500 people were diagnosed as having contracted Rift Valley fever in both countries and at least 215 died: 106 in Saudi Arabia and 109 in Yemen. The death rate is perhaps the highest case fatality rate (~13%) for a Rift Valley fever outbreak to date. However, the number of deaths could be correct while the number of infected people was under reported, thus lowering the case fatality rate. Several thousand domestic animals also perished but exact numbers were not reported [39].

Materials and methods

Our analysis was preceded by conference presentation in 2014 that used ecological niche modeling coupled with satellite-derived land surface temperature and NDVI [40]. This work was calibrated based on previous African outbreaks and extrapolated to predict outbreak sites in Arabia in the Gizan region. We provide additional evidence for the validity of this approach by using three sources of NDVI data that identified the same outbreak areas in western Saudi Arabia. Three sources of NDVI satellite data were used for our rainfall analysis in southwestern Arabia: 8-km data from 1981 to 2016 derived from the AVHRR instruments carried on a series of polar-orbiting meteorological satellites operated by the National Oceanic and Atmospheric Administration and the European Organization for the Explotation of Meteorological Satellites; NASA 250 m MODIS imagery from 2000 to early 2020; and NASA and US Geological Service 30 m data derived from Landsat-7's Enhanced Thematic Mapper instrument for 2000 and 2001. We now are able to complement Landsat 30 m data with “harmonized” Landsat-8 and Sentinel-2a and Sentinel-2b 30 m data if greater spatial detail is needed [41]. These harmonized data provide time series NDVI data at a 30 m spatial resolution with a revisit frequency of 3.7 days at the equator. Fig 4 shows the NDVI correspondence between AVHRR 8 km and MODIS 250 m data for the Arabian outbreak area.

Fig 4

(A). The AVHRR NDVI 8 km anomalies from July 1981 to December 2016 from the area in (4c). (B). The MODIS 250 m NDVI anomalies for the same area from 2000 to 2019 in (4c) from Al Qunfunda, Saudi Arabia to Wadi Mawr, Yemen, from the coast to the foothills of the Sarawat mountains, an area of 100,000 km2 in Southwestern Arabia bordering the Red Sea in the image of (C). Positive NDVI values are a consequence of above-average rainfall and are color-coded in blue in both 4a and 4b [27]. Dryer periods are color-coded in red. It is possible the introduction of Rift Valley fever virus into Southwest Arabia occurred in 1997–1998, while the East Africa 1997–1998 Rift Valley fever outbreak was underway. Note the very similar NDVI trends from 2000 to 2016 derived from AVHRR NDVI and from MODIS NDVI data. The MODIS NDVI data in Fig 4b show favorable conditions for Rift Valley fever outbreaks in 2016–2019 but none have occurred in Arabia during this time.

We also used two DigitalGlobe WorldView-1 along-track stereo pair images acquired on November 7, 2017 only seconds apart from which elevation data were determined. These data were processed using the Surface Extraction with TIN-based Search-space Minimization (SETSM) algorithm [22] to produce a 2 x 2 m digital elevation hillshaded image with a vertical uncertainty of ±70 cm (Fig 5). An analysis of the digital elevation profile and image for Fig 5 found 2.1 km2 of potentially inundated areas that were comprised of 4,188 different 100 km2 or greater non-connected areas. This capability is a new tool to address mosquito-linked infectious diseases and provides direct identification and innumeration of small mosquito breeding areas.

Fig 5

(A) WorldView-1 panchromatic 2 m resolution image from November 7, 2017 from the Wadi Mawr village area of Northwest Yemen; and (B) a stereo digital elevation hillshaded image and elevation profile produced from a stereo pair of WorldView-1 panchromatic images acquired on November 7, 2017 from the same area. The high-resolution elevation data shows potential inundated areas along the terrian. Mapping inundated areas to identify potential mosquito-breeding habitats is a new tool for infectious disease study.

Results and discussion

In tandem with the Landsat-7 NDVI analysis in Fig 3, we examined NDVI3g AVHRR data from 1981 to 2016 and MODIS 8-day NDVI from April 2000 through April 2019 (Fig 4). Because the outbreak occurred in September 2000, it must have rained in the region during the preceding weeks to allow for the flooding of mosquito breeding habitats and subsequent emergence of the Rift Valley fever vectors to initiate a large-scale outbreak [4]. The Landsat, NDVI3g, and MODIS NDVI anomalies from May to September 2000 showed a strip of persistent positive anomalies along the Sarawat mountain range. This mountain range, ~2000 meters above the sea and parallel to the Red Sea, is the most prominent elevated topographic feature in this region. Rainfall falling on the mountain range drains into ephemeral streams that in turn flow to the coastal plain. The reported focal areas of the outbreak in Saudi Arabia, Al Qunfuda and Jizan are cities, while Asir is a state. The reported focal area of the outbreak in Yemen was Wadi Mawr, also a district. These four locations are located on the coastal plain (Fig 3).

It has been suggested that 2000 Arabian Rift Valley fever outbreak resulted from the importation of infected livestock animals from East Africa before the 2000 outbreak. The period of rainfall from late August 2000 into 2001 would have provided the conditions for the presence of mosquito amplification vectors (Fig 4) [42-45]. However, it is not known if the virus was introduced to Arabia in 1997–1998 or 1999–2000.

However, the genetic sequence of the Rift Valley fever viruses isolated in Saudi Arabia during this period were closely related to virus samples isolated during the 1997–1998 epizootic in East Africa [46-48]. While no Rift Valley fever outbreaks were reported in Africa in the June to September 2000 time period, the disease can be present and be undetected in a residual manner within herbivore populations.

Most agriculture in this region is practiced in the coastal plain, and during the heavy rains in the Sarawat Mountains, agricultural fields become inundated, creating ideal habitats for mosquito breeding as we show with our 2 m scale digital elevation surface mapping. Malaria has been known to be endemic in the lowlands of this region and various species of Anopheles mosquitoes, including Anopheles arabiensis and Anopheles gambiae, have been identified there [49].

Other mosquito species possibly implicated in Rift Valley fever Southwest Arabian outbreak include Culex tritaneniorhynchus and Aedes vexans arabiensis mosquitoes in the Jizan area of Saudi Arabia, where more than 75,000 mosquitoes were collected between September 25, 2000 and October 10, 2000 and 23,699 were tested for Rift Valley fever virus [50].

Since early 2001, the Ministries of Agriculture and Health of Saudi Arabia have taken precautionary measures to prevent renewed outbreaks of Rift Valley fever. These measures included: providing Rift Valley fever animal vaccines and veterinarians to carry out the vaccination program; undertaking mosquito control efforts during periods of high rainfall; and routine mosquito testing for the Rift Valley fever virus [51]. Medical surveillance of humans has also been actively undertaken, with possible Rift Valley fever cases reported in September 2004 in Al Karbous village [52], in December 2008 in Asir state [53, 54], in May 2009 where 33 cases were reported in Jeddah and 103 in Mecca [55], and in May 2010 in Najran City [56]. Routine veterinary serosurveillance is also undertaken, with five seropositive Rift Valley fever cases detected in four flocks of sheep reported in April 2004 in Jizan, although without clinical confirmation [57].

Al-Afaleq et al. 2012 [58] report a summary of veterinary surveillance, where a total of 3,480 sheep, goats, cattle and camels with no history of vaccination against Rift Valley fever were tested at random in Saudi Arabia. All animals tested were negative for IgG class antibodies against the virus, except three out of 913 goats and four out of 1,508 sheep, which tested positive. No virus activity evidence was found in the areas studied where the three goats and four sheep tested positive. All seven animals were clinically normal. These rare positive cases were attributed to false positives or vaccinated animals transferred from other areas [58].

While Saudi Arabia has instituted a thorough, continuing, and apparently successful program of medical and veterinary Rift Valley fever surveillance since the 2000 outbreak, the same cannot be said for Yemen. The on-going conflict in Yemen has made animal importation inspections, quarantine, and medical and veterinary surveillance activities there impossible since 2015.

Conclusions

The Arabian 2000 Rift Valley fever outbreak was unique in that infected animals were imported into areas where large numbers of mosquito amplification vectors were present, although it is not known when the infected animals were introduced into Arabia. Amplification vector mosquitos fed upon infected animals and the outbreak started. Using satellite data, we document the 2000 to 2018 precipitation regime for the coastal areas to the Sarawat Mountains of southwest Arabia with time series MODIS NDVI data at the 250 m scale in Fig 4. These data, coupled with the extensive number of potential-inundated mosquito breeding areas determined from digital elevation imagery at the 2 x 2 m scale in Fig 5, document excellent mosquito breeding potential in southwest Arabia in wetter periods. The fact no major RVF outbreak have occurred since 2000, and especially between 2015 to 2018 when the rainfall regime was very favorable to outbreaks, leads to two conclusions: (1) the Rift Valley fever reservoir was not established in Aedes mosquitos in Southwest Arabia after the 2000 outbreak; and/or (2) effective Rift Valley fever domestic animal quarantine and import restrictions, medical and veterinary surveillance, and mosquito control institutued by the Saudi Arabian Ministry of Agriculture have prevented outbreaks in that country. The conflict in Yemen since 2015 hinders preventative action such as undertaken in Saudi Arabia and is thus a cause for concern.

20 Sep 2019

PONE-D-19-21159

Reanalysis of the 2000 Rift Valley fever outbreak in Southwestern Arabia

PLOS ONE

Dear Dr. Tucker,

Thank you very much for submitting your manuscript "Reanalysis of the 2000 Rift Valley fever outbreak in Southwestern Arabia" (#PONE-D-19-21159) for review by PLOS ONE. As with all papers submitted to the journal, your manuscript was fully evaluated by academic editor (myself) and by independent peer reviewers. The reviewers appreciated the attention to an important health topic, but they raised substantial concerns about the paper that must be addressed before this manuscript can be accurately assessed for meeting the PLOS ONE criteria. Therefore, if you feel these issues can be adequately addressed, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process. We can’t, of course, promise publication at that time.

We would appreciate receiving your revised manuscript by Nov 04 2019 11:59PM. When you are ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter.

To enhance the reproducibility of your results, we recommend that if applicable you deposit your laboratory protocols in protocols.io, where a protocol can be assigned its own identifier (DOI) such that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols

Please include the following items when submitting your revised manuscript:

A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). This letter should be uploaded as separate file and labeled 'Response to Reviewers'.

A marked-up copy of your manuscript that highlights changes made to the original version. This file should be uploaded as separate file and labeled 'Revised Manuscript with Track Changes'.

An unmarked version of your revised paper without tracked changes. This file should be uploaded as separate file and labeled 'Manuscript'.

Please note while forming your response, if your article is accepted, you may have the opportunity to make the peer review history publicly available. The record will include editor decision letters (with reviews) and your responses to reviewer comments. If eligible, we will contact you to opt in or out.

We look forward to receiving your revised manuscript.

Kind regards,

Abdallah M. Samy, PhD

Academic Editor

PLOS ONE

Additional Editor Comments:

I invited and received three reviews for your manuscript. All reviews raised some substantial concerns about your manuscript as it currently stands. As such, I would recommend “major revision”. I would kindly ask you to go through all comments raised by each reviewer and address them properly before sending a revised version of this manuscript. Please check all PLOS ONE style requirements available via https://journals.plos.org/plosone/s/submission-guidelines before submitting the revised version.

Journal requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at

http://www.journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and http://www.journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. We note that Figures 1, 3 and 5 in your submission contain map/satellite images which may be copyrighted.

All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For these reasons, we cannot publish previously copyrighted maps or satellite images created using proprietary data, such as Google software (Google Maps, Street View, and Earth). For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright.

We require you to either (a) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (b) remove the figures from your submission:

a. You may seek permission from the original copyright holder of Figures 1, 3 and 5 to publish the content specifically under the CC BY 4.0 license.

We recommend that you contact the original copyright holder with the Content Permission Form (http://journals.plos.org/plosone/s/file?id=7c09/content-permission-form.pdf) and the following text:

“I request permission for the open-access journal PLOS ONE to publish XXX under the Creative Commons Attribution License (CCAL) CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). Please be aware that this license allows unrestricted use and distribution, even commercially, by third parties. Please reply and provide explicit written permission to publish XXX under a CC BY license and complete the attached form.”

Please upload the completed Content Permission Form or other proof of granted permissions as an "Other" file with your submission.

In the figure caption of the copyrighted figure, please include the following text: “Reprinted from [ref] under a CC BY license, with permission from [name of publisher], original copyright [original copyright year].”

b. If you are unable to obtain permission from the original copyright holder to publish these figures under the CC BY 4.0 license or if the copyright holder’s requirements are incompatible with the CC BY 4.0 license, please either i) remove the figure or ii) supply a replacement figure that complies with the CC BY 4.0 license. Please check copyright information on all replacement figures and update the figure caption with source information. If applicable, please specify in the figure caption text when a figure is similar but not identical to the original image and is therefore for illustrative purposes only.

The following resources for replacing copyrighted map figures may be helpful:

USGS National Map Viewer (public domain): http://viewer.nationalmap.gov/viewer/

The Gateway to Astronaut Photography of Earth (public domain): http://eol.jsc.nasa.gov/sseop/clickmap/

Maps at the CIA (public domain): https://www.cia.gov/library/publications/the-world-factbook/index.html and https://www.cia.gov/library/publications/cia-maps-publications/index.html

NASA Earth Observatory (public domain): http://earthobservatory.nasa.gov/

Landsat: http://landsat.visibleearth.nasa.gov/

USGS EROS (Earth Resources Observatory and Science (EROS) Center) (public domain): http://eros.usgs.gov/#

Natural Earth (public domain): http://www.naturalearthdata.com/

3. We note that you have indicated that data from this study are available upon request. PLOS only allows data to be available upon request if there are legal or ethical restrictions on sharing data publicly. For information on unacceptable data access restrictions, please see http://journals.plos.org/plosone/s/data-availability#loc-unacceptable-data-access-restrictions.

In your revised cover letter, please address the following prompts:

a) If there are ethical or legal restrictions on sharing a de-identified data set, please explain them in detail (e.g., data contain potentially identifying or sensitive patient information) and who has imposed them (e.g., an ethics committee). Please also provide contact information for a data access committee, ethics committee, or other institutional body to which data requests may be sent.

b) If there are no restrictions, please upload the minimal anonymized data set necessary to replicate your study findings as either Supporting Information files or to a stable, public repository and provide us with the relevant URLs, DOIs, or accession numbers. Please see http://www.bmj.com/content/340/bmj.c181.long for guidelines on how to de-identify and prepare clinical data for publication. For a list of acceptable repositories, please see http://journals.plos.org/plosone/s/data-availability#loc-recommended-repositories.

We will update your Data Availability statement on your behalf to reflect the information you provide.

4. Please amend your list of authors on the manuscript to ensure that each author is linked to an affiliation. Authors’ affiliations should reflect the institution where the work was done (if authors moved subsequently, you can also list the new affiliation stating “current affiliation:….” as necessary).

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Is the manuscript technically sound, and do the data support the conclusions?

The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: Yes

**********

2. Has the statistical analysis been performed appropriately and rigorously?

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: No

**********

3. Have the authors made all data underlying the findings in their manuscript fully available?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: No

**********

4. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

Reviewer #3: No

**********

5. Review Comments to the Author

Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: The submitted Ms deals with an important topic and presented in very good shape that reflects the authors’ effort in planning and carrying it. However, very few comments and corrections were inserted within the text, these are:

1. Page 5, Line 92: are least susceptible Delete

2. Page 5, Line 96: Change “be a reported” to reported

3. In the whole text, replace/write Jazan for state, Jizan for city, for examples:

a. Change “Jizan” to Jazan in “Page 9, Line 186; Page 10, Line 193; Page 10, Line 193; Page 10, Line 195”

b. Page 13, Line 264: Jazan to Jizan

4. Page 10, Line 192: Change “reported to” reported that

5. Page 11, Line 223: (Fig 4) delete, repetition

6. Page 13, Line 267: Change “suggested to” suggested that

7. Page 14, Line 281: Change “arabiens” to arabiensis

8. Page 14, Line 281: and not Italic

9. Since mosquito control is the responsibility and taken by Health authorities:

a. Change Ministry of Agriculture to Ministries of Agriculture and Health (Page 14, Line 288)

b. Change “Agriculture” to Health (Page 16, Line 328)

Reviewer #2: The authors evaluate the 2000 Rift Valley fever virus outbreak in Yemen and Saudi Arabia using satellite data to determine favourable conditions based on rainfall and water availability for mosquitos. The authors further evaluate conditions from 2000 to 2018 to identify favourable conditions for Rift Valley fever virus outbreaks in the region.

Minor comments

Line 94 Replace with There is variability in the susceptibility of different species and breeds with sheep, goats, cattle and camels being the primary species affected.

Can this satellite data be used to determine the risk of Rift Valley fever virus outbreaks in regions where the disease is cyclically present such as South Africa and Kenya?

This is important as if this is the case this could be used to potentially predict Rift Valley fever virus outbreaks and be used to allow vaccination of animals prior to outbreaks.

Reviewer #3: The authors anticipated RVF outbreak in Saudi Arabia using remote sensing data. The manuscript is well-written; however, I have some concerns to the manuscript as it currently stands. These points should be addressed before considering a revised version of this manuscript.

- Provide justification for using this very finer spatial resolution for your study. Do you have RVF data in such spatial resolution for comparison.

- Similar analyses was presented early in 2014 ASTMH meeting by Egyptian researcher working at the University of Kansas (Check http://tiny.cc/95r2cz). I remember that Fig 1 was presented by Samy during the meeting, particularly the close-up map to Saudi Arabia with prediction to the West coast of Saudi Arabia and Yemen. Authors should refer clearly to this study across the manuscript text and cite it to the reference section.

- How authors managed to scale different spatial resolution of diverse climate data to present data with a finer resolution.

- These models didn't consider any additional dimensions for the key roles of the vector in anticipating the location with suitable conditions for disease occurrence.

- Robust validation approach for your prediction; i think authors should provide sensitive tools to evaluate their results. Positive cases identified in Western Saudi Arabia were more than just 4 sites presented in Fig 1 and 3.

**********

6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: Yes: Mohamed A Kenawy

Reviewer #2: No

Reviewer #3: No

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files to be viewed.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email us at figures@plos.org. Please note that Supporting Information files do not need this step.

Submitted filename: REV-PONE-D-19-21159_reviewer.pdf

Click here for additional data file.

30 Apr 2020

We agree with all the points and suggestions of the reviewers and have addressed every one of their concerns or questions:

1. We have studied PLOS ONE's style requirements and have modified our manuscript accordingly;

2. Figures 1 and 3 are figures which Jennifer Small, one of our coauthors, produced. Because she is employed by NASA, these images are in the public domain and are not copyrighted. Katherine Melocik, another coauthor produced figure 5. Figure 5a is copyrighted and we have obtained permission from the National Geospatial Intelligence Agency for public release of figure 5a--it is labeled accordingly. Because figure 5b is a derived product from NASA-licensed commercial satellite data, this figure is not copyrighted.

3. All data used in our manuscript are publicly available. This includes the Landsat-7 data in figure 3, the AVHRR data in figure 4a, the MODIS data in figure 4b, figure 5a, and the digital DEM in figure 5b.

4. We have amended our list of authors ensuring that each author is linked to an affiliation.

Reviewers' comments:

Reviewer #1: We have heeded this reviewers comments and suggestions for every one of his nine numbered points. We thank this reviewer for his thoroughness.

Reviewer #2: We replaced line 94 with exactly the wording suggested by this reviewer. We also have made excellent progress using satellite data to predict Rift Valley fever virus outbreaks in areas such as Kenya and South Africa to allow vaccination of animals prior to outbreaks.

Reviewer #3: We use 2 m WorldView-1 satellite data in figure 5 because these data are a stereo pair. These data enable the 2 m scale 3-D mapping of inundation potential for mosquito breeding habitats. We do not have Rift Valley fever data at the same spatial scale. However, our point here is to show a new potential for mapping fine-scale mosquito breeding habitats.

We thank reviewer #3 for bringing to our attention the work of Samy, Kenawy, and Townsend (2014). Our NASA librarian was able to find a description of this poster from the 2014 ASTMH meeting. We concur with reviewer #3 that this reference is very similar to our work and cite this work accordingly as reference 39 in our revised manuscript. We give this reference credit for their earlier description of the methodology for what we have also done. Furthermore, we acknowledge that our work strengthens their earlier work by using additional satellite data available after 2014.

We were able to scale different spatial resolutions of diverse climate data by using 30 m Landsat data as in figure 3, compared to the 250 m MODIS data and 8 km AVHRR data we used in figure 4.

We acknowledge Samy, Kenawy, and Townsend (2014) are the masters of ecological niche modeling which we did not use. Instead, we focused on uses of satellite data that support their expertise in ecological niche modeling. We showed very similar NDVI results using Landsat, MODIS, and AVHRR data sets over a 38-year period at three different spatial scales. Lastly, we show the use of stereo satellite data to map inundation potential at the 2 m scale. This technique compliments ecological niche modeling where inundation is an important consideration for ecological niches.

We attempted to use robust validation tools to test our Arabian predictions. See lines 292 to 315 in our revised manuscript. However, the results of these validations were mixed and inconclusive. This led us to conclude that Saudia Arabia had instituted a thorough and continuing program of medical and veterinary Rift Valley fever surveillance since the 2000 outbreak.

Submitted filename: Response to Reviewers PONE-D-19-21159.docx

Click here for additional data file.

4 May 2020

Reanalysis of the 2000 Rift Valley fever outbreak in Southwestern Arabia

PONE-D-19-21159R1

Dear Dr. Tucker,

We are pleased to inform you that your manuscript, "Reanalysis of the 2000 Rift Valley fever outbreak in Southwestern Arabia" (PONE-D-19-21159R1), has been judged scientifically suitable for publication and will be formally accepted for publication once it complies with all outstanding technical requirements.

Within one week, you will receive an e-mail containing information on the amendments required prior to publication. When all required modifications have been addressed, you will receive a formal acceptance letter and your manuscript will proceed to our production department and be scheduled for publication.

Shortly after the formal acceptance letter is sent, an invoice for payment will follow. To ensure an efficient production and billing process, please log into Editorial Manager at https://www.editorialmanager.com/pone/, click the "Update My Information" link at the top of the page, and update your user information. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to enable them to help maximize its impact. If they will be preparing press materials for this manuscript, you must inform our press team as soon as possible and no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

With kind regards,

Abdallah M. Samy, PhD

Academic Editor

PLOS ONE

3 Dec 2020

PONE-D-19-21159R1

Reanalysis of the 2000 Rift Valley fever outbreak in Southwestern Arabia

Dear Dr. Tucker:

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department.

If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org.

If we can help with anything else, please email us at plosone@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Abdallah M. Samy

Academic Editor

PLOS ONE