Many public safety officials (e.g., emergency managers and first responders) use weather-radar data to inform many life-saving decisions, such as sounding outdoor warning sirens and directing storm spotters. Therefore, to include this important user group in ongoing radar applications research, a knowledge coproduction framework is used to interact with, learn from, and provide information to public safety officials. From these interactions, it became clear that radar-based products that estimate a tornado’s location, intensity, or both could be valuable to public safety officials. Therefore, a survey was conducted and a focus group formed to 1) collect feedback on several of these products currently under development, 2) identify potential decisions that could be made with these products, and 3) examine the impact of radar update time on product usefulness. An analysis of the survey and focus group responses revealed that public safety officials preferred simple interactive products provided to them using multiple communication methods. Once received, any product that could clearly communicate where a tornado may have occurred would likely help public safety officials focus search and rescue efforts in the immediate aftermath of a tornado. Additionally, public safety officials preferred products created using rapid-update data (1–2-min volumetric updates) over conventional-update data (4–5-min volumetric updates) because it provided them with more complete information.
Many public safety officials (e.g., emergency managers and first responders) use weather-radar data to support decisions ranging from directing storm spotters to coordinating search and rescue efforts (e.g., Morris et al. 2002; Baumgart et al. 2008; Weaver et al. 2014). In a national survey of approximately 900 public safety officials working in the United States, Weaver et al. (2014) found that 30.3% of respondents would activate their emergency-response system based solely on Doppler radar evidence of a tornado. This percentage increased as more data (e.g., law enforcement reports) became available and the storm got closer to the respondent’s area of responsibility. Research in Oklahoma has provided additional insight into how public safety officials access and use radar data. League et al. (2010) analyzed results from a survey distributed to 62 Oklahoma public safety officials and found that 86% of respondents used radar data every few minutes during severe weather events. Respondents reported accessing radar data most commonly through the National Weather Service (NWS) website and the Oklahoma First-Response Information Resource System using Telecommunications (OK-FIRST; Morris et al. 2002) that has provided radar training to over 1300 public safety officials since it began in 1996.
To determine how public safety officials use radar data, Baumgart et al. (2008) presented 11 Oklahoma public safety officials with a questionnaire about radar use and decisions typically made during severe weather events. The participants then interacted with radar data in a simulated real-time case and vocalized their thought process while working the case. After analyzing the data, researchers determined that public safety official use of radar data consisted primarily of looking at low-level reflectivity and velocity data to assess storm location, movement, size, and intensity. This information then supported decisions such as activating outdoor warning sirens, evacuating a local airport, and routing search and rescue teams around dangerous storms (e.g., Morris et al. 2002; Baumgart et al. 2008; League et al. 2010).
Since public safety officials are an important user of radar data in Oklahoma and across the United States, it is crucial to include them in the development of new weather radar technology and products. One example of ongoing collaborations includes researchers working with NWS forecasters and public safety officials to evaluate probabilistic hazard information (e.g., Stumpf et al. 2008; Karstens et al. 2015) in an experiment that aims to simulate the real-time working environment of an integrated warning team (LaDue et al. 2016). Another collaboration process, called coproduction of knowledge (e.g., Jasanoff and Wynne 1998; Lemos and Morehouse 2005; Meadow et al. 2015), provides a framework for expanding ongoing collaborations between meteorologists working at the National Weather Center and public safety officials to include radar data applications. This process emphasizes collaboration between scientists and stakeholders through relationship building and two-way communication to produce information that is understandable and easily accessible by decision-makers (e.g., Jasanoff and Wynne 1998; Meadow et al. 2015). Coproduction studies can involve different levels of stakeholder engagement with higher levels more likely to produce usable information because stakeholders act as partners during the research process. The four primary modes of engagement in order of stakeholder involvement are 1) contractual, 2) consultative, 3) collaborative, and 4) collegial (Biggs 1989; Meadow et al. 2015).
To further engage public safety officials in the development of new radar technology and radar-based products, we adopted the collaborative mode of engagement, which emphasizes building long-term relationships and continuous stakeholder involvement (e.g., Meadow et al. 2015). Therefore, two-way relationships were built with members of the public safety official community by attending their monthly meetings, annual workshops, and conferences, as well as engaging in dozens of face-to-face conversations. This ongoing relationship building provided an opportunity to learn about the daily duties of public safety officials during days with severe weather, determine common uses of radar data, identify knowledge gaps and potential research needs based on stakeholder knowledge, and share information about ongoing weather-related research at the National Weather Center. During this first step of stakeholder engagement, multiple public safety officials mentioned a need for a product that could clearly indicate where a tornado had occurred. Knowing that development of these products had already begun, there was an immediate need to involve public safety officials in the ongoing development of products that estimate a tornado’s location, intensity, or both [hereafter referred to as tornado track estimation products; e.g., Manross et al. (2008); Snyder and Ryzhkov (2015); Karstens et al. (2016)]. Therefore, the purpose of this study was to ensure that public safety official’s ideas were considered by product developers by gathering information from public safety officials regarding their tornado track estimation product preferences and the decisions they might make with the support of these products.
To obtain this information, we leveraged the relationships built with many Oklahoma public safety officials to distribute a weather-radar survey using a snowball sampling technique (e.g., Biernacki and Waldorf 1981) in which each respondent is encouraged to send the survey link to fellow colleagues. A focus group was also conducted to address some limitations of the survey and collect more specific feedback from a subset of Oklahoma public safety officials. Questions posed to survey and focus group participants focused on three key topics of interest: 1) typical use of radar data on a day with severe weather, 2) respondents’ perceptions of five tornado track estimation products—two created manually and three created automatically—currently under development that could become operational in the future, and 3) examples of how these products could support decisions in the immediate aftermath of a tornado. This portion of our overarching study is more representative of the consultative mode of engagement (Biggs 1989; Meadow et al. 2015), in which stakeholders are involved at specific stages to inform and guide research efforts. However, the survey and focus group also further our overall collaborative research efforts because the provided responses will ultimately help researchers share understandable and easily accessible information and products with public safety officials.
This paper describes five tornado track estimation products (section 2) and the methods by which feedback was collected from public safety officials (section 3). Feedback collected via the survey and focus group is outlined in section 4 and then discussed within the context of applications to meteorological research (section 5).
2. Radar estimation of tornado track and intensity
The weather-radar survey and focus group activities presented public safety officials with five tornado track estimation products: 1) NWS track, 2) tornado track and intensity, 3) rotation track, 4) maximum Doppler velocity track, and 5) tornado debris signature (TDS). The first two aforementioned products are manually generated (Fig. 1) while the last three are automatically generated by algorithms (Fig. 2). All product examples included in the survey and focus group were created using a dual-polarization research Weather Surveillance Radar 1988-Doppler (WSR-88D) located in Norman, Oklahoma (KOUN). This radar can perform 90°-sector scans, which result in volumetric update times of less than 2 min, increasing the utility of the data it collects for evaluating tornado track estimation products. Each product is currently experimental, but preliminary versions of the NWS track and rotation track products are available for operational use (e.g., Miller et al. 2013).
Various radar limitations such as spatial resolution (e.g., Brown et al. 1978) and aspect ratio (e.g., Burgess et al. 1993) prevent most of the products discussed here from detecting the tornado itself. These products instead indicate tornado location and perhaps intensity based on features more readily detected by WSR-88D radars (e.g., mesocyclones and tornado vortex signatures), along with the aid of NWS forecaster input and spotter reports. In addition, radar detects features at beam height, not necessarily very near the ground where damage occurs (e.g., Speheger and Smith 2006). These factors limit product usefulness with increasing range, since a radar’s accuracy in depicting near-surface conditions decreases with increasing range (Fig. 3). Therefore, conditions at the surface could be different than what the products depict and should be applied with caution by users far (i.e., over about 100 km) from the nearest radar. In addition, the TDS product is only created when the radar beam (3-dB beamwidth) is below the melting layer and therefore may not be available to users far from the nearest radar.
a. NWS track
In 2012, the Norman NWS Forecast Office developed a manually generated product specifically designed for public safety officials. A tool allows forecasters to produce preliminary tornado damage paths by tracking the location of a tornadic velocity couplet in quasi real time. Using this tool, a forecaster can mark the position of a velocity couplet in the Advanced Weather Interactive Processing System (AWIPS) over time. These points are used to generate a Keyhole Markup Language (KML) file that shows an estimation of the tornado’s centerline track along with uncertainty bounds (Fig. 1a). The uncertainty bounds are based on ongoing research at the Norman NWS Forecast Office similar to that of Speheger and Smith (2006), in which radar-estimated tornado locations were compared to ground-surveyed locations for 240 tornadoes across the United States between 2009 and 2016. Analysis of the results (Fig. 3) shows that the uncertainty distance (i.e., distance between radar-estimated location and actual location) is about one-half of that shown in Speheger and Smith (2006) thanks to recent radar advancements such as superresolution data (e.g., Wood et al. 2001; Brown et al. 2002; Brown and Wood 2012) and improved filtering of side-lobe contamination (Piltz and Burgess 2009). This updated uncertainty distance provides the basis for the NWS track’s uncertainty bounds, which represent radar-based location uncertainty as a function of the velocity couplet’s distance from the radar. The centerline of the observed tornado lies within the uncertainty bounds 90% of the time.
The accuracy of the preliminary paths can be improved by the forecaster’s consideration of other data sources (e.g., environmental parameters, spotter reports, and information from local media), recognition of radar limitations (e.g., beam broadening), and past operational experience. While the paths are not produced for all velocity couplets, if a tornado is observed and significant impacts are anticipated, a forecaster can choose to use the tool. For example, the product was created shortly after the 20 May 2013 tornado that occurred in the Oklahoma City, Oklahoma, metropolitan area (e.g., Burgess et al. 2014) and was used by the Federal Emergency Management Agency to identify locations in need of resources (e.g., Karstens et al. 2016).
b. Tornado track and intensity
The authors generated a second manually created product that estimates a tornado’s location and intensity based on encouraging results from previous studies that found a relationship between low-level Doppler velocity observations and a tornado’s enhanced Fujita (EF) scale rating (e.g., Doswell et al. 2009; LaDue et al. 2012; Toth et al. 2013; Kingfield and LaDue 2015; Smith et al. 2015). Specifically, intensity estimates were determined using a velocity couplet’s rotational velocity and the conditional probability of tornado damage intensity presented in Smith et al. (2015). The product can likely be produced similarly to the NWS track in that an NWS forecaster could track the location of a tornadic velocity couplet and measure the couplet’s rotational velocity with time in AWIPS. The resulting product could contain a line showing the tornado’s approximate location that is color coded based on the intensity estimate (Fig. 1b). Though not included here, uncertainty bounds could likely be added similarly to the NWS track.
c. Rotation track
This automated product (Fig. 2a) was developed to aid NWS forecasters and emergency managers during postevent assessments (Manross et al. 2008). Radar data from the Multi-Radar Multi-Sensor system (e.g., Zhang et al. 2016) are used to produce a gridded product depicting the maximum values of azimuthal shear (i.e., rotational intensity) in the lowest 2 km accumulated over time (e.g., Manross et al. 2008; Karstens et al. 2016). The product has undergone improvements since its creation in 2007 including quality controlling reflectivity data to account for nonmeteorlogical echoes, applying a range correction algorithm to lessen the impacts of beam widening with increasing range, and eliminating relatively low background values of azimuthal shear to highlight the stronger values likely associated with mesocyclones (Miller et al. 2013). This product has been used by NWS forecast offices for damage survey planning and by the American Red Cross for disaster resource allocation (Manross et al. 2008; Miller et al. 2013). In this study, we used 0.5° elevation angle data from KOUN to create the rotation tracks.
d. Maximum Doppler velocity track
This automated product was developed by the authors for this study as a proof of concept to depict the scope (i.e., location, width, and magnitude) of strong winds associated with a tornado or other damaging thunderstorm winds (e.g., downbursts and rear-flank downdrafts). To produce the product, the 0.5° velocity field is used to calculate the maximum absolute radial velocity over a specified time period. Currently, the user must manually specify a minimum threshold to filter out lower Doppler velocities less likely to be associated with the tornado or damaging winds. This minimum threshold would likely vary by case depending on factors such as the range from the radar and mesocyclone intensity and could, therefore, be challenging to determine in real time. Therefore, automation of this threshold identification process is likely needed for any future operational product. The product presented in the weather-radar survey depicts the maximum radial Doppler velocity at every radar range gate over time and had a minimum velocity threshold of 35 m s−1 (Fig. 2b).
Van Den Broeke and Jauernic (2014) showed that 16% of the 744 tornadoes they studied produced a TDS, but 88.2% of tornadoes rated EF3 (n = 17) and 100% of tornadoes rated EF4 or EF5 (n = 7) were associated with a TDS. Considering the strong association between the appearance of a TDS and the occurrence of strong to violent tornadoes, automatically detecting a TDS could provide useful information to forecasters and public safety officials. Snyder and Ryzhkov (2015) described this automated product that uses dual-polarization radar data and a modified version of the hydrometeor classification algorithm (HCA; Park et al. 2009) to identify areas of debris lofted by a tornado (i.e., the TDS). Classifying a TDS involves using fuzzy logic applied to five inputs: azimuthal shear, differential phase, reflectivity, differential reflectivity, and correlation coefficient. The algorithm calculates an aggregation value for each output classifier, the results of which are then used to determine the classifier returned by the HCA at each range gate. In general, the algorithm returns the output classifier with the maximum aggregation value, given that it is at least 0.40 (otherwise, an “unknown” classification is returned). To reduce false detections, the TDS algorithm requires an aggregation value of at least 0.80. By isolating the range gates for which a TDS is assigned and accumulating this classification with time, near-real-time tornado paths can be produced based on locations within the storm characterized by strong rotation and lofted debris (Fig. 2c).
3. Weather-radar survey and focus group design
The link to the online survey was active from 21 April through 13 June 2016, and we received 182 responses during that time. Of the 182 responses, 138 were from Oklahoma, 16 from Wisconsin, 5 from Illinois, and fewer than 5 each from 12 additional states (Fig. 5a). Just over 100 respondents identified themselves as emergency managers, 28 self-identified as first responders, and the remaining 51 identified themselves as “other,” which included positions such as 911 call center director, city manager, and emergency communications chief (Fig. 5b). All respondents used radar data in some way to aid in their decision-making process.
While the survey provided useful information, we did identify some limitations while analyzing the collected responses. The survey format only allowed for limited information to be communicated to the respondents (Fig. 4). This limited information can lead to confusion and likely resulted in some survey respondent’s misconceptions about the tornado track estimation products (section 4). We therefore made some modifications to the focus group design to specifically address questions generated during the survey analysis and to enhance the communication and clarity of the products to the participants. During the focus group, which was held in early September 2016, we provided more detailed information (e.g., strengths and limitations) about each of the products. This approach allowed us to collect more thorough, specific, and informed feedback from a subset of six public safety officials working in central Oklahoma. These six participants were selected—based on willingness, availability, and interest—from a group of central Oklahoma public safety officials and represented county and city emergency management (n = 3 and 2, respectively), as well as first responders (n = 1).
During the focus group, we also expanded on feedback collected from the survey by facilitating a discussion about radar update time (i.e., time between successive radar volume scans) because faster updates of low-level radar data are now available from operational radars (e.g., Crum et al. 2013; ROC 2014) and faster updates of volumetric data are potentially coming in the future (e.g., Zrnić et al. 2007; Heinselman and Torres 2011). To familiarize participants with rapid-update volumetric update times (about 1 min), we showed examples collected by the single-polarization National Radar Testbed Phased Array Radar (Forsyth et al. 2005; Zrnić et al. 2007) and compared such data with examples of conventional volumetric update times (about 4–5 min) collected by the WSR-88D network. We then showed participants examples of the tornado track estimation products created using rapid-update data collected by KOUN and conventional-update data. Participants then answered questions about radar update time and its impacts on the tornado track estimation products.
4. Public safety official feedback
While the results presented here include all collected responses, it is important to remember that 138 of the 182 survey respondents and all focus group participants work in Oklahoma. There were no obvious major differences in the survey responses from those working in Oklahoma and those working outside of Oklahoma, but Oklahoma public safety officials may have more severe-weather-related experience and may also receive different radar-based training (e.g., OK-FIRST). Therefore, the results are likely only generalizable to Oklahoma.
a. Survey results
Survey questions first sought to provide context to each respondent’s feedback by asking about how often they use weather-radar data during severe weather events and how the data were used in the decision-making process. Nearly 80% (n = 143) of survey respondents reported that they used radar data at least once every 10 min when severe weather threatened their area of responsibility. Only 6% (n = 9) reported using radar data no more than once per hour during an event. Respondents provided a wide range of answers to the open-ended questions regarding radar data use, which reflects the wide range of responsibilities public safety officials have, but an analysis identified several common themes. The most common response (n = 78) for the use of radar data was determining a storm’s motion, proximity, and intensity (i.e., storm interrogation). Other common responses included providing information to storm spotters and first responders (n = 40), and activating warning sirens (n = 15). These findings corroborate previous research results (e.g., Baumgart et al. 2008; Weaver et al. 2014).
We also asked an open-ended question about potential decisions that could be made with the support of a tornado track estimation product. Over half (n = 106) of the respondents indicated that these products would help them determine the disaster’s scope and therefore aid in deciding where to send search and rescue teams and disaster-response resources. The products could help them narrow down the area potentially impacted by a tornado and therefore allow them to coordinate recovery efforts to specific areas more quickly. Other potential decisions that multiple respondents mentioned included identifying safe staging areas and transportation routes (n = 10) and checking on individual households and registered storm shelter locations within the damage path (n = 8).
In order, survey respondents indicated that they were most likely to use the 1) NWS track, 2) rotation track, 3) tornado track and intensity, 4) TDS, and 5) maximum Doppler velocity track (Fig. 6a). Similarly, in order from best to worst, survey respondents ranked the usefulness of products as follows: 1) rotation track, 2) NWS track, 3) tornado track and intensity, 4) maximum Doppler velocity track, and 5) TDS (Fig. 6b). Responses to open-ended questions provided insight into the respondents’ reasoning for these rankings and helped to highlight differences in product preferences despite comparable median values for the likelihood of use (Fig. 6a). The NWS track and rotation track were most preferred because they were easy to understand and interpret. Respondents noted that the rotation track did provide additional information about relative intensity and width compared to the NWS track. However, the NWS track was easiest to interpret and provided vital information about where damage may have occurred, so many respondents (n = 79) indicated they were extremely likely to use this product. Responses to the open-ended questions did not provide clear answers to why the tornado track and intensity product was preferred less than the NWS track and rotation track. Respondents did report two primary dislikes—use of the EF scale for estimating intensity prior to completion of the official damage survey and lack of tornado width information—that we infer led to the somewhat lower ratings.
The maximum Doppler velocity track and TDS were least preferred primarily because they were hard to understand. Respondents especially singled out the maximum Doppler velocity track as difficult to use. The product was described as vague, muddled, and confusing, and respondents mentioned the need for significant training to use the product successfully. A few respondents (n = 9) did like that this product could also be used to identify damaging winds outside of the tornado’s circulation (e.g., from strong rear-flank downdrafts or downbursts). Additionally, lower rankings for the TDS product arose from misconceptions about what the product actually showed. The most common misconceptions were 1) the product showed debris that was thrown far from the tornado (i.e., debris fallout) and 2) the product only confirmed that a tornado was present but did not show the tornado’s approximate track. Respondents who did not have these misconceptions tended to assign a higher ranking to the product. These factors likely contributed to the product’s lower median ranking and larger spread in the assigned rankings (Fig. 6b) and were, therefore, a topic that we addressed during the focus group.
b. Focus group results
Focus group questions were aimed at collecting more-detailed information than was obtained in the online survey. The focus group received additional information about each tornado track estimation product, including situations where each product might work well and when it might fail. We also included questions about radar volumetric update time and its impact on the aforementioned products.
Similar to the survey respondents, members of the focus group singled out the NWS track as their most preferred product. This preference arose because they unanimously agreed that it would allow them to quickly identify areas in need of search and rescue teams and disaster-response resources by providing them with the information they need most in the aftermath of a tornado—the location where the tornado occurred and areas that might have sustained damage. They also valued the expert input of NWS forecasters in the product’s creation. Such input can improve the product’s performance because the forecaster can consider radar limitations as well as other data sources (Karstens et al. 2016). In terms of the tornado track and intensity product, focus group participants did like that it provided additional information about intensity not included in the NWS track, but felt that this information was not critical to search and rescue efforts. Search and rescue teams must address the entire path of the tornado regardless of intensity because injuries can occur even where a tornado is not particularly intense. In addition, the participants had concerns about potential misinterpretation of the EF-scale values included within the tornado track and intensity product by key partners and the general public.
Focus group participants identified the TDS product as their most preferred automated product and second most preferred product overall. This preference differed from the survey results likely because the focus group setting allowed us to more clearly communicate what the product showed, how it was produced, and its strengths and limitations. The focus group participants liked that the product provided confirmation of a tornado via detection of lofted debris. They agreed that knowing the location of lofted debris would give a good idea of where damage had likely occurred and what areas might require assistance. Another attractive aspect of the product to the participants was its near-real-time production. As an automated product, the opportunity exists to produce the product quickly and display it in near–real time in software packages such as OK-FIRST (Morris et al. 2002). The TDS product was also identified during a discussion about the group’s ideal tornado track estimation product. One idea included viewing the TDS product along with other radar variables such as reflectivity and velocity in real time. The TDS product could then later be overlaid with the NWS track product when it became available. Focus group participants liked this idea because it provided them with near-real-time information about tornado location as well as expert input provided by the NWS track as soon as it was available.
The focus group unanimously identified the maximum Doppler velocity track product as their least preferred product for a variety of reasons including human factors issues. They felt that the product was cluttered, noisy, hard to interpret, and confusing, which could result in bad decisions such as sending resources to the wrong location. The color scale was also not ideal, though participants said a change in colors would not influence their opinions about the product. Similar to the survey, the focus group pointed to identification of potential wind damage outside of the tornado track as a positive for this product.
After discussing each of the products, we shifted to a discussion about radar update time and its potential role within the public safety official community. Participants were first shown two examples of rapid-update data—one of a tornadic supercell and the other of a downburst-producing severe thunderstorm—side by side with conventional-update data. Based on the two cases, participants agreed that rapid-update data would be beneficial to them in general because it painted a better picture of storm movement and intensity trends. We then showed multiple examples of tornado track estimation products produced by rapid-update data and conventional-update data. Participants unanimously preferred tornado track estimation products produced by rapid-update data because they provided a clearer, more complete picture of what actually happened (Fig. 7a). In contrast, participants felt that products produced with conventional-update data looked incomplete, and it was unclear whether or not the track was produced by a continuous tornado or multiple short-lived tornadoes (Fig. 7c). Despite the preference for the products produced with rapid-update data, participants agreed that product differences arising from update time would likely not affect their decision-making. For example, they felt that all areas in and around the locations highlighted by the product would be searched. However, participants indicated that they were more likely to use a product created with rapid-update data because it looked more complete to them, which gave them more confidence in using the product to determine where the tornado may have occurred and what homes and infrastructure may have been impacted. Therefore, it is likely that the potential benefits of using a tornado track estimation product would be increased if it is produced with rapid-update data.
Participants in both the survey and focus group identified multiple situations where a tornado track estimation product could help public safety officials make life-saving decisions. Therefore, it is important for the operational and research meteorology communities to continue the development of such products and include public safety officials in the development process [i.e., coproduction of knowledge; Meadow et al. (2015)]. Participants in the survey and focus group had many similar opinions about the tornado track estimation products. For example, they singled out the NWS track product as being especially useful because it provided essential information in a straightforward manner. Survey and focus group participants did provide differing feedback with respect to the TDS product, however. Survey participants ranked the TDS product as one of their least preferred products, while focus group participants selected the TDS product as their most preferred automated product. The focus group environment provided an opportunity to more clearly communicate what each product displayed and its strengths and weaknesses. This additional information likely contributed to the differing feedback provided by survey and focus group participants. These results point out the need to develop easily understandable products for all decision-makers as well as the need to clearly communicate key information including how each product is created and situations when the product performs well and when it does not.
Survey and focus group participants also highlighted a need for products to be produced as quickly as possible. Participants preferred to have products available in near–real time rather than waiting for a product. Some participants even went as far as saying that a tornado track estimation product would have little use to them if not available in near–real time. In terms of timeliness, the automated products tend to hold an advantage over the manual products. However, public safety officials preferred the manually produced NWS track because of expert input and ease of use. Therefore, the meteorological community should aim to provide public safety officials with a combination of easy-to-use automated and manually created radar-based products, similar to the idea brought forward by the focus group to provide the TDS product in real time and then overlay it with the NWS track when available (section 4b).
Meteorologists should also consider how products might be shared with public safety officials. Toward this end, we asked respondents about how they might want products sent to them and what file formats would be most preferred. Survey and focus group participants preferred multiple channels of communication (e.g., e-mail, text, and NWS Chat) and file formats (e.g., KML file, shapefile, etc.) that would ultimately allow them to interact with and add information, such as county roads or critical infrastructure, to the products. For example, respondents suggested that the product could be sent via e-mail with an attention-grabbing subject line and at the same time a text message could be sent to each affected party alerting them that the product was completed and ready to view. A KML file and shapefile sent via e-mail would allow recipients to overlay the product with other important geospatial datasets (e.g., storm shelter locations), while an interactive website or smart phone application could allow users to display the product at any location (e.g., incident site). This multipronged approach would allow nearly every public safety official to view and interact with the products regardless of whether he or she had significant experience using a geographic information system (e.g., ArcMap or Google Earth). Additionally, focus group participants stressed the importance of communication using multiple platforms because lines of communication can fail in the aftermath of a disaster.
Previous studies have shown the potential benefits of rapid-update volumetric radar data to NWS forecasters (e.g., Heinselman et al. 2012, 2015; Bowden et al. 2015; Wilson et al. 2017). This work suggests public safety officials will also benefit from more rapidly updating data. Focus group participants unanimously preferred tornado track estimation products created using rapid-update data. While not a primary topic during the focus group, faster low-level WSR-88D updates currently provided by scanning techniques such as Supplemental Adaptive Intravolume Low-Level Scans (SAILS; Crum et al. 2013) and Multiple Elevation Scan Option for SAILS (MESO-SAILS; ROC 2014) should benefit radar-based product creation and public safety officials using low-level radar data (Fig. 7b). A future system of operational phased-array radars has the capability to provide rapid-update volumetric data to users who look above the lowest elevation angle for information about midlevel rotation or hail cores and for products that rely on volumetric data.
The purpose of this study was to involve the public safety official community in the research and development process of radar-based products and future radar systems (e.g., a rapidly updating phased-array radar network). To accomplish this collaboration, we cultivated relationships within the Oklahoma public safety official community by attending meetings, having face-to-face discussions, and presenting at workshops and conferences. We then conducted a weather-radar survey and focus group to collect information from public safety officials regarding their use of radar data, opinions on various developmental tornado track estimation products, ideas for sharing and improving such radar-based products, and first impressions of rapid-update radar data and its impact on tornado track estimation products. Through an analysis of the collected responses, we concluded the following:
Public safety officials use radar data to support many decisions including placement of storm spotters, activation of outdoor warning sirens, and identifying areas in need of search and rescue teams.
Respondents prefer simple, easy-to-use products—such as the one produced by the Norman NWS Forecast Office (Fig. 1a)—that are provided in near–real time.
Clear communication of a product’s content, strengths, and weaknesses is essential for effective use and understanding of a product.
Respondents prefer multiple methods for being alerted to and receiving the product (e.g., text message alerts, NWS Chat, e-mail, etc.) and multiple file types to display the data in a variety of ways (e.g., ArcMap, Google Earth, interactive website, etc.).
Focus group participants indicated that rapid-update radar data provide a clearer picture of storm location and movement and improve the usefulness of tornado track estimation products.
The first conclusion above corroborates findings from past studies on the use of radar data by public safety officials (e.g., Baumgart et al. 2008; League et al. 2010), while the remaining conclusions build upon past work by addressing specific radar-based products and the potential impacts of radar update time. In addition, the information collected through the survey and focus group, along with ongoing interactions with public safety officials, can help product developers refine and improve current and future products. The meteorological community can also use this information in decisions related to radar products and systems. For example, developing straightforward products that quickly and clearly communicate information about the location of a storm’s potential impacts to life and property appears to be most useful to public safety officials.
Despite collecting feedback from over 180 public safety officials, we must be aware of the limitations present in our findings. The sample consists primarily of public safety officials from Oklahoma who may have more experience dealing with severe weather than those in other states and may also receive more radar training owing to initiatives and programs such as OK-FIRST (Morris et al. 2002). No survey questions sought to quantify these differences in training or weather-radar knowledge among survey respondents, though it is important to remember that public safety officials have different levels of training, knowledge, and experience in interpreting and using weather radar. These differences may have affected how each respondent answered the survey questions. In addition, radar and its derived products can be challenging to understand and interpret accurately without additional background information. The focus group setting allowed us to present such information, but the survey setting did not, which could have impacted the survey responses. Survey participants also only saw an example of each product produced using a single case of a strong tornado relatively close to the radar. Focus group participants saw multiple examples including weaker tornadoes, but it may have been difficult for survey participants to provide fully informed feedback after seeing only one example. However, this initial study allowed us to step into the public safety official community and open new doors for additional research. Future work could include nationwide or state-specific surveys, focus groups, or experiments with larger sample sizes that address specific weather-related needs or knowledge gaps identified by public safety officials and research meteorologists. These long-term collaborations between researchers and key stakeholders—consistent with the ideas presented in Meadow et al. (2015)—should advance the knowledge and understanding of both groups, as was demonstrated in this study.
The authors thank all of the public safety officials who participated in the survey and focus group and those who welcomed us into the public safety official community. We thank David Ball for setting up contacts within the public safety official community and providing us with opportunities to give presentations about our research. We also thank Jeff Brogden, Karen Cooper, and Robert Toomey for their expertise with WDSSII; Eddie Forren and Brandon Smith for their help with radar data processing; Daphne LaDue and Andrea Melvin for insightful discussions regarding public safety officials and our research; and Alan Gerard, Terry Schuur, and Greg Whitworth for their internal reviews of the manuscript. We also thank four anonymous reviewers for helping us improve the quality of this manuscript. Funding for CK, JS, and KW was provided by NOAA/Office of Oceanic and Atmospheric Research under NOAA–University of Oklahoma Cooperative Agreement NA11OAR4320072, U.S. Department of Commerce.
Supplemental information related to this paper is available at the Journals Online website: https://doi.org/10.1175/WAF-D-17-0031.s1.