Discrete fire events, their severity, and their ignitions, as derived from MODIS MCD 14ML active-fire detection data for Indonesia, 2002-2019

3. DATA FILES Two data files are distributed here – one for discrete fire events, and another for the ignition AFDs of each fire event. The data files are provided in a GIS-compatible format, and also as a generic text format, as described below. 3.1 GIS VERSION Data files in GIS-compatible format are provided as ‘feature classes’ within an ArcGIS file geodatabase ‘Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb’. These data files can be viewed and manipulated using either ArcGIS Desktop or ArcGIS Pro software. There is one feature class for fire events, and another file for ignitions. Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb\nfire4_all_spatial_fire_2002_2019_joins_sp_LC This file pertains to fire events. All AFDs of a given fire event are included, without differentiation as to whether the AFDs are ignition AFDs or other (propagation) AFDs. Fire events are assigned unique ID values and basic attribute data. Sloan_MODIS_FireEvents_Ignitions_2002_2019.gdb\nfire4_all_spatial_fire_2002_2019_igs_sp_LC This file pertains to ignitions. Only ignition AFDs are included for a given fire event. Fire events corresponding to the ignitions are assigned unique ID values and basic attribute data. 3.2 CSV TEXT VERSION Both data files are also supplied as comma-separated value (CSV) text files for viewing and manipulation in non-GIS software, such as Excel, text editors, or any statistical software. The text files can also be read into various GIS software. CSV-formatted files have the same file name and attribute fields as the corresponding GIS-formatted data files. These CSV-formatted data files (as well as the GIS-formatted data files) include attribute data on the latitude and the longitude of each AFD. Attribute field names are included as the first row of values in a CSV file. No ‘text qualifiers’ like quotations (“ ”) or inverted commas (‘’) are used to designate text/string values within the CSV file. Text values appear directly between commas in the CSV data file, e.g., …,Kalimantan_Southern,… . Note two points of caution for working with these CSV data: i) Microsoft Excel may be used for a partial view of the data file nfire4_all_spatial_fire_2002_2019_joins_sp_LC.csv, but it is not recommended for working with this data file. This is because the number of records/rows in this csv file slightly exceeds that maximum that may be read by Excel, which is just over 1 million. This limitation does not apply to the other csv file, however. ii) The GIS-formatted data files employ ‘null values’ in their attribute tables, and so the corresponding ‘values’ in the CSV-formatted data files are similarly null. For null values, no value whatsoever is ascribed, not even 0. In the syntax of a CSV file (apparent upon opening the file in any text editor like Microsoft Notepad), a null value is denoted by two consecutive commas without any value, text, or space between them. If a CSV file were opened in Excel, a cell assigned a null value would be blank, not 0 or otherwise. This denotes the correct transcription of the GIS-formatted data. This feature will not impede the correct reading of these CSV data by whatever software. Users are made aware of this feature merely to ensure the proper input of these data into whatever software.