<?xml-model href='http://www.tei-c.org/release/xml/tei/custom/schema/relaxng/tei_all.rng' schematypens='http://relaxng.org/ns/structure/1.0'?><TEI xmlns="http://www.tei-c.org/ns/1.0">
	<teiHeader>
		<fileDesc>
			<titleStmt><title level='a'>Time to leave: an analysis of travel times during the approach and landfall of Hurricane Irma</title></titleStmt>
			<publicationStmt>
				<publisher></publisher>
				<date>09/01/2020</date>
			</publicationStmt>
			<sourceDesc>
				<bibl> 
					<idno type="par_id">10210577</idno>
					<idno type="doi">10.1007/s11069-020-04093-7</idno>
					<title level='j'>Natural Hazards</title>
<idno>0921-030X</idno>
<biblScope unit="volume">103</biblScope>
<biblScope unit="issue">2</biblScope>					

					<author>David Marasco</author><author>Pamela Murray-Tuite</author><author>Seth Guikema</author><author>Tom Logan</author>
				</bibl>
			</sourceDesc>
		</fileDesc>
		<profileDesc>
			<abstract><ab><![CDATA[Hurricane Irma caused widespread evacuation activity across Florida and some of its neighboring states in September of 2017. The researchers gathered estimated travel times from the Google Distance Matrix API over about a month to identify and analyze evacuation periods on roads in Florida, Georgia, and South Carolina during this time. Travel time data was mathematically adjusted to show more realistic estimations. Both sets of travel times were then graphed, with the assumption that elevated travel times prior to and during hurricane landfall were indicative of evacuation activity. The study generally corroborated the wellestablished daytime evacuation preference. However, not all evacuation periods followed the daytime travel preference, and at least one nighttime evacuation may have been caused by flooding. In another case, later elevated travel coincided with significant power loss. Finally, the Florida data suggest that most of the evacuation traffic departed before local jurisdictions' recommended evacuation start times.]]></ab></abstract>
		</profileDesc>
	</teiHeader>
	<text><body xmlns="http://www.tei-c.org/ns/1.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink">
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Hurricane Irma's approach in September 2017 led to a variety of evacuation announcements in the southeastern United States. Florida Governor Rick Scott urged residents to prepare for rapid evacuation on September 5 <ref type="bibr">(Mitchell 2017)</ref>, and, two days later, he issued another public statement to emphasize the danger the storm posed (WFLA staff 2017). These warnings were accompanied by local advisories around Florida. Also on September 5, Florida Keys emergency management officials issued a mandatory evacuation order for both tourists (beginning the next morning) and residents (beginning the evening of Sept. 6th) <ref type="bibr">(NWS Key West 2017a,b)</ref>. Irma made landfall near Cudjoe Key as a category 4 hurricane around 9:00 a.m. on September 10 and a subsequent landfall near Marco Island, FL around 3:35 pm local time <ref type="bibr">(Stein et al. 2017;</ref><ref type="bibr">Weather Underground 2018)</ref>. As Irma approached the Florida coast, some communities received advisories while others received mandatory evacuation notices (e.g., the differences between areas in the Florida panhandle, as shown by <ref type="bibr">Etters (2017)</ref> and Payne ( <ref type="formula">2017</ref>)). The announcements, initial concern, and uncertainty surrounding the storm's path resulted in evacuation traffic across Florida.</p><p>The traffic continued into Georgia and South Carolina, as those states were both evacuation destinations and possible secondary targets for Irma <ref type="bibr">(Stein et al. 2017</ref>).</p><p>This study uses travel time estimates from the Google Distance Matrix API (Google Maps' data source) recorded from September 5 to October 2, 2017 to gain more insight into aggregate evacuation behavior. Google Maps uses historical data and real-time data from sensors and cell phones to produce travel time estimates and route recommendations <ref type="bibr">(Brindle 2020 and references therein)</ref>. In this study, travel time estimate data is considered along with power outage information where available (recorded at UM-Ann Arbor from Florida Power and Light, Gulf Power, and Duke Energy) to provide more context. These datasets were used to address five research questions:</p><p>1. How do the estimated travel times at departure compare with travel times that have been adjusted to better reflect driver experiences? 2. When did evacuation noticeably begin and end in different areas, based on the travel time data indicating high travel times? 3. How do the evacuations align with official evacuation notices? 4. Do power outages have a discernible association with evacuation activity? 5. What were the best times (i.e., the moments with shortest travel times) for evacuees to leave their respective areas prior to Irma? This paper is divided into four sections. First, a literature review covers some key points related to the choices to evacuate and when. Then, the methodology and results are presented. The paper concludes with a discussion of the findings and suggestions for further investigation.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Literature Review</head><p>There has been substantial research into the factors associated with the decision of whether or not to evacuate. Since this paper is based on aggregate data, the following discussion is focused on broader factors, rather than individual or household level characteristics.</p><p>Based on survey responses, <ref type="bibr">Baker (1991)</ref> found that safety during an event is a primary concern and perceptions of safety are influenced by public announcements and advice from others. Similarly, <ref type="bibr">Sorensen (2000)</ref> indicated moderate levels of empirical support for perceived risk being associated with warnings and response to the warnings increasing with higher risk perception. Murray-Tuite and Wolshon (2013) and <ref type="bibr">Thompson, Garfin, and Silver (2017)</ref> also reported consistency in the literature of higher risk perception and receiving warnings as factors associated with evacuating across hazard types.</p><p>Areas that are geographically vulnerable during hurricanes often have evacuation rates over 80 percent; areas with lower perceived risk have much lower evacuation rates. However, low-risk areas also tend to produce evacuees that are not necessarily accounted for in the overall calculus, because they are not seen as likely candidates to join the evacuation stream <ref type="bibr">(Baker 1991)</ref>. This secondary group creates a "shadow" evacuation <ref type="bibr">(Zeigler et al. 1981)</ref>, which may contribute a non-trivial traffic volume.</p><p>Evidence also suggests that personal risk perception tends to encourage evacuation decision making. In focusing on the Florida Keys and Hurricane Georges, <ref type="bibr">Dash and Morrow (2001)</ref> found that residents made their decisions to evacuate based on their awareness of their precarious situation and their monitoring of the storm.</p><p>Even though there was a mandatory evacuation in the Keys, only around 53% of residents evacuated, with a much higher percentage evacuating in the region that actually experienced landfall. This suggests that Keys residents had a good feel for how their respective communities would be affected by Georges, and also that the mandatory evacuation order was a secondary consideration for them <ref type="bibr">(Dash and Morrow 2001)</ref>. It is possible that because of the unique circumstances in the Keys (one route of evacuation; isolated and exposed to hurricanes on the south side of Florida; limited shelter availability) <ref type="bibr">(Chen et al. 2005)</ref>, the residents have developed a heightened awareness of hurricane impacts.</p><p>To properly manage hurricane evacuations, it is necessary to understand not only the factors involved in making the decision to evacuate, but also the timing of the evacuation trips. In <ref type="bibr">Urbanik et al.'s (1980)</ref> function of the time it takes a household to evacuate are three terms not including travel time and thus associated with departure time: the time it takes for authorities to decide to issue an evacuation notice, the time it takes a household to receive the warning, and the time it takes a household to prepare to evacuate. These terms are not necessarily additive in the hurricane context since a household may begin preparing to evacuate based on weather forecasts and other information and may even leave before an evacuation notice. However, announcements from authorities can affect evacuation urgency, as was believed to have been the case in Hurricane Floyd in 1999. Voluntary and mandatory evacuation announcements spaced just five hours apart appeared to contribute to the ensuing severe traffic congestion on the interstates heading inland.</p><p>Though the announcements probably did not give people the initial idea to leave, the rapidity with which the bulk of the evacuation ensued thereafter (61% left the same day) suggests that the decision of when to leave was affected by the announcements <ref type="bibr">(Dow and Cutter 2002)</ref>. <ref type="bibr">Lindell, et al. (2005)</ref> found that during Hurricane Lili in 2002, the evacuation on the U.S. Gulf Coast began on the same morning that the National Hurricane Center (NHC) issued a hurricane warning, indicating that some evacuees in this region had also decided to leave prior to an official announcement. This may have been due in part to the fact that the NHC had also declared a hurricane watch the previous night, and also because authorities in the affected areas issued their own warnings <ref type="bibr">(Lindell et al. 2005)</ref>. <ref type="bibr">Fu and Wilmot's (2004)</ref> logit model for household evacuation decisionmaking was created from data from Hurricane Andrew in 1992. Consistent with the above discussion, they found that increased risk levels (for example, living in a flood-prone area versus not) raise the likelihood of evacuation, and that warning announcements tend to hasten evacuation. The model also showed a strong preference for evacuation during daylight hours, consistent with many other studies, e.g., <ref type="bibr">Baker (1991)</ref>, <ref type="bibr">Dow and</ref><ref type="bibr">Cutter (2002), and</ref><ref type="bibr">Lindell et al. (2005)</ref>.</p><p>Hurricane Irma provides an opportunity to evaluate how travel time estimates fluctuated during different time periods. The travel times are examined in the context of available announcement information, hurricane arrival times, and power outages to see if associations can be discerned.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Method</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Data Acquisition and Selection of Origin-Destination Pairs</head><p>Evacuations are often characterized by higher than usual traffic volumes and related travel times. Evacuation periods therefore may be able to be inferred by examining travel times and finding increased travel time intervals that correspond to the onset of an evacuation-causing event. The likelihood of an identified period being attributable to evacuation behavior increases when the period features travel times that are significantly higher than those during normal peak hours.</p><p>The researchers used Google's Distance Matrix API to record travel time estimates along routes in Florida, Georgia, and South Carolina that lead inland and north, away from the threatened coastal areas. Florida was anticipated to be the primary impact area for the hurricane, and the Carolinas would potentially be subject to at least storm surge. Georgia can be an evacuation destination for Florida residents.</p><p>Data recording began at 11:06 p.m. on September 5, 2017, and estimates were gathered at roughly fifteen-minute intervals. When researchers recognized the potential scope and force of Irma, more origin-destination pairs were added to the list. This expanded collection effort began at approximately 11:45 p.m. on September 6th. Each data group contains a set of routes that were assigned to the same collection routine in the same general area; all routes within a given group therefore have the same times assigned to their readings.</p><p>In assessing the data, researchers examined longer journeys in different parts of the study area (Figure <ref type="figure">1</ref>) to obtain a broad picture of the evacuation across the impacted region, and particularly in Florida. The travel time estimates for the selected pairs of locations were then plotted against time of day. The graphs illustrate how traffic patterns evolved during Irma's approach and landfall, and for a few weeks thereafter (data collection stopped on October 2). Evacuation windows were approximated based on the knowledge that statewide warnings were issued as early as September 5. As discussed above, previous studies demonstrate that people in hurricane-prone areas may respond to official announcements fairly quickly, and also that they are often prepared to take action based on their own assessments beforehand.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>INSERT FIGURE 1 APPROXIMATELY HERE</head><p>The routes shown in Figure <ref type="figure">1</ref> are represented as straight lines because the exact routes taken by drivers cannot be determined from the data sets. The only information is the origin-destination pair. Numbers in the pairs refer to major roads; as shown in Figure <ref type="figure">1</ref>, N75-275 is close to Tampa-St. Petersburg, 10_19 is just east of Tallahassee, and 95_4 is beside Daytona.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Adjusting Travel Time Estimates</head><p>Because evacuations are not typical events, it is possible that the time estimated for a longer trip at a given departure time is not what was experienced during the evacuation. Some refinement of the data may yield a better picture of travel times that were experienced by Irma evacuees.</p><p>A preliminary review of the raw data revealed situations where the travel times reported for two or three adjacent time entries varied tremendously. For example, if a vehicle departed from Orlando for Columbus on September 8 at 15:49, its estimated travel time was 410 minutes. If the vehicle left 15 minutes later, the journey was estimated to take 367 minutes. This 43-minute fluctuation suggests that the raw data may not be an accurate reflection of experienced travel times, especially on the longer routes. Thus, adjusted travel time estimates were developed based on the strong, simplifying assumption that each vehicle on a route experienced the travel time that applied to each 15-minute interval during which it was on the roadway. Using the previous example to demonstrate, a vehicle that started from Orlando at 15:49 on September 8 would initially travel at a speed based on 410.05 minutes of estimated road time for the first interval of its journey to Columbus. Then, at the next reading at 16:04, the vehicle's speed would increase based on an overall travel time of 366.53 minutes. The speed changes would continue at each interval until the vehicle finished its journey. For this particular case, the adjusted estimated travel times were 373.91 minutes for vehicles that started at 15:49, and 371.92 minutes for vehicles that started 15 minutes later. This is a much smaller fluctuation. Determination of these adjusted travel time estimates began with estimating the distance traveled during each interval. The total distance traveled was not known with certainty for each pair of locations, since the actual route corresponding to the estimate was not recorded. Distances between pairs were selected based on recommended routes shown on Google Maps (determined in December 2017). The selected total distance (D, in miles) was used to calculate the distance traveled during each interval based on each raw total travel time (equation 1):</p><p>where d j,j+1 is the distance traveled during an interval between two readings j and j+1 in miles, R j is the raw travel time corresponding to reading j, t j,j+1 is the duration of an interval between readings j and j+1 in minutes, and j is the record number of the observation.</p><p>At this point in the calculations, the sums of the interval distances were checked for completed journeys. The minimum number of intervals that had one or more results that sum to at least the total mileage for the journey was chosen as the starting point for deriving adjusted travel time estimates, since this was the threshold within the dataset at which vehicles began completing the journey. The summed travel times were not accurate though, because a given vehicle finished its journey at some point during the final interval that it was on the road. It was therefore necessary to adjust the summed times based on the rate of travel during the last interval (equation 2):</p><p>where m j is the amount of extra distance in a completed trip distance sum assigned to record j (miles),</p><p>x is the number of intervals in a completed trip set, and all other terms are as previously defined.</p><p>The travel times for the extra distances are based on equation (3), and these values can then be subtracted from their associated interval sums to yield the desired adjusted travel time estimates (equation 4):</p><p>where c j is the number of minutes to be subtracted from a sum of intervals for a completed trip as in equation ( <ref type="formula">4</ref>) and other terms are as previously defined.</p><p>where T j is the adjusted travel time estimate in minutes for record j.</p><p>This computational approach assumes that the conditions on any particular route were uniform along the length of the route for each time interval, based on the raw travel times given.</p><p>After the adjusted travel time estimates were calculated and graphs were produced, basic comparative calculations were carried out. These results include ranges and range differences; differences between low-end/high-end raw travel times and their respective corresponding adjusted travel time estimates; and differences between the highest and lowest adjusted travel time estimates. These figures are accompanied by estimated start and end times for each location pair (where possible) and the shortest adjusted travel time estimates for daylight departures.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Travel Times and Events</head><p>Because there were major announcements that predated the data collection start times, the timings and potential effect(s) of those announcements cannot be analyzed directly in this paper. The residents of the Florida Keys in particular were likely sensitive to the approach of Irma, given what <ref type="bibr">Dash and Morrow (2001)</ref> found for that group over a decade ago. Based on the findings of <ref type="bibr">Lindell et al. (2005)</ref> and <ref type="bibr">Dow and Cutter (2002)</ref>, there is a chance that the largest part of the Keys evacuation happened early on September 5, the day after the first major hurricane watch notice was posted (NWS Key West 2017c). Similar evacuation peaks were observed the day after the NHC issued a Hurricane Watch for Hurricanes Rita <ref type="bibr">(Huang et al, 2016)</ref> and Ike <ref type="bibr">(Huang et al., 2012)</ref>. This part of the evacuation would have taken place almost a full day prior to the earliest data reading in this study, and thus it is not reflected in the data. However, it was possible that some of the Keys traffic appeared later in other states and/or the northern part of Florida during the sampling windows of this study.</p><p>For each origin-destination pair, two graphs were developed: a graph showing travel times for the recording period from September 6 to September 30 (only a few of these are depicted here to save space, but the others are available from the authors upon request) and an annotated graph showing travel times proximate to Irma (September 6-13 where possible; September 7-13 otherwise). The annotations give the times of various hurricane warning and evacuation announcements and the first and second landfall times. The first landfall refers to the one at Cudjoe Key, and the second landfall refers to the one at Marco Island <ref type="bibr">(Stein et al. 2017)</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Key Largo to Belle Glade</head><p>The Key Largo-Belle Glade pair represents a primary evacuation corridor out of the Keys. Due to limited connectivity between the Keys and the mainland, the Keys should be evacuated well in advance of the arrival of tropical storm force wind and hurricane landfall. Both Figure <ref type="figure">2A</ref> and Figure <ref type="figure">2B</ref> show how the adjusted travel time estimates differ from the recorded ones: the adjusted times have a smaller range (lower high values and higher low values). The adjusted travel time estimate curve is shifted slightly to the left of the original because of the way the adjusted estimates are calculated (as described in section 3.2). This general relationship between the adjusted and recorded travel times is consistent for all of the data sets due to the calculation method employed. Gov. Scott said shortly after Irma passed that he wanted the Keys reopened by October 1st. Although some Keys residents felt this goal was too ambitious, they were aware that without a formal barrier, tourists would still start returning as soon as they had the opportunity. As of September 30th, this was indeed the case <ref type="bibr">(Contorno 2017)</ref>, and the increased traffic heading out of the Keys could indicate heightened activity on the roadways in general later in the month (Figure <ref type="figure">2A</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>INSERT FIGURE 2 APPROXIMATELY HERE</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Port St. Lucie to Sebring</head><p>Port St. Lucie is located to the north of Miami on the east coast of Florida. As shown in Figure <ref type="figure">2C</ref>, there is a period at the beginning of the analysis that has inflated travel times that do not occur again during the month. The higher travel times last for a little more than two days from the morning of September 6 to the afternoon of the As shown in Figure <ref type="figure">2D</ref>, even though the evacuation appears to have begun in the early morning on the 6th, noticeably high travel times are present in the evening and even close to midnight on the 7th. Within the main evacuation period (September 6 and 7), the difference between the longest and shortest travel time is nearly 12 minutes (see Table <ref type="table">2</ref>). Although travel speeds at night tend to be lower than during the day, the values for September 6 and 7 exceed those of corresponding hours on other days in September, as shown in Figure <ref type="figure">2C</ref> (e.g., travel time at 12:00am on September 7 is approximately 7% higher than that of September 14).</p><p>This suggests the presence of an evacuation wave that chose to travel on roads in the area during the night, something that goes against the general daylight evacuation preference highlighted by <ref type="bibr">Baker (1991)</ref> and many others. The nighttime travel may have been somewhat attributable to school closures on the 7th and 8th that were announced on the 5th (Atterbury 2017). The elevated travel times that persisted the following night might have had the first mandatory evacuation notice as a contributing factor. Although night is not the preferred time to travel, Lindell et al.</p><p>(2019) note that people will do so if necessary, such as for Hurricanes Eloise <ref type="bibr">(Baker et al. 1976</ref>), Elena <ref type="bibr">(Baker 1986)</ref>, and Opal (USACE Philadelphia District 1996).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Fort Pierce to Turnpike Orlando</head><p>Fort Pierce is just north of Port St. Lucie on the east coast, and Orlando is inland to the northwest. Like Port St. Lucie to Sebring, this route had elevated travel times at the beginning of the analysis window (September 7 and 8) that did not appear for the rest of the month. This pattern suggests this is a probable evacuation route, and a heavily impacted one. The raw travel times during the evacuation window approach 160 minutes (see Table <ref type="table">1</ref>), and even the adjusted values exceed 150 minutes (see Tables <ref type="table">1</ref> and<ref type="table">2</ref>) (approximately 80% higher than the typical travel times for the route post-evacuation -between 80 and 90 minutes). These highest travel times were observed close to the evacuation announcement at 5:30pm on September 7 that indicated the evacuation orders would be in effect at 3:00pm on the 8 th . The main evacuation period appeared to end more than 40 hours prior to the arrival of tropical storm force winds at Fort Pierce. Like Port St. Lucie, Fort Pierce's evacuation may have been affected by the regional school closure announcement <ref type="bibr">(Atterbury 2017)</ref>, leading to departures that preceded the mandatory evacuation announcements. The timing of the official evacuation the next day coincided with what appears to be the tail end of the evacuation period (Figure <ref type="figure">3A</ref>). While there was evacuation-type behavior throughout the 7th, it is not possible to tell if the evacuation began earlier.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.4">Orlando to Columbus</head><p>Orlando to Columbus is a long trip that has Interstate 75 as a prominent possible component. I-75 is an interstate highway that connects Atlanta with major cities in central Florida. As with Fort Pierce to Turnpike Orlando, the travel time estimates suggest an evacuation period that may have begun before the 7th. The peak points on the evacuation days (around mid-day) show a strong preference for daylight travel, as travel times increased into the evening before declining to a local minimum around midnight (Figure <ref type="figure">3B</ref>). The peak adjusted travel time estimate occurred at approximately 2:30pm on the 7 th and was 16% greater than the corresponding adjusted travel time estimate on the 14 th . The evacuation period ended on the 8 th , nearly two full days before the arrival of tropical storm force wind in Orlando.</p><p>Notably, much of the evacuation traffic preceded the timing of the local jurisdiction's notice for mobile home evacuation. Because this pair includes a major roadway in central Florida, the evacuation travel times may have been primarily</p><p>attributable to through traffic from locations to the south and the east.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>INSERT FIGURE 3 APPROXIMATELY HERE</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.5">Daytona to Columbus</head><p>As with Orlando-Columbus, Daytona-Columbus had at least two days of elevated travel times, indicating probable evacuation traffic (Figure <ref type="figure">3C</ref>). The highest adjusted travel time estimate occurred near noon on September 7 and was approximately 7%</p><p>greater than the corresponding time on September 21 (the 14 th was not used for comparison due to power outages remaining). The pattern of the evacuation is also similar to Orlando-Columbus, with the evacuation possibly starting before the 7 th and ceasing on the 8 th , a preference for daylight travel, much of the evacuation appearing to occur before the local jurisdiction's notice for mobile home evacuation (and beachside areas), and most of the evacuation appearing to end two days before the arrival of tropical storm force winds.</p><p>Just after tropical storm winds arrived in Daytona on the evening of the tenth, power outages began to manifest and escalate. On the 11 th and 12 th , 80% of the customers in the area were without power (Figure <ref type="figure">3C</ref>). The heavy loss of power coincided with another period of slightly elevated travel times, perhaps indicating another evacuation wave that was catalyzed by the lack of power. People traveling from Daytona to Columbus during the evacuation had the typical preference for daylight travel, even during the possible second evacuation period.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.6">95-4 to S95-Jacksonville</head><p>This journey originates in the Daytona area as well. The data shows the same basic evacuation pattern as the two preceding origin-destination pairs (Figure <ref type="figure">3D</ref>). The evacuation period covers the 7 th and the 8 th , with much of the evacuation appearing to precede the official evacuation order effective period by 1-33 hours and the arrival of tropical storm force winds by approximately 48-81 hours. The data suggest a preference for daylight travel with the highest adjusted travel time estimate occurring near noon on September 7 (approximately 57% longer than the corresponding time on September 14). The flat period before the travel times started to rise on the 7 th makes it difficult to determine if the evacuation carried over from the previous day.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.7">N75-275 to 10-19</head><p>N75-275 to 10-19 starts in the greater Tampa area and goes into the panhandle of Florida, east of Tallahassee. This pair shows three days of evacuations, approximately centered around the evacuation order that was issued for Zone A in Tampa (comprised of coastline areas; Office of Emergency Management 2017) in the middle of September 8 (Figure <ref type="figure">4A</ref>). The end of the third day of this evacuation appeared to precede the arrival of high winds by about 24 hours. The data follows the overall trend of featuring a pattern that implies a preference for daylight travel (all three days, as in Figure <ref type="figure">4A</ref>). While there is no way to know from the data if the evacuation began on the 6 th or earlier, it would be notable if it did because that would extend the evacuation period to around four days.</p><p>Parr and Acevedo (2019) indicated that, based on detector data, the Tampa region experienced an initial gain in the number of vehicles (potentially due to being an evacuation destination before Hurricane Irma changed paths). However, an evacuation of the Tampa area appeared to start approximately two days before the first landfall <ref type="bibr">(Parr and Acevedo 2019)</ref>. This corresponds to the second peak in travel times seen in Figure <ref type="figure">4A</ref>. The highest adjusted evacuation time estimate on September 8 occurred near noon and was approximately 28% higher than the corresponding time on September 22 (the 15 th was not used for comparison due to the power outage).</p><p>The outage data (Figure <ref type="figure">4A</ref>) shows a similar scenario to the one in Figure <ref type="figure">3C</ref>,</p><p>where the onset of tropical storm-force winds portended power loss. In the N75-275 area, power loss was as high as 61% before recovering to about 40% on the 13th.</p><p>Note that there is not a discernable secondary evacuation that could be ascribed to the power problems, possibly because this is a road location and not a specific municipality.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>INSERT FIGURE 4 APPROXIMATELY HERE</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.8">Jacksonville Beach to Lake City</head><p>Jacksonville Beach-Lake City does not appear to have had a typical evacuation, since the travel times in the hurricane period were very similar to the ones that were reported for the post-hurricane period later in the month (e.g., September 18-23; 26-30 not shown here). Some variation in travel time exists throughout the day on September 6-8 that drops on September 9 and 10. However, this area did experience elevated travel times beginning just before the arrival of tropical storm force winds late on September 10 and becoming more prominent on the 11 th (Figure <ref type="figure">4B</ref>). Similar to Figures <ref type="figure">3B</ref> and<ref type="figure">3C</ref>, 4B shows increased travel times after Irma's arrival. While three FDOT detectors in Duval county indicated obviously lower traffic counts in the Jacksonville area on the 11 th compared to the 12 th , these counts were in the multiple hundreds around 2pm. The elevated travel time period on the 11 th followed the arrival of tropical storm winds the previous night. This could have been partially due to flooding in the Jacksonville area (News4Jax staff 2017).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.9">Jacksonville to 95-Savannah</head><p>Figure <ref type="figure">4C</ref> for Jacksonville-Savannah shows probable evacuation traffic, again on the 7 th and 8 th with some evidence of preference for daylight travel. Though the travel times are not drastically elevated, they are still consistently above the norm shown in the post-hurricane weeks. The 8 th , in particular, has a couple of recorded travel times that are outliers; these were "smoothed" by the adjusted travel time estimate calculation process. The highest adjusted travel time estimate occurred near noon (more than 48 hours before the arrival of tropical storm force winds) and was 18% greater than that for the corresponding time on the 15 th . These highest travel times on the 8 th occurred after the evacuation announcement, while the peak on the 7 th preceded the announcement.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.10">10-19 to Montgomery</head><p>10-19 to Montgomery, which starts outside of Tallahassee in the Florida panhandle, had the peak of its evacuation on the 8 th , more than 24 hours before the voluntary evacuation notice and more than two days before power losses (see Figure <ref type="figure">4D</ref>).</p><p>Evacuees may know well in advance of official evacuation orders that they are going to do so. The highest adjusted travel time estimate occurred near 6pm on the 8 th and was 19% greater than that of the 22 nd . The travel times between this pair of locations could also be due to other evacuation traffic coming from the south of Florida, but the absence of elevated travel times after the announcements suggests either there were few evacuations in response, or that the roads were able to easily accommodate the volume that was generated.</p><p>This location did not have powerful enough sustained wind speed to make it easy to identify the arrival of tropical storm force wind (Weather Underground 2018).</p><p>However, it is likely that strong winds are associated with power losses (see the power outage ratio line in Figure <ref type="figure">4D</ref>). This area started to lose power around midnight on the 11 th , and this outage continued to expand until, by the evening of the 11 th , approximately 90% of customers were without power. Since 10-19 refers to a road location rather than a municipality, the outage severity probably did not trigger another discernible evacuation; people could have been driving through on the way to other destinations.</p><p>Though this path follows on directly from the terminus of the N75-275-to-10-19 route, it does not have a similar evacuation profile. Like the N75-275 route, there is evacuation activity on the 8 th ; however, unlike N75-275, there is comparatively little travel time inflation on the 7 th and 9 th (Figures <ref type="figure">4A</ref> and<ref type="figure">4D</ref>).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.11">Charleston city center to Florence, SC</head><p>Unlike Florida, South Carolina employed contraflow in select locations to expand evacuation capacity. It is possible that drivers traveling from Charleston to Florence were able to benefit from contraflow, as it was implemented on Interstate 26 leading out of Charleston <ref type="bibr">(Haire 2017)</ref>. The somewhat balanced travel times throughout the month shown in Figure <ref type="figure">5A</ref> suggest that contraflow was a success or, possibly, that contraflow was unnecessary. However, as is visible in Figure <ref type="figure">5B</ref>, there were still discernible higher travel times during the evacuation period on September 7 and 8, approximately 16 and 30 hours before implementation of the official evacuation notice and 66 and 90 hours before the arrival of tropical storm force wind. The highest adjusted travel time estimate occurred at approximately 6pm on the 8 th and was approximately 22% greater than that for the corresponding time on the 15 th . The evacuation appeared to begin right after the announcement that there would be an official evacuation start time and contraflow measures on the interstate. The data implies that a late-day evacuation took place, perhaps partially in response to the announcement, and then a larger one transpired the next day for the population segment that either had to wait or had a strong daytime evacuation preference.</p><p>The Charleston situation stands out because evacuations in Florida largely seem to have commenced well before official evacuation start times. In contrast, the evacuation in Charleston appears to have been at least in part in response to the official announcement on September 7, approximately four days before the arrival of tropical storm force winds. Florida notices tended to be issued closer to the arrival of tropical storm force winds.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>INSERT FIGURE 5 APPROXIMATELY HERE</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.12">Calculated Differences Between Recorded and Adjusted Travel Times</head><p>In Table <ref type="table">1</ref>, the adjusted values provide travel times over a smaller range in all cases.</p><p>The differences between the recorded and adjusted travel time estimate ranges are often substantial. Adjusted travel time estimates are important because people may choose to evacuate based on a lower travel time estimate, only to be confronted by a much more daunting figure 15 minutes later while enroute. The reality of their travel situation would more likely lie somewhere in the middle, and this would be shown by adjusted travel time estimates.</p><p>For every high and low value in the recorded set, the corresponding adjusted travel time estimate (the value in the same record slot, not the overall high/low experienced time) is a more conservative travel time estimate (Table <ref type="table">1</ref>). The major differences are shown with the recorded high-end values. The recorded high-end values tend to be more extreme than the low-end values. As a result, the differences between the highest values and their associated adjusted travel time estimates tend to be larger by comparison. (Note: The calculations for the differences between the recorded and adjusted travel time estimates were carried out using only data from the evacuation windows defined in Table <ref type="table">2</ref>.) As can be seen in Table <ref type="table">2</ref>, the majority of the evacuations started after midnight and before 6 a.m. While the early morning hours are devoid of sunlight, evacuations likely started at these times because drivers knew they would be on the road during daylight in the event of a large delay. The notable exception in terms of timing was Jacksonville Beach, a coastline community in the northeastern part of Florida. These increased travel times are possibly a reaction to flooding and/or power outages which are post-impact environmental cues <ref type="bibr">(Lindell 2018;</ref><ref type="bibr">Lindell and Perry 2012)</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.13">High and Low Adjusted Evacuation Travel Time Estimates</head><p>The most common theme amongst the estimated departure times (Table <ref type="table">2</ref>) is that the best time to leave was usually between midnight and dawn. This is logical considering the well-established preference for daytime evacuation: on a given day, there are simply fewer cars on the road during the early hours of the morning, and thus lower travel times. The question for anyone evacuating in a personal vehicle would be whether he/she values time saved over evacuating at a preferred hour. In it would not seem that the extra time spent on the road would be a huge deterrent in these cases. Unsurprisingly, the best post-sunrise time to leave was usually right after the sun rose, because evacuations tend to build from the lowest travel times early in the morning through the day.  (Note on Tables <ref type="table">1</ref> and<ref type="table">2</ref>: The specific evacuation end times were taken from the peak region of the last perceivable evacuation wave on each graph, since there is no good way to define a moment for the "end" of a given evacuation on the downside of its last interval. By choosing the last peak instead of a point later in time, the most and least favorable leaving times are kept within a window in which evacuation traffic can be safely assumed to have still been entering the road segments.)</p><p>5 Discussion of Results and Conclusions</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1">Summary of Observations</head><p>The Irma evacuation origin-destination pairs in this analysis conformed to some of the commonly observed features of hurricane evacuations. Consistent with <ref type="bibr">Baker (1991)</ref>, <ref type="bibr">Dow and</ref><ref type="bibr">Cutter (2002), and</ref><ref type="bibr">Lindell et al. (2005)</ref>, evacuees often demonstrated a preference for daylight travel. This preference was less pronounced in at least one case (Port St. Lucie to Sebring), but the overall trend in the data reinforces this preference.</p><p>Many evacuations in this analysis seemed to finish before official start times were announced. This appears to support the finding by <ref type="bibr">Lindell et al. (2005)</ref> that people start to prepare and make their decisions to evacuate when they have significant information about the probable approach of a hurricane (through news services, friends, online forums, etc.); official evacuation announcements then only serve as confirmations. Because of the time period of the data recording, the early Irma statements issued by Florida Governor Scott could not be matched with travel times in this paper. However, Governor Scott did make a statewide announcement about school closure in Florida on the evening of September 7 <ref type="bibr">(Postal 2017</ref>), which overlaps with the evacuation activity apparent in the southern part of Florida on the same day. Based on what <ref type="bibr">Dash and Morrow (2001)</ref> found for residents of the Keys specifically, it is likely that many people knew well in advance of even Governor Scott's notices that they were going to evacuate inland for at least a few days.</p><p>In this study, it is not possible to definitively state the starting times of all of the evacuations. However, due to the preference for daylight travel, it is likely that any evacuation traffic that preceded the data collection would have followed a similar pattern (high travel times in the middle of the day, with the lowest times generally occurring just before and just after midnight). Considering this finding, someone who wants to avoid delays could leave well before dawn on the chosen departure day. On the planning side, finding a way to better distribute traffic over a 24-hour period would perhaps help even out travel times in future events, and reduce the travel time for those who have to evacuate during daylight hours exclusively (such as people with poor night vision).</p><p>In Figures <ref type="figure">3C</ref> and<ref type="figure">4A</ref>, a significant power outage seems to coincide with late evacuation behavior. Power outages leading to later evacuation surges is an issue that should be more thoroughly investigated, if only so officials can prepare for sudden evacuations under compromised circumstances. While the preference for daytime evacuation seems to hold under power outage circumstances, it does not seem to be as reliable (Figure <ref type="figure">3C</ref> has a local travel time peak close to midnight on the 11th). This may make sense, because if one already has no light or cooling, the preference for staying at night might be diminished. This implies that evacuations stemming from power loss may happen suddenly regardless of hour, so disaster officials have to be prepared for egress roads to be accessible and navigable for large volumes of traffic at any time of day.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2">Conclusions</head><p>This study investigated the evacuation travel time patterns for selected locations for Hurricane Irma. Five questions were central to the research:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1.">How do the estimated travel times in the data match up with travel times that have been adjusted to better reflect driver experiences?</head><p>The adjusted travel times have smaller estimate ranges than those recorded from the Google API, and this is a function of their more moderate overall values. This is to be expected. Since the adjusted values "look ahead" in the recorded data to arrive at their results, they shift the overall travel time curves marginally to the left on the graphs.</p><p>The recorded travel time estimates may have reduced accuracy for longer routes because unexpected conditions can arise (as acknowledged when Google</p><p>Maps provides a travel time). Using the travel time adjustment method in this paper thus provides a way to create a more reasonable picture of the long-route experienced travel times. This can be helpful to residents and officials alike during evacuations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2.">When did evacuation noticeably begin and end in different areas, based on the travel time data?</head><p>In most cases, evacuations began in the early morning before dawn. The only evacuations appearing to start after dawn were on the Jacksonville-Savannah (Figure <ref type="figure">4C</ref>) and Charleston-Florence (Figure <ref type="figure">5B</ref>) routes. The Jacksonville Beach-Lake City evacuation began in the late afternoon (Figure <ref type="figure">4B</ref>), and that was perhaps due to flooding and/or power outages. This general pattern somewhat reinforces the daytime travel preference that has been observed in many previous evacuation studies. The occurrence of an evacuation that started well into the afternoon implies that there are other events that can cause more spontaneous evacuations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.">How do the evacuations match up with official evacuation notices?</head><p>Evacuations were typically already underway by the time official evacuation notices were issued or the evacuations were officially supposed to begin; in addition, most evacuations had already largely ended by the time evacuation announcements were officially made. Though Charleston residents had sufficient warning, they waited until later to leave.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.">Do power outages have any discernible association with possible evacuation activity?</head><p>There is some potential evidence of power outages being associated with evacuations; hence, they might be a causative factor. The circumstances surrounding these kinds of quasi-spontaneous evacuations and the means of safely facilitating them is an area for further exploration. In particular, is there heightened risk during an evacuation attributable to a power outage? And if so, how can this risk be mitigated efficiently?</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.">What were the best and worst times for evacuees to leave their respective areas prior to Irma?</head><p>The best times to leave were early in the morning before dawn, on a given day, in all but one pre-Irma case featured in this analysis. Only Jacksonville-Savannah and Fort Pierce-Turnpike Orlando featured advantageous departure times that occurred after sunrise in the morning. The worst time to leave before Irma was often between 11am and 1pm; in three cases, it was after 6pm (Table <ref type="table">2</ref>). This timing is problematic for people who have strict 9-to-5 work schedules or have other responsibilities prior to a hurricane, because unless they can alter their usual schedules, they will experience heavier afternoon/evening evacuation traffic.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.3">Limitations</head><p>This study used a dataset not typically used to identify evacuation periods. More traditional data types are based on surveys and traffic counts/speeds available from detectors. This initial study faced several limitations that can be addressed in future studies. First, the data collection for this study began potentially after some early evacuees departed, particularly from the Florida Keys. Starting the collection earlier will capture the whole evacuation period. Second, the travel time adjustment process used a distance based on recommended routes, which may not match with the travel times. Future studies should collect both the route distance and the travel time simultaneously. Third, the travel times were based on the shortest travel times, which may not align with evacuee route preferences. Evacuees tend to use Interstates regardless of whether an alternate route's travel time is shorter <ref type="bibr">(Dow and Cutter 2002;</ref><ref type="bibr">Lindell et al. 2019)</ref>. Future data collection efforts should obtain data for multiple routes. Fourth, the adjustment process used a strong assumption that each vehicle on a route experienced the travel time that applied to each 15-minute interval during which it was on the roadway. This assumption could be relaxed in the future by creating smaller route segments as well as alternative data generation systems (e.g., individual vehicle tracking).</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.4">Future Directions</head><p>In this study, adjusting the instantaneous travel times smooths very high and low travel time values (especially high ones). This narrows the range of estimated travel times for a given route, and it shifts the travel time curve slightly to the left as a byproduct of the method. The next logical step is to try to verify the adjusted travel times by obtaining travel time data recorded during a pre-event evacuation on specific routes. These recorded times could also be used to compare travel speeds after dark with those during daylight for corresponding traffic counts to determine how much travel speed is affected by lighting conditions during an evacuation.</p><p>This study also revealed limited information about the phenomenon of an evacuation caused by flooding and/or power loss. An approach to predicting the occurrence of one of these comparatively spontaneous evacuations might include information about how much experience a given community has with hurricanes, as well as its likelihood of being hit with a strong storm and susceptibility to water inundation. The duration of tropical storm force wind in an area could also be explored for a relationship with travel, particularly travel occurring after the wind's arrival with and without associated power losses. Hurricane Irma was significantly weakened and well inland by the time it affected communities like Jacksonville and Charleston with heavy rains and storm surge. The degree to which the Jacksonville area in particular could have mitigated roadway congestion after the storm by effecting a preemptive evacuation would make for interesting further inquiry.</p><p>The research findings have reinforced two of the established notions about evacuation behavior: daytime preference and living in risk-prone areas leading to advanced evacuation planning. Other features of this study that require further investigation are power outage evacuations and the question of why some households begin their evacuations before state and local officials issue evacuation notices. The relationship between inferred evacuation travel and evacuation notices in this study seem to contradict <ref type="bibr">Baker's (2000)</ref> conclusion that typically less than 15% of evacuees depart before evacuation notices are issued. These conflicting results could be due to changes in evacuation behavior over two decades or the difference in research methods. The difference in results warrants additional exploration and the study of evacuation departure times, in general, still has room for additional research <ref type="bibr">(Lindell et al. 2019)</ref>. announcements and events, 9/7 through 9/13 of 2017 (3B); Daytona to Columbus travel times with announcements, events, and portion of power out, 9/7 through 9/13 of 2017 (3C); 95-4 to S95-Jacksonville travel times with announcements and events, 9/7 through 9/13 (3D) Fig. <ref type="figure">4</ref>: N75-275 to 10-19 travel times with announcements, events, and portion of power out, 9/7 through 9/13 of 2017 (4A); Jacksonville Beach to Lake City travel times with announcements and events, 9/7 through 9/13 of 2017 (4B); Jacksonville to 95-Savannah travel times with announcements and events, 9/7 through 9/13 of 2017 (4C); 10-19 to Montgomery travel times with announcements, events, and portion of power out, 9/7 to 9/13 of 2017 (4D) Charleston to Florence travel times with announcements and events, 9/7 through 9/13 of 2017 (5B)</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Figure Captions</head></div><note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1004" xml:id="foot_0"><p/></note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1008" xml:id="foot_1"><p/></note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1012" xml:id="foot_2"><p/></note>
		</body>
		</text>
</TEI>
