{ "currentVersion": 11.5, "cimVersion": "3.5.0", "serviceDescription": "

NOTE: this is exercise data and not representative of real events. The original data is from wildfires in New Mexico in June 2025.<\/span><\/p>

Dates of Images:<\/span><\/p>

Post-Event: May 23, 2026; May 22, 2026<\/span><\/p>

Pre-Event: May 20, 2025<\/span><\/p>

Date of Next Image:<\/span><\/p>

Unknown<\/span><\/p>

Summary:<\/span><\/p>

These pre-fire and post-fire images pair were analyzed for normalized burn ratio (NBR). The input images were generated from the Harmonized Landsat Sentinel-2 (HLS) dataset at 30m resolution.<\/span><\/p>

NBR is defined mathematically as (NIR \u2013 SWIR)/(NIR + SWIR) where NIR is near-infrared and SWIR is short-wave infrared. dNBR is computed by the difference between the pre-fire NBR and the post-fire NBR. More information on dNBR can be found here: https://un-spider.org/advisory-support/recommended-practices/recommended-practice-burn-severity/in-detail/normalized-burn-ratio.<\/span><\/p>

dNBR data may be computed while the fire is in progress. This is intentionally done to prioritize rapid data availability for proactive disaster response but means data can change over the course of the fire.<\/span><\/p>

Check fire containment and image dates for further context on image timing.<\/span><\/p>

Suggested Use:<\/span><\/p>

NBR is commonly used as a proxy to indicate areas which have charred vegetation. Darker areas (more negative values) in the NBR image more strongly represent the presence of burned vegetation. Since the dNBR considers the condition of the scene before the fire occurred, the resulting value has been used as a proxy for burn severity. Higher dNBR values represent a proxy for greater burn severity. Negative dNBR values may represent a re-greening of or growth of vegetation in between pre and post imagery.<\/span><\/p>

The use of this dNBR product as a quantitative metric of burn severity at the time of posting this dataset should be strongly caveated. This is due to several dNBR limitations:<\/span><\/p>

The spectral band selections used for dNBR calculations, and the implication of changes observed following fire in those wavelengths, primarily pertain to how vegetation spectral signatures change in NIR and SWIR wavelengths following charring. Because of this, dNBR may not accurately describe burned surfaces that are not vegetation (e.g. human built infrastructure).<\/span><\/p>

This dataset has not been validated by independent burn severity assessments.<\/span><\/p>

The degree to which dNBR is accurately determined depends on careful selection of pre and post event imagery. An effort was made to use the highest quality imagery (i.e. cloud free) with representative conditions for each scene; however, it is unknown at the time of this posting how selection of different pre/post image pairs could affect the derived dNBR values.<\/span><\/p>

Satellite/Sensor:<\/span><\/p>

Harmonized Landsat Sentinel-2 data: https://www.earthdata.nasa.gov/data/projects/hls<\/span><\/p>

Resolution:<\/span><\/p>

30 meters<\/span><\/p>

Credits:<\/span><\/p>

NASA LP DAAC: https://www.earthdata.nasa.gov/data/projects/hls<\/span><\/p>

Service URL:<\/span><\/p>

https://gis.earthdata.nasa.gov/portal/home/item.html?id=42dc8b50e387435ea4dc80a13c4ca9ca<\/span><\/p>

WMS Endpoint:<\/span><\/p>

https://gis.earthdata.nasa.gov/gis05/services/DISASTERS_202506_FIRE_NM/2506_hls_dnbr/ImageServer/WMSServer<\/span><\/p>

<\/p><\/div><\/div><\/div>", "mapName": "ex2605_hls_dnbr", "description": "NOTE: this is exercise data and not representative of real events. The original data is from wildfires in New Mexico in June 2025.Dates of Images:Post-Event: May 23, 2026; May 22, 2026Pre-Event: May 20, 2025Date of Next Image:UnknownSummary:These pre-fire and post-fire images pair were analyzed for normalized burn ratio (NBR). The input images were generated from the Harmonized Landsat Sentinel-2 (HLS) dataset at 30m resolution.NBR is defined mathematically as (NIR \u2013 SWIR)/(NIR + SWIR) where NIR is near-infrared and SWIR is short-wave infrared. dNBR is computed by the difference between the pre-fire NBR and the post-fire NBR. More information on dNBR can be found here: https://un-spider.org/advisory-support/recommended-practices/recommended-practice-burn-severity/in-detail/normalized-burn-ratio.dNBR data may be computed while the fire is in progress. This is intentionally done to prioritize rapid data availability for proactive disaster response but means data can change over the course of the fire.Check fire containment and image dates for further context on image timing.Suggested Use:NBR is commonly used as a proxy to indicate areas which have charred vegetation. Darker areas (more negative values) in the NBR image more strongly represent the presence of burned vegetation. Since the dNBR considers the condition of the scene before the fire occurred, the resulting value has been used as a proxy for burn severity. Higher dNBR values represent a proxy for greater burn severity. Negative dNBR values may represent a re-greening of or growth of vegetation in between pre and post imagery.The use of this dNBR product as a quantitative metric of burn severity at the time of posting this dataset should be strongly caveated. This is due to several dNBR limitations:The spectral band selections used for dNBR calculations, and the implication of changes observed following fire in those wavelengths, primarily pertain to how vegetation spectral signatures change in NIR and SWIR wavelengths following charring. Because of this, dNBR may not accurately describe burned surfaces that are not vegetation (e.g. human built infrastructure).This dataset has not been validated by independent burn severity assessments.The degree to which dNBR is accurately determined depends on careful selection of pre and post event imagery. An effort was made to use the highest quality imagery (i.e. cloud free) with representative conditions for each scene; however, it is unknown at the time of this posting how selection of different pre/post image pairs could affect the derived dNBR values.Satellite/Sensor:Harmonized Landsat Sentinel-2 data: https://www.earthdata.nasa.gov/data/projects/hlsResolution:30 metersCredits:NASA LP DAAC: https://www.earthdata.nasa.gov/data/projects/hlsService URL:https://gis.earthdata.nasa.gov/portal/home/item.html?id=42dc8b50e387435ea4dc80a13c4ca9caWMS Endpoint:https://gis.earthdata.nasa.gov/gis05/services/DISASTERS_202506_FIRE_NM/2506_hls_dnbr/ImageServer/WMSServer", "copyrightText": "NASA LP DAAC, USGS, NASA Disasters Program", "supportsDynamicLayers": true, "layers": [ { "id": 0, "name": "Difference between (Post-event) May 23, 2026 and (Pre-event) May 20, 2025", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Raster Layer", "supportsDynamicLegends": true }, { "id": 1, "name": "Difference between (Post-event) May 22, 2026 and (Pre-event) May 20, 2025", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Raster Layer", "supportsDynamicLegends": true } ], "tables": [], "spatialReference": { "wkid": 6933, "latestWkid": 6933, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -17367700, "falseY": -7342400, "xyUnits": 10000, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 }, "singleFusedMapCache": false, "initialExtent": { "xmin": -1.1802628501253575E7, "ymin": 4560126.8115453655, "xmax": -1.1785663097367615E7, "ymax": 4574104.070220134, "spatialReference": { "wkid": 6933, "latestWkid": 6933, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -17367700, "falseY": -7342400, "xyUnits": 10000, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "fullExtent": { "xmin": -1.1801828141130172E7, "ymin": 4556896.398386732, "xmax": -1.178314446808631E7, "ymax": 4578759.162241404, "spatialReference": { "wkid": 6933, "latestWkid": 6933, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -17367700, "falseY": -7342400, "xyUnits": 10000, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "datesInUnknownTimezone": false, "minScale": 0, "maxScale": 0, "units": "esriMeters", "supportedImageFormatTypes": "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP", "documentInfo": { "Title": "ex2605_hls_dnbr", "Author": "", "Comments": "NOTE: this is exercise data and not representative of real events. The original data is from wildfires in New Mexico in June 2025.Dates of Images:Post-Event: May 23, 2026; May 22, 2026Pre-Event: May 20, 2025Date of Next Image:UnknownSummary:These pre-fire and post-fire images pair were analyzed for normalized burn ratio (NBR). The input images were generated from the Harmonized Landsat Sentinel-2 (HLS) dataset at 30m resolution.NBR is defined mathematically as (NIR \u2013 SWIR)/(NIR + SWIR) where NIR is near-infrared and SWIR is short-wave infrared. dNBR is computed by the difference between the pre-fire NBR and the post-fire NBR. More information on dNBR can be found here: https://un-spider.org/advisory-support/recommended-practices/recommended-practice-burn-severity/in-detail/normalized-burn-ratio.dNBR data may be computed while the fire is in progress. This is intentionally done to prioritize rapid data availability for proactive disaster response but means data can change over the course of the fire.Check fire containment and image dates for further context on image timing.Suggested Use:NBR is commonly used as a proxy to indicate areas which have charred vegetation. Darker areas (more negative values) in the NBR image more strongly represent the presence of burned vegetation. Since the dNBR considers the condition of the scene before the fire occurred, the resulting value has been used as a proxy for burn severity. Higher dNBR values represent a proxy for greater burn severity. Negative dNBR values may represent a re-greening of or growth of vegetation in between pre and post imagery.The use of this dNBR product as a quantitative metric of burn severity at the time of posting this dataset should be strongly caveated. This is due to several dNBR limitations:The spectral band selections used for dNBR calculations, and the implication of changes observed following fire in those wavelengths, primarily pertain to how vegetation spectral signatures change in NIR and SWIR wavelengths following charring. Because of this, dNBR may not accurately describe burned surfaces that are not vegetation (e.g. human built infrastructure).This dataset has not been validated by independent burn severity assessments.The degree to which dNBR is accurately determined depends on careful selection of pre and post event imagery. An effort was made to use the highest quality imagery (i.e. cloud free) with representative conditions for each scene; however, it is unknown at the time of this posting how selection of different pre/post image pairs could affect the derived dNBR values.Satellite/Sensor:Harmonized Landsat Sentinel-2 data: https://www.earthdata.nasa.gov/data/projects/hlsResolution:30 metersCredits:NASA LP DAAC: https://www.earthdata.nasa.gov/data/projects/hlsService URL:https://gis.earthdata.nasa.gov/portal/home/item.html?id=42dc8b50e387435ea4dc80a13c4ca9caWMS Endpoint:https://gis.earthdata.nasa.gov/gis05/services/DISASTERS_202506_FIRE_NM/2506_hls_dnbr/ImageServer/WMSServer", "Subject": "(EXERCISE - JAHAAX 2026) Normalized Burn Ratio Difference (dNBR) for California Refinery Fires May 2026", "Category": "", "Version": "3.5.0", "AntialiasingMode": "Fast", "TextAntialiasingMode": "Force", "Keywords": "USA,California,NASA,NASA Disasters Program,Wildfires,NBR,dNBR,Normalized Burn Ratio" }, "supportsQueryDomains": true, "capabilities": "Query,Map,Data", "supportedQueryFormats": "JSON, geoJSON, PBF", "exportTilesAllowed": false, "referenceScale": 0.0, "supportsDatumTransformation": true, "archivingInfo": {"supportsHistoricMoment": false}, "supportsClipping": true, "supportsSpatialFilter": true, "supportsTimeRelation": true, "supportsQueryDataElements": true, "mapUnits": {"uwkid": 9001}, "maxSelectionCount": 2000, "maxRecordCount": 2000, "maxImageHeight": 4096, "maxImageWidth": 4096, "supportedExtensions": "WMSServer", "serviceItemId": "90b2308ebb8b4a24ae43c22fa837af17" }