<?xml version="1.0"?>
<metadata xml:lang="en">
<Esri>
<CreaDate>20260814</CreaDate>
<CreaTime>15185100</CreaTime>
<ArcGISFormat>1.0</ArcGISFormat>
<ArcGISProfile>ISO19139</ArcGISProfile>
<DataProperties>
<itemProps>
<imsContentType Sync="TRUE">002</imsContentType>
<itemName Sync="FALSE">Imagery_GIS_Burn_Severity_MTBS_2017</itemName>
<nativeExtBox>
<westBL Sync="TRUE">6323770.187548</westBL>
<eastBL Sync="TRUE">6598572.787548</eastBL>
<southBL Sync="TRUE">1764743.982894</southBL>
<northBL Sync="TRUE">2121337.757894</northBL>
<exTypeCode Sync="TRUE">1</exTypeCode>
</nativeExtBox>
</itemProps>
<coordRef>
<type Sync="TRUE">Projected</type>
<geogcsn Sync="TRUE">GCS_North_American_1983</geogcsn>
<csUnits Sync="TRUE">Linear Unit: Foot_US (0.304801)</csUnits>
<projcsn Sync="TRUE">NAD_1983_StatePlane_California_II_FIPS_0402_Feet</projcsn>
<peXml Sync="TRUE">&lt;ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/3.5.0'&gt;&lt;WKT&gt;PROJCS[&amp;quot;NAD_1983_StatePlane_California_II_FIPS_0402_Feet&amp;quot;,GEOGCS[&amp;quot;GCS_North_American_1983&amp;quot;,DATUM[&amp;quot;D_North_American_1983&amp;quot;,SPHEROID[&amp;quot;GRS_1980&amp;quot;,6378137.0,298.257222101]],PRIMEM[&amp;quot;Greenwich&amp;quot;,0.0],UNIT[&amp;quot;Degree&amp;quot;,0.0174532925199433]],PROJECTION[&amp;quot;Lambert_Conformal_Conic&amp;quot;],PARAMETER[&amp;quot;False_Easting&amp;quot;,6561666.666666666],PARAMETER[&amp;quot;False_Northing&amp;quot;,1640416.666666667],PARAMETER[&amp;quot;Central_Meridian&amp;quot;,-122.0],PARAMETER[&amp;quot;Standard_Parallel_1&amp;quot;,38.33333333333334],PARAMETER[&amp;quot;Standard_Parallel_2&amp;quot;,39.83333333333334],PARAMETER[&amp;quot;Latitude_Of_Origin&amp;quot;,37.66666666666666],UNIT[&amp;quot;Foot_US&amp;quot;,0.3048006096012192],AUTHORITY[&amp;quot;EPSG&amp;quot;,2226]]&lt;/WKT&gt;&lt;XOrigin&gt;-115211800&lt;/XOrigin&gt;&lt;YOrigin&gt;-93821500&lt;/YOrigin&gt;&lt;XYScale&gt;36983428.057351544&lt;/XYScale&gt;&lt;ZOrigin&gt;-100000&lt;/ZOrigin&gt;&lt;ZScale&gt;10000&lt;/ZScale&gt;&lt;MOrigin&gt;-100000&lt;/MOrigin&gt;&lt;MScale&gt;10000&lt;/MScale&gt;&lt;XYTolerance&gt;0.0032808333333333331&lt;/XYTolerance&gt;&lt;ZTolerance&gt;0.00020000000000000001&lt;/ZTolerance&gt;&lt;MTolerance&gt;0.00020000000000000001&lt;/MTolerance&gt;&lt;HighPrecision&gt;true&lt;/HighPrecision&gt;&lt;WKID&gt;102642&lt;/WKID&gt;&lt;LatestWKID&gt;2226&lt;/LatestWKID&gt;&lt;/ProjectedCoordinateSystem&gt;</peXml>
</coordRef>
</DataProperties>
<ModDate>20260820</ModDate>
<ModTime>09373000</ModTime>
<SyncOnce>FALSE</SyncOnce>
<SyncDate>20260820</SyncDate>
<SyncTime>09373000</SyncTime>
</Esri>
<dataIdInfo>
<idAbs>&lt;p&gt;The Monitoring Trends in Burn Severity (MTBS) Program assesses the frequency, extent, and magnitude (size and severity) of all large wildland fires (wildfires and prescribed fires) in the conterminous United States (CONUS), Alaska, Hawaii, and Puerto Rico for the period 1984 and beyond. All fires reported as greater than 1,000 acres in the western U.S. and greater than 500 acres in the eastern U.S. are mapped across all ownerships. MTBS produces a series of geospatial and tabular data for analysis at a range of spatial, temporal, and thematic scales and are intended to meet a variety of information needs that require consistent data about fire effects through space and time. This map layer is a thematic raster image of MTBS burn severity classes for all inventoried fires occurring in Napa County during calendar year 2017. Fires omitted from this mapped inventory are those where suitable satellite imagery was not available, or fires were not discernable from available imagery.&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;p&gt;This dataset has been processed and clipped for Napa County by PBES GIS Staff.&lt;/p&gt;</idAbs>
<idCitation>
<resTitle>Burn_Severity_MTBS_2017</resTitle>
<date>
<pubDate>2026-04-09</pubDate>
</date>
<presForm>
<PresFormCd value="005">
</PresFormCd>
</presForm>
<presForm>
<fgdcGeoform>raster digital data</fgdcGeoform>
</presForm>
<collTitle>A Project for Monitoring Trends in Burn Severity</collTitle>
<citRespParty>
<rpOrgName>U.S. Geological Survey</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>USDA Forest Service</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
</idCitation>
<dataExt>
<geoEle>
<GeoBndBox>
<westBL>-122.6466</westBL>
<eastBL>-122.0614</eastBL>
<northBL>38.8643</northBL>
<southBL>38.1537</southBL>
<exTypeCode>true</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<dataExt>
<exDesc>ground condition</exDesc>
<tempEle>
<TempExtent>
<exTemp>
<TM_Instant>
<tmPosition>2017</tmPosition>
</TM_Instant>
</exTemp>
</TempExtent>
</tempEle>
</dataExt>
<dataExt>
<geoEle>
<GeoBndBox esriExtentType="search">
<westBL Sync="TRUE">-122.836950</westBL>
<eastBL Sync="TRUE">-121.870156</eastBL>
<northBL Sync="TRUE">38.987190</northBL>
<southBL Sync="TRUE">38.005065</southBL>
<exTypeCode>1</exTypeCode>
</GeoBndBox>
</geoEle>
</dataExt>
<idPoC>
<rpOrgName>U.S. Geological Survey</rpOrgName>
<rpPosName>MTBS Project Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<eMailAdd>burnseverity@usgs.gov</eMailAdd>
<delPoint>47914 252nd Street</delPoint>
<city>Sioux Falls</city>
<adminArea>SD</adminArea>
<postCode>57198</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>800-252-4547</voiceNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="007">
</RoleCd>
</role>
</idPoC>
<searchKeys>
<keyword>imageryBaseMapsEarthCover</keyword>
<keyword>Wildfire</keyword>
<keyword>Prescribed fire</keyword>
<keyword>Fire occurrence</keyword>
<keyword>Landsat</keyword>
<keyword>Differenced normalized burn ratio</keyword>
<keyword>Wildland fire</keyword>
<keyword>Normalized burn ratio</keyword>
<keyword>MTBS</keyword>
<keyword>Burned area</keyword>
<keyword>Burn severity</keyword>
<keyword>Fire location</keyword>
<keyword>Location</keyword>
<keyword>Sentinel</keyword>
<keyword>United States</keyword>
<keyword>California</keyword>
<keyword>Napa County</keyword>
<keyword>US</keyword>
<keyword>CONUS</keyword>
<keyword>CA</keyword>
</searchKeys>
<themeKeys>
<keyword>imageryBaseMapsEarthCover</keyword>
<thesaName>
<resTitle>ISO 19115 Topic Category</resTitle>
</thesaName>
</themeKeys>
<themeKeys>
<keyword>Wildfire</keyword>
<keyword>Prescribed fire</keyword>
<keyword>Fire occurrence</keyword>
<keyword>Landsat</keyword>
<keyword>Differenced normalized burn ratio</keyword>
<keyword>Wildland fire</keyword>
<keyword>Normalized burn ratio</keyword>
<keyword>MTBS</keyword>
<keyword>Burned area</keyword>
<keyword>Burn severity</keyword>
<keyword>Fire location</keyword>
<keyword>Location</keyword>
<keyword>Sentinel</keyword>
</themeKeys>
<idPurp>The data generated by MTBS will be used to identify national trends in burn severity, providing information necessary to monitor the effectiveness of the National Fire Plan and Healthy Forests Restoration Act. MTBS is sponsored by the Wildland Fire Leadership Council (WFLC), a multi-agency oversight group responsible for implementing and coordinating the National Fire Plan and Federal Wildland Fire Management Policies. The MTBS project objective is to provide consistent, 30-meter spatial resolution burn severity data and burned area delineations that will serve four primary user groups including: 1. National policies and policy makers such as the National Fire Plan and WFLC which require information about long-term trends in burn severity and recent burn severity impacts within vegetation types, fuel models, condition classes, and land management activities. 2. Field management units that benefit from mid to broad scale GIS-ready maps and data for pre- and post-fire assessment and monitoring. Field units that require finer scale burn severity data will also benefit from increased efficiency, reduced costs, and data consistency by starting with MTBS data. 3. Existing databases from other comparably scaled programs, such as Fire Regime and Condition Class (FRCC) within LANDFIRE, that will benefit from MTBS data for validation and updating of geospatial datasets. 4. Academic and government agency research entities interested in fire severity data over significant geographic and temporal extents.</idPurp>
<idCredit>Monitoring Trends in Burn Severity Project (U.S. Geological Survey and USDA Forest Service)</idCredit>
<resConst>
<Consts>
<useLimit>This layer is open data. It is made available under the Public Domain Dedication and License version v1.0 whose full text can be found at: https://opendatacommons.org/licenses/pddl/1.0/	Disclaimer: This GIS data is intended to provide a visual display of data for the user's convenience. Users of this data are hereby notified that the appropriate public primary information sources should be consulted for verification of the information. Although every reasonable effort has been made to assure the accuracy of this data, Napa County makes no warranty, representation or guaranty as to the content, sequence, accuracy, timeliness or completeness of any of the data provided herein and explicitly disclaims any representations and warranties, including, without limitation, the implied warranties of merchantability and fitness for a particular purpose. Napa County assumes no liability for any errors, omissions, or inaccuracies in the information provided regardless of how caused and assumes no liability for any decisions made or actions taken or not taken by the user of the data in reliance upon any information or data furnished hereunder. Because the GIS data provided is not warranted to be up-to-date, the user should check with the County staff for updated information.</useLimit>
</Consts>
</resConst>
<resConst>
<LegConsts>
<useLimit>Unless otherwise stated, all data, metadata and related materials are considered to satisfy the quality standards relative to the purpose for which the data were collected. Although these data and associated metadata have been reviewed for accuracy and completeness and approved for release by the U.S. Geological Survey (USGS), no warranty expressed or implied is made regarding the display or utility of the data for other purposes, nor on all computer systems, nor shall the act of distribution constitute any such warranty.</useLimit>
</LegConsts>
</resConst>
<dataLang>
<languageCode value="eng" Sync="TRUE">
</languageCode>
<countryCode value="USA" Sync="TRUE">
</countryCode>
</dataLang>
<dataChar>
<CharSetCd value="004">
</CharSetCd>
</dataChar>
<spatRpType>
<SpatRepTypCd value="002">
</SpatRepTypCd>
</spatRpType>
<envirDesc>ERDAS Imagine and ESRI ArcGIS</envirDesc>
<idStatus>
<ProgCd value="001">
</ProgCd>
</idStatus>
<suppInfo>This dataset contains thresholded burn severity data available for the specified state or geographic region at time of publication. The dataset may be updated as burn severity data for additional MTBS fires are completed, or otherwise revised as necessary. See https://www.mtbs.gov/ for project information and data access. Refer to https://www.mtbs.gov/contact for additional support. This dataset has been processed and clipped by Napa County PBES GIS Staff</suppInfo>
<resMaint>
<maintFreq>
<MaintFreqCd value="quarterly or as needed">
</MaintFreqCd>
</maintFreq>
</resMaint>
<aggrInfo>
<aggrDSName>
<resTitle>A Project for Monitoring Trends in Burn Severity</resTitle>
<date>
<pubDate>2007</pubDate>
</date>
<citRespParty>
<rpOrgName>Jeff Eidenshink</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Brian Schwind</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Ken Brewer</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Zhi-Liang Zhu</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Brad Quayle</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<citRespParty>
<rpOrgName>Stephen Howard</rpOrgName>
<role>
<RoleCd value="006">
</RoleCd>
</role>
</citRespParty>
<presForm>
<PresFormCd value="publication">
</PresFormCd>
</presForm>
<presForm>
<fgdcGeoform>publication</fgdcGeoform>
</presForm>
<otherCitDet>Fire Ecology Special Issue
Vol. 3, No. 1, 2007</otherCitDet>
<citOnlineRes>
<linkage>https://www.mtbs.gov/sites/mtbs/files/inline-files/Eidenshink-final.pdf</linkage>
</citOnlineRes>
</aggrDSName>
<assocType>
<AscTypeCd value="002">
</AscTypeCd>
</assocType>
</aggrInfo>
<placeKeys>
<keyword>United States</keyword>
<keyword>California</keyword>
<keyword>Napa County</keyword>
<thesaName>
<resTitle>Common geographic areas</resTitle>
</thesaName>
</placeKeys>
<placeKeys>
<keyword>US</keyword>
<keyword>CONUS</keyword>
<keyword>CA</keyword>
<thesaName>
<resTitle>Common geographic areas</resTitle>
</thesaName>
</placeKeys>
<tpCat>
<TopicCatCd value="010">
</TopicCatCd>
</tpCat>
<tpCat>
<TopicCatCd value="013">
</TopicCatCd>
</tpCat>
</dataIdInfo>
<mdLang>
<languageCode value="eng" Sync="TRUE">
</languageCode>
<countryCode Sync="TRUE" value="USA">
</countryCode>
</mdLang>
<mdHrLv>
<ScopeCd value="005">
</ScopeCd>
</mdHrLv>
<mdHrLvName>dataset</mdHrLvName>
<mdChar>
<CharSetCd value="004">
</CharSetCd>
</mdChar>
<mdDateSt>20260409</mdDateSt>
<mdContact>
<rpOrgName>U.S. Geological Survey</rpOrgName>
<rpPosName>MTBS Project Manager</rpPosName>
<rpCntInfo>
<cntAddress addressType="both">
<eMailAdd>burnseverity@usgs.gov</eMailAdd>
<delPoint>47914 252nd Street</delPoint>
<city>Sioux Falls</city>
<adminArea>SD</adminArea>
<postCode>57198</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>800-252-4547</voiceNum>
</cntPhone>
</rpCntInfo>
<role>
<RoleCd value="007">
</RoleCd>
</role>
</mdContact>
<dqInfo>
<dqScope>
<scpLvl>
<ScopeCd value="005">
</ScopeCd>
</scpLvl>
</dqScope>
<dataLineage>
<prcStep>
<stepDesc>For a detailed definition and discussion on the processing and production of MTBS geospatial data, please refer to https://www.mtbs.gov. A synopsis of the production of this layer is provided below.
MTBS burn severity class data are derived from data obtained from suitable imagery (including Landsat TM, Landsat ETM+, Landsat OLI, Sentinel 2A, and Sentinel 2B). A pre- and a post-fire scene are used to create a dNBR image. The continuous dNBR image portrays the variations of burn severity within the fire. In exceptional circumstances, a suitable pre-fire image may not be available to generate a dNBR. Consequently, analysis and assessment are conducted using the post-fire Normalized Burn Ratio (NBR) image only.
The MTBS mapping approach has consistently occurred in five primary steps:
1. Fire Occurrence Data Compilation
2. Scene Selection and Image Pre-processing
3. Perimeter Delineation
4. Burn Severity Interpretation
5. Data Distribution;
1. Fire Occurrence Data Compilation:
Historically, MTBS compiled fire occurrence data from several federal and state databases that maintained little consistency in standards for content, geospatial accuracy, and nomenclature. These datasets were then filtered and standardized internally by MTBS staff to reduce duplication of incident records reported by multiple agencies, and to resolve gross geospatial inaccuracies that were commonly found in the source data.
In recent years, significant improvements have been made to streamline the reporting procedures and data exchange for land management agencies in their creation and maintenance of fire occurrence data. Specifically, the Integrated Reporting of Wildland-Fire Information (IRWIN) Project has provided an end-to-end fire reporting system focused on the goals of reducing redundant data entry, identifying authoritative data sources, and improving the consistency, accuracy, and availability of operational data. Through a multi-year phased approach, the IRWIN Project is tasked with identifying and integrating fire occurrence data from several different sources and applications.
Fire occurrence data from IRWIN are routinely ingested into a database maintained by MTBS and other postfire mapping programs, and currently make up the bulk of the records used by MTBS to identify candidate fires for mapping. More information on IRWIN can be found at: https://www.forestsandrangelands.gov/WFIT/applications/IRWIN/index.shtml.</stepDesc>
<stepDateTm>2026-04-09</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>2. Scene Selection and Image Pre-processing: For fire events that meet the minimum size requirement for MTBS mapping, corresponding Landsat or Sentinel scenes are selected based upon the reported location and ignition date. After an initial review and determination of the appropriate assessment strategy: initial, extended, or single scene, candidate pre-fire and postfire scenes are reviewed and downloaded using tools and applications developed by U.S. Geological Survey Earth Resources Observation and Science (EROS) Center, such as Earth Explorer and GloVis. Limitations due to scene quality are common in areas prone to cloud cover (e.g., the Southeast United States). Other atmospheric conditions such as smoke from active fires, terrain shadows and other obscurations also reduce the number of candidate scenes. In addition, northern latitudes are subject to a shorter period of optimal scene selection due to undesirable sun angles in the fall and a shorter growing season.
Downloaded scenes are processed to generate top-of-atmosphere reflectance images according to existing USGS-EROS protocols that include geometric (including terrain correction) and radiometric correction through the Landsat Ground Processing System process. Prior to processing the imagery into a burn severity product, pre-fire and postfire images are inspected for co-registration accuracy and corrected if spatial differences are noted.
Using the reflectance imagery, a Normalized Burn Ratio (NBR) image is generated for each pre-fire and postfire scene as the normalized difference between middle infrared and near infrared wavelength bands and then differenced to create a dNBR image. A relativized dNBR (RdNBR) is also calculated to evaluate potential limitations of dNBR to characterize fire severity on low biomass sites and potentially enhance inter-fire comparability of the results at larger ecological scales. Processing the Landsat image data to NBR, dNBR and RdNBR is a straightforward series of calculations relying principally on automated production sequences.</stepDesc>
<stepDateTm>2026-04-09</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>3. Perimeter Delineation:
The burned area boundary is delineated by on-screen interpretation of the reflectance imagery, NBR, dNBR and/or RdNBR images. The mapping analyst digitizes a perimeter to include any detectable fire area derived from these images. Clouds, cloud shadows, snow or other anomalies intersecting the fire area are also delineated and used to generate a mask later in the workflow. The mapping analyst may inspect and/or modify an existing burn area boundary and mask sourced from a reputable fire occurrence dataset or fire detection model when available. To ensure consistency and high spatial precision, digitization and inspection is performed at on-screen display scales between 1:24000 and 1:50000.</stepDesc>
<stepDateTm>2026-04-09</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>4. Burn Severity Interpretation:
The process of developing a categorical burn severity product is subjective and is dependent on analyst interpretation. The analyst evaluates the dNBR data range and determines where significant thresholds exist in the data to discriminate between burn severity classes. Interpretations are conducted on the NBR, dNBR and RdNBR data, aided by the pre-fire and postfire imagery, and analyst experience with fire behavior and effects in each ecological setting. Where available, high-resolution imagery is visually inspected to provide confidence in selecting the burn severity thresholds.
Thresholding dNBR data into thematic class values results in an intuitive map depicting a manageable number of ecologically significant classes (typically 4 to 7 class values). There are uncertainties in this approach stemming from analyst subjectivity and limited or no plot data to guide threshold selection. Ecological significance of burn severity classes will also likely vary across regions and landscapes and one set of thresholds cannot be expected to apply equally well to all analysis objectives and management issues.</stepDesc>
<stepDateTm>2026-04-09</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>5. Data Distribution:
The primary access point for acquiring MTBS data is through the program website: https://www.mtbs.gov. There you will find an interactive viewer which allows users to search for and download individual fire data in addition to direct download options for state and national data products. Connection information is also provided for those interested in using web map services.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
Source burn severity raster for 2017 was downloaded from the MTBS Direct Download portal (https://burnseverity.cr.usgs.gov/direct-download). Source raster is an 8-bit unsigned, single-band GeoTIFF with classified pixel values 1–6 representing burn severity categories per the standard MTBS/BAER scheme. Original CRS is [SOURCE CRS — e.g., EPSG 4326 / GCS WGS 1984].
Tool/Software: MTBS Direct Download — https://burnseverity.cr.usgs.gov/direct-download</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
Napa County boundary feature class was dissolved to a single polygon using arcpy.management.Dissolve, then buffered outward by 5 miles using arcpy.analysis.Buffer (dissolve option: ALL) to ensure full coverage of fires with burn extent crossing the county boundary. Buffer was created in the coordinate system of the county boundary feature class and stored as a temporary feature class in a scratch file geodatabase.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
The 5-mile county buffer was reprojected to match the native coordinate system of the source raster ([SOURCE CRS]) using arcpy.management.Project prior to clipping. Reprojection of the mask — rather than the raster — avoids introducing resampling artifacts before the clip operation. If the buffer and source raster shared the same CRS (matched factory codes), this step was skipped and the original buffer was used directly as the clip mask.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
Source raster was clipped to the 5-mile buffered Napa County boundary using Spatial Analyst Extract by Mask (arcpy.sa.ExtractByMask). Pixels outside the buffer extent were assigned NoData. Output was saved as a temporary raster in the scratch file geodatabase. This step requires the ArcGIS Spatial Analyst extension.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
Clipped raster was reprojected from [SOURCE CRS] to NAD83 California State Plane Zone 2 (EPSG 2226, US feet) using arcpy.management.ProjectRaster. Resampling technique was set to NEAREST NEIGHBOR to preserve exact integer class values (1–6). Bilinear or cubic resampling was intentionally avoided as interpolation between discrete class values would produce invalid non-integer results. Cell size was maintained at the equivalent of 30 meters in US feet (~98.43 ft) to match the native MTBS raster resolution. Output saved as a temporary raster in the scratch file geodatabase.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
Raster pyramids were built on the reprojected raster using arcpy.management.BuildPyramids. All pyramid levels were generated (level = -1, full pyramid set). Compression type LZ77 (lossless) was applied. Resampling technique was set to NEAREST NEIGHBOR to maintain class value integrity at all pyramid levels. Existing pyramids were overwritten. Pyramids are embedded in the final COG to enable efficient multi-scale streaming in ArcGIS Online.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
<prcStep>
<stepDesc>Step description by Napa County PBES GIS:
Final output was exported as a Cloud Optimized GeoTIFF (COG) using arcpy.management.CopyRaster with format set to CLOUD_OPTIMIZED_GEOTIFF. Pixel type retained as 8-bit unsigned. LZW lossless compression applied. COG internal tiling and pyramid structure enable efficient partial reads and zoom-level streaming when hosted as an Imagery Layer in ArcGIS Online or ArcGIS Enterprise.</stepDesc>
<stepDateTm>2026-05-20</stepDateTm>
</prcStep>
</dataLineage>
<report type="DQQuanAttAcc">
<measDesc>MTBS analysts examine the differenced Normalized Burn Ratio (dNBR) image for each fire in the context of remote sensing spectral data and any ancillary information available to the analyst. dNBR image data for each fire are thresholded into classes representing unburned areas; areas of low, moderate, high burn severities; and areas of increased vegetation response. Analysts follow guidelines established by subject matter experts to maintain consistency in discerning burn severity thresholds from fire to fire and minimize subjectivity.</measDesc>
</report>
<report type="DQConcConsis">
<measDesc>No tests for logical consistency have been performed on this map layer.</measDesc>
</report>
<report type="DQCompOm">
<measDesc>Data completeness reflects the availability of fire occurrence information and/or availability of suitable imagery (including Landsat TM, Landsat ETM+, Landsat OLI, Sentinel 2A, and Sentinel 2B), and the current progression of processing by the MTBS program in the specified state or geographic region. In some areas, fires smaller than the specified MTBS fire size criteria may be present. These fires were mapped using MTBS mapping protocols to meet the data/information needs of other unrelated programs but are included in the MTBS database.</measDesc>
</report>
<report dimension="horizontal" type="DQAbsExtPosAcc">
<measDesc>Each image used to create the burn severity assessment (utilizing Landsat TM, Landsat ETM+, Landsat OLI, Sentinel 2A, and Sentinel 2B), was precision terrain-corrected using 3-arc-second digital terrain elevation data, and Geo registered using ground control points. This resulted in a root mean square registration error of less than 1 pixel (30-meters).</measDesc>
</report>
<report dimension="vertical" type="DQAbsExtPosAcc">
<measDesc>N/A</measDesc>
</report>
</dqInfo>
<distInfo>
<distFormat>
<formatName>File Geodatabase Raster Dataset</formatName>
</distFormat>
<distributor>
<distorCont>
<rpIndName>GS ScienceBase</rpIndName>
<rpOrgName>U.S. Geological Survey</rpOrgName>
<role>
<RoleCd value="005">
</RoleCd>
</role>
<rpCntInfo>
<cntAddress addressType="postal">
<eMailAdd>sciencebase@usgs.gov</eMailAdd>
<delPoint>Denver Federal Center, Building 810, Mail Stop 302</delPoint>
<city>Denver</city>
<adminArea>CO</adminArea>
<postCode>80225</postCode>
<country>US</country>
</cntAddress>
<cntPhone>
<voiceNum>1-888-275-8747</voiceNum>
</cntPhone>
</rpCntInfo>
</distorCont>
<distorOrdPrc>
<resFees>None</resFees>
</distorOrdPrc>
<distorFormat>
<formatName>Digital Data</formatName>
</distorFormat>
<distorTran>
<onLineSrc>
<linkage>https://doi.org/10.5066/P9NETC0T</linkage>
</onLineSrc>
</distorTran>
</distributor>
</distInfo>
<refSysInfo>
<RefSystem>
<refSysID>
<identCode code="2226" Sync="TRUE">
</identCode>
<idCodeSpace>EPSG</idCodeSpace>
<idVersion>5.3(9.0.0)</idVersion>
</refSysID>
</RefSystem>
</refSysInfo>
<eainfo>
<detailed Name="SDE_VAT_108">
<enttyp>
<enttypl>None</enttypl>
<enttypd>Raster geospatial data file</enttypd>
<enttypds>Producer defined</enttypds>
<enttypt>Table</enttypt>
<enttypc>6</enttypc>
</enttyp>
<attr>
<attrlabl>OBJECTID</attrlabl>
<attalias>OBJECTID</attalias>
<attrtype>OID</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
<attrdef>Internal feature number.</attrdef>
<attrdefs>Esri</attrdefs>
<attrdomv>
<udom>Sequential unique whole numbers that are automatically generated.</udom>
</attrdomv>
</attr>
<attr>
<attrlabl>Value</attrlabl>
<attrdef>Unique numeric values contained in each raster cell</attrdef>
<attrdefs>Producer defined</attrdefs>
<attrdomv>
<edom>
<edomv>0</edomv>
<edomvd>Background/No Data</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>1</edomv>
<edomvd>Unburned/Underburned to Low Burn Severity</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>2</edomv>
<edomvd>Low burn severity</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>3</edomv>
<edomvd>Moderate burn severity</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>4</edomv>
<edomvd>High Burn Severity</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>5</edomv>
<edomvd>Increased Greenness/Increased Vegetation Response</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attrdomv>
<edom>
<edomv>6</edomv>
<edomvd>Non-Processing Area Mask</edomvd>
<edomvds>Producer defined</edomvds>
</edom>
</attrdomv>
<attalias>Value</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>Count_</attrlabl>
<attalias>Count_</attalias>
<attrtype>Double</attrtype>
<attwidth>8</attwidth>
<atprecis>38</atprecis>
<attscale>8</attscale>
</attr>
<attr>
<attrlabl>ClassName</attrlabl>
<attalias>ClassName</attalias>
<attrtype>String</attrtype>
<attwidth>100</attwidth>
<atprecis>0</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>R</attrlabl>
<attalias>R</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>10</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>G</attrlabl>
<attalias>G</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>10</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>B</attrlabl>
<attalias>B</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>10</atprecis>
<attscale>0</attscale>
</attr>
<attr>
<attrlabl>Opacity</attrlabl>
<attalias>Opacity</attalias>
<attrtype>Integer</attrtype>
<attwidth>4</attwidth>
<atprecis>10</atprecis>
<attscale>0</attscale>
</attr>
</detailed>
<overview>
<eaover>MTBS thematic burn severity classes are thresholded from continuous dNBR images or NBR images when pre-fire images are not available. Thresholds are based on interpretation by MTBS analysts.</eaover>
<eadetcit>MTBS Thresholded Burn Severity</eadetcit>
</overview>
</eainfo>
<spatRepInfo>
<Georect>
<numDims>3</numDims>
<axisDimension type="001">
<dimSize>101538</dimSize>
</axisDimension>
<axisDimension type="002">
<dimSize>156336</dimSize>
</axisDimension>
<axisDimension type="003">
<dimSize>1</dimSize>
</axisDimension>
<cellGeo>
<CellGeoCd value="002">
</CellGeoCd>
</cellGeo>
</Georect>
</spatRepInfo>
<mdStanName>ArcGIS Metadata</mdStanName>
<mdStanVer>1.0</mdStanVer>
<spdoinfo>
<rastinfo>
<rasttype Sync="TRUE">Pixel</rasttype>
<rowcount Sync="TRUE">3623</rowcount>
<colcount Sync="TRUE">2792</colcount>
<rastxsz Sync="TRUE">98.425000</rastxsz>
<rastysz Sync="TRUE">98.425000</rastysz>
<rastbpp Sync="TRUE">8</rastbpp>
<vrtcount Sync="TRUE">1</vrtcount>
<rastorig Sync="TRUE">Upper Left</rastorig>
<rastcmap Sync="TRUE">TRUE</rastcmap>
<rastcomp Sync="TRUE">LZ77</rastcomp>
<rastband Sync="TRUE">1</rastband>
<rastdtyp Sync="TRUE">pixel codes</rastdtyp>
<rastifor Sync="TRUE">SDR</rastifor>
<rastplyr Sync="TRUE">TRUE</rastplyr>
</rastinfo>
</spdoinfo>
<spref>
<horizsys>
<planar>
<planci>
<plance Sync="TRUE">row and column</plance>
<coordrep>
<absres Sync="TRUE">98.425000</absres>
<ordres Sync="TRUE">98.425000</ordres>
</coordrep>
</planci>
</planar>
</horizsys>
</spref>
</metadata>
