Wildfire Risk and Wildfire Risk Extreme:
-
Addition of Provisional Neighborhood spatial file and quarterly Fire perimeter refresh
-
Addition of two new fields in Geoenrichment file
-
Change in file naming for Wildfire Risk
Abstract
If you are a Wildfire Risk and/or Wildfire Risk Extreme Data Customer, please read this very important Product Support Announcement. The Wildfire Risk and Wildfire Risk Extreme products will include an additional spatial file and two new data fields in the Geoenrichment data schema. We are also making changes to the filenames of the Wildfire Risk product deliverable. These updates will be in effect from April 2026 for Wildfire Risk and May 2026 for Wildfire Risk Extreme (v.2026.03)
Specific details can be found below.
Overview
Provisional Spatial layers and Reason Codes in Geoenrichment file
Wildfire Risk and Wildfire Risk Extreme products are released quarterly and include a spatial Fire Risk Pro polygon dataset and a Geoenrichment flat file that contains PreciselyIDs enriched with risk ratings.
With each passing quarter, there is a possibility of intervening wildfires and updated address point locations which may lead to a currentness mismatch between the product and changing reality on the ground. To address this mismatch, additional datasets (provisional_neighborhood and updated fire perimeters), and an additional field in the main Geoenrichment files are now being introduced.
The Geoenrichment file will contain a new data field called PROV_STATUS that will contain codes that can be used to identify those PreciselyIDs whose ratings will be reviewed and potentially changed in upcoming releases of the spatial Fire Risk Pro dataset due to the currentness mismatch mentioned above.
Geocoding accuracy indicator in Geoenrichment file
We are now providing an additional field in the Geoenrichment file that distinguishes between PreciselyIDs with the highest spatial accuracy in their geocoded locations and a smaller subset that originates from lower-accuracy geocoding processes. This additional field will be called LOC_ACC. We believe this approach gives our customers both clarity and flexibility, ensuring business decisions are based on information you can trust.
Filenames for Wildfire Risk
For Wildfire Risk (NOT Wildfire Risk Extreme), we will be making changes to the file naming to follow Precisely's file naming standards and bring uniformity across Enrich data products. Currently, the filenames inside the delivery zip files in the data folder read fireriskpro_<region number>_<region_name>.shp, etc. These files will now be named fire_risk_pro_<region number>_<region_name>.shp, etc. This change also brings alignment between Wildfire Risk and Wildfire Risk Extreme naming conventions.
Example: fireriskpro_22_big_sur.shp will be changed to fire_risk_pro_22_big_sur.shp.
Features and Functionality
Data Schema
The updated data schema information which incorporates all the breaking changes is attached to this announcement. The 'field value key' tab in the Data Schema workbook describes each possible value in the two new fields, namely, PROV_STATUS and LOC_ACC.
Breaking change Summary
In summary,
- The spatial content of the products will see a new layer, provisional_neighborhood, added as a separate XTAB and SHP file.
- The fire perimeter dataset that was previously only updated annually will now be updated quarterly.
- The Geoenrichment file will contain two new data fields PROV_STATUS and LOC_ACC
- Filenames in the deliverable package for Wildfire Risk (NOT Wildfire Risk Extreme) will be changing from fireriskpro… to fire_risk_pro…
Product Refresh
The above, newly introduced changes will be refreshed quarterly after the Q1 2026 April release
Documentation
For the April 2026 Release, we will also be reiterating these changes in the Product Release Notes in Precisely Help Center
Availability
Wildfire Risk - April Release v2026.03
Wildfire Risk Extreme - May Release v2026.03
Precisely understands the disruptive nature of a breaking change, and how important the Wildfire Risk and Wildfire Risk Extreme products are to your use cases and business processes. We believe this advance notice will serve you better in planning for this change.
We appreciate your continued business and use of Precisely products!
Contact Information
If you would like technical assistance, please contact the Precisely Global Support team at Contact Support – Precisely Support.
Product documentation is available in the Precisely Help Center at help.precisely.com.
Any questions relating to this announcement should be directed to Chris White, Product Management Director, at chris.white@precisley.com.