WALLACED_2024-12-19_AF93 DerekWallaceU.S. Forest ServiceProfessional Researcher

320 E. Green St Athens Georgia 30602 USA

(512) 698 - 7008derek.wallace@usda.gov https://orcid.org/0009-0001-2533-4838 StevenFlanaganU.S. Forest ServiceResearch Ecologist

320 E. Green St Athens Georgia 30602 USA

Steven.Flanagan@usda.gov Ignition tracking data collected with Garmin GPS and Go Pro recorders for prescribed fire research. Ignitions for the Ft. Stewart 2024 prescribed burns were completed primarily with dragon eggs dropped from a helicopter, and the ground ignitions were completed with a terra torch attached to the back of a pickup truck. On the E11.5 burn unit the dragon ball hopper ran at the '2-Fast' speed setting until 15:04 Zulu time when the operator switched to '4-slow' speed setting for the remainder of that unit. On the E16 units the dragon ball hopper ran at the '4-slow' speed setting for the entire burn. The terra torch ignitions were used to set the black line, that is a line of fire set to have a backing fire burn a side of the unit that will "receive" the main ignitions by the helicopter. The remaining ignitions by the terra torch were used to "clean up/mop up" remaining areas around edges of the burn unit that did ignite due to local conditions (e.g. variability in the landscape).This dataset is part of the Wildland Fire Science Initiative (WFSI) research burn campaign held at Fort Stewart from February 8th 2024 to February 10th 2024. In addition, pre- and post-fire data collection occurred before and after these dates. See the most recent version of the contextual dataset “Fort Stewart 2024: Contextual data for Wildland Fire Science Initiative (WFSI) Research Burn Campaign” for more information about the campaign (see Annotations section for has Metadata link).Ignition trackingData Types and Measurement VariablesTerra torchDragon ballsPrescribed firelongleaf pineFire behaviorNoneFort Stewart 2024WFSI Research Burn Campaign This work is licensed under the Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/. E11.5 site, Fort Stewart, Georgia -81.81697-81.8169732.02260432.022604 E16 sites, Fort Stewart, Georgia -81.87215-81.8721532.0223832.02238 2024-02-082024-02-10 https://datacite-metadata-schema.readthedocs.io/en/4.5/appendices/appendix-1/relationType/#hasMetadatahttps://doi.org/10.60594/W4KW2R DerekWallaceU.S. Forest ServiceProfessional Researcher

320 E. Green St Athens Georgia 30602 USA

(512) 698 - 7000derek.wallace@usda.gov https://orcid.org/0009-0001-2533-4838 Go Pro 11's Calibration/Settings: 1. Time Zone: UTC-5. 2. Video Settings: Standard, Highest quality, Hyperview, 1x speed/low light. 3. Satellite Systems: GPS/GLONASS/GALILEO (this is standard for Go Pro 11, you don't have to set this). 4. Time format: 12 Hour 5. Time Zone: Automatically set after you set date and time manually, or automatically when you connect to the internet. 6. Position format: Decimal degrees. Garmin eTrex 10's Calibration/Settings: 1. Time Zone: Zulu, but will also record local time. 2. Satellite systems: GPS/GLONASS a. Optionally, in the settings turn on WAAS/EGNOS for more accurate GPS position information. 3. Record interval: Most often. 4. Time format: 12 hour. 5. Distance and speed: Statute. 6. Elevation: Feet/minute. 7. Position format: Decimal degrees. 8. Map datum: WGS 84. 9. Map spheroid: WGS 84. QA/QC: The Go Pro GPS data was extracted into a CSV file and converted into a Shapefile in the ArcGIS Pro workspace. The Garmin GPS data was extracted into a GPX file and also converted into a Shapefile in the ArcGIS Pro workspace. With the two shapefiles, my notes from each days burn, the Go Pro ignition videos, and the burn plans provided by the ignition boss, I was able to confirm the accuracy of the tracking data. I also clipped the tracking data using the videos and my knowledge of the burn units and surrounding areas. Known issues/Limitations: It is important to understand the these shapefiles only identify where the igniters travelled, and that each point location in a shapefile does represent where fire was put on the ground, only the path travelled when fire was put on the ground. For example, the shapefile of the helicopters path over the burn unit, and each point in the shapefile, only represent when the GPS pinged the satellite, and each point in the shapefile does not indicate where a dragon egg (incendiary device) dropped. However, I do have the rate at which the helicopter dropped the dragon eggs and video recordings from the helicopter. So, calculations can be made as to roughly how many dragon eggs were dropped and the spacing between each drop, however the speed of the helicopter and and drift experienced by a dragon egg would complicate the matter. The above goes for the ignition tracking on the ground, both the truck terra torch (incendiary device). The truck terra torch is the most accurate among all the data regarding where fire was placed on the ground, due to the slow speed at which the truck moved, the truck travelled on the roads surrounding the burn units, the video recordings, the GPS data, and my familiarity of the burn units. Conversion of coordinate systems:1. I used ArcGIS Pro version3.3.1 to upload the raw tracking data, edit the data (e.g. remove points where no ignitions occurred) and convert to NAD83 UTM 17N.2. I then used QGIS version 3.28.13-Firenze to export the tracking data into a .csv file format. James Furman USDA FS james.h.furman@usda.gov Principal Investigator U. S. Department of Defense (DoD), Strategic Environmental Research and Development Program (SERDP) http://dx.doi.org/10.13039/100013316 RC20-7189 WFSI_flmd_file_index_Fort_Stewart_2024.csvtext/csvCHANGES.mdtext/markdownE11_5_blackline.csvtext/csvE11_5_heli_ignitions.csvtext/csvE11_5_test_fire.csvtext/csvE16_units_blackline.csvtext/csvE16_units_heli_ignitions.csvtext/csvE16_units_test_fire.csvtext/csvFt_Stewart_2024_Data_Dictionary.csvtext/csv