WALLACED_2024-09-09_F022 DerekWallaceUnited States Forest Service RWU 4156Research Professional

320 Green St. Athens GA 30602 U.S.A.

derek.wallace@usda.gov https://orcid.org/0009-0001-2533-4838 StevenFlanaganUnited States Forest Service RWU 4156Research Ecologist

320 Green St. Athens GA 30602 U.S.A.

steven.flanagan@usda.gov Ignition tracking data for the prescribed fire research campaign conducted at Ft. Stewart Army Base (2022). This data can be used to coordinate other prescribed fire datasets collected at each site to better understand where and when ignitions occurred and the fire behavior afterwards. This data was collected with handheld Garmin GPS units, and also Go Pro cameras, processed with ArcGIS Pro geospatial software, GQIS geospatial software, and exist as text files with UTM Zone 17 N locations, date and time (Zulu time zone). The helicopter ignitions used a dragon ball hopper that operated at '2-slow' for all burns.This dataset is part of the Wildland Fire Science Initiative (WFSI) research burn campaign held at Fort Stewart from March 2nd, 2022 to March 5th 2022. 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 2022: Contextual data for Wildland Fire Science Initiative (WFSI) Research Burn Campaign” for more information about the campaign (see Annotations section for hasMetadata link).IgnitionsData Types and Measurement VariablesPrescribed fireSERDPFire behaviorlongleaf pineNoneFort Stewart 2022WFSI 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/. F6.3 and F6.4 sites, Ft. Stewart Army Base, Georgia, United States -81.7558922-81.716410132.081949932.0467888 E16.2 and E16.3 sites, Ft. Stewart Army Base, Georgia, United States -81.8452725-81.805266931.997924531.9881018 2022-03-022022-03-05 https://datacite-metadata-schema.readthedocs.io/en/4.5/appendices/appendix-1/relationType/#hasMetadatahttps://doi.org/10.60594/W4VC7Z DerekWallaceUnited States Forest Service RWU 4156Research Professional

320 Green St. Athens GA 30602 U.S.A.

derek.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 thehelicopters path over the burn unit, and each point in the shapefile, only represent when theGPS 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 thedragon eggs and video recordings from the helicopter. So, calculations can be made as to roughlyhow many dragon eggs were dropped and the spacing between each drop, however the speed of thehelicopter 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 (incendiarydevice). The truck terra torch (Ft. Stewart 2022) is the most accurate among all the dataregarding 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.The helicopter ignitions for the E16 units does not have time records for each location record. I did not collect this data, it was provided by the helicopter pilot as I understand, and I have not determined why the time records were not included. 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_2022.csvtext/csvCHANGES.mdtext/markdownE16_units_helicopter_ignitions.csvtext/csvE16_units_blackline_and_mop_up.csvtext/csvF6_3_blackline.csvtext/csvF6_3_helicopter_ignitions.csvtext/csvF6_4_blackline_and_mop_up.csvtext/csvF6_4_helicopter_ignitions.csvtext/csvFt_Stewart_2022_Data_Dictionary.csvtext/csv