Main Content

Hazus Releases

This page contains information regarding Hazus updates and any previous releases of the software that have resulted in changes, updates, and improvements to Hazus. Links to useful documents and information related to a particular release are also provided below.

Hazus 4.2 (SP01)

Release Date: May 25, 2018

Specific enhancements in Service Pack 1 include:

  • Integration of the Hazus Export Tool
  • The addition of USGS Vs30 Site Soil Characterization to the Earthquake module
  • A new view of buildings damaged by count to the Hurricane module
  • New import capabilities in the Flood module
  • New documentation for design upgrades, including case studies of recent performance and methodology changes

 

Additionally, defect resolutions addressed include:

  • Fixes to shelter parameters (Earthquake and Hurricane), and displaced households (Hurricane)
  • Waste water facilities mapping fix (Hurricane)
  • Severe losses no long exceed exposure in coastal analysis (Flood)
  • Now able to assign damage functions to essential facilities (Flood)
  • When combining Earthquake and Tsunami, damage no longer underestimated for moderate seismic events
     

Hazus 4.2 SP1 has the same hardware and software requirements as Hazus 4.2.

Hazus 4.2

Release Date: January 29, 2018

On January 29, 2018, the Hazus Team deployed release 4.2. This release is a full-versioned software release with a number of key highlights, including:

  • Hazus 4.2 is compatible with ArcGIS 10.5.1
  • Major processing time reductions for hydrology and hydraulics within level 1 flood.
  • Additional supported formats for level 2 flood depth grid import
  • High resolution ShakeMaps now compatible, with faster import times
  • Restoration of the Fire Following Earthquake (FFE) module
  • Improvements to the Comprehensive Data Management System (CDMS) for easier import of user data

NOTE: You must uninstall any existing versions of Hazus and all Microsoft SQL components from your computer before downloading and ensure that you have ArcGIS 10.5.1 on your computer. Because of the datum update, any existing state databases need to be replaced with the new state data provided on the FEMA Map Service Center Download page.

Users wishing to preserve their study regions and transfer them to Hazus 4.2 may do so, but only if they are operating on the most recent version of Hazus (4.0). They will be able to follow the steps outlined in the Getting Started Guide available with the download to extract their study regions in Hazus 4.0 and then upload them into 4.2 once it is downloaded. For questions or issues, feel free to contact the Hazus Help Desk at hazus-support@riskmapcds.com.

Hazus 4.0

Release Date: March 20, 2017

On March 20, 2017, the Hazus Team deployed the Hazus Tsunami Module as part of the Hazus 4.0 release. This release is a full-versioned software release with a number of key highlights, including:

  • Territory Analysis: This release represents the first time that analysis will be available for U.S. Pacific territories (Guam, American Samoa, Commonwealth of Northern Mariana Islands, and and U.S. Virgin Islands).
  • New Point Format: The Hazus General Building Stock (GBS) for the Tsunami release will use a new National Structure Inventory (NSI) point format (details in User Release Notes available with download).
  • Case Studies: The Tsunami Module will require user-provided data, so the Hazus Team has provided five case study datasets for users, which will be available on the MSC download site.
  • Two Types of Damage Analysis: Users will be able to run both near-source (Earthquake + Tsunami) and distant-source (Tsunami only) damage analysis.

NOTE: You must uninstall any existing versions of Hazus and all Microsoft SQL components from your computer before downloading and ensure that you have ArcGIS 10.4 on your computer. When installing ArcGIS 10.4, a patch must be applied for Hazus 4.0 to properly display ArcGIS attribute tables from the ArcMap Table of Contents. Additional details are available in the User Release Notes as part of the Hazus Installation package. The patch is available at: http://support.esri.com/download/7427.

Users wishing to preserve their study regions and transfer them to Hazus 4.0 may do so, but only if they are operating on the most recent version of Hazus (3.2). They will be able to follow the steps outlined in the Getting Started Guide available with the download to extract their study regions in Hazus 3.2 and then upload them into 4.0 once it is downloaded.

For the Tsunami Module, users must supply their own data for analysis. To assist in preparing this data, the Hazus Team has provided five case study datasets for users, which are available at the bottom of the MSC download page. Users can model their own datasets after these samples.

For questions or issues, feel free to contact the Hazus Help Desk at hazus-support@riskmapcds.com.

What Has Changed?

Users will notice the following major changes to installation:

When upgrading Hazus 3.2 to 4.0, users should follow these steps:

  • After uninstalling Hazus 3.2 or any other version of Hazus, it is always recommended to uninstall all Microsoft SQL Server components as well. To do this, go to Windows Control Panel  Uninstall Programs and remove any instances of Microsoft SQL Server or related products
  • Users should make sure to delete the C:\HazusData folder after uninstalling Hazus 3.2 to avoid duplicate Hazard Data Input folders being created
  • When installing ArcGIS 10.4, a patch must be applied for Hazus 3.2 or 4.0 to properly display ArcGIS attribute tables from the ArcMap Table of Contents. All other Hazus capability will function without this patch; the patch is only for the proper display of attribute tables. The patch is available at: http://support.esri.com/download/7427
  • Users should use a location other than the root C:\ drive for extracting the HAZUS_APP zip. When extracting the zip file, extract the files to an existing folder, or a new folder such as C:\HazusApp

Users will notice the following addition to the Hazus software hazards:

  • Hazus 4.0 is the official release of the Hazus Tsunami Module. Hazus Tsunami will offer two types of hazard analysis based on the location of the source of the earthquake that caused the tsunami:
    • Distant Source (Tsunami Only), where the earthquake occurs far enough from land or deep enough in the ocean such that coastal areas will only see impact from inundation, but not ground shaking. For this type of study region, select only the Tsunami checkbox in the aggregation wizard
    • Near Shore (Combined Tsunami & Earthquake), where the earthquake is near enough to the landmass that coastal areas will experience impacts from both earthquake and tsunami – for this type of analysis, select both Earthquake and Tsunami checkboxes in the aggregation wizard
  • Much like Hazus Hurricane is only available for states vulnerable to hurricanes, Hazus Tsunami is only available for a selection of high risk U.S. States and Territories. Hazus Tsunami is only available for the following states/territories:
    • Alaska
    • Washington
    • Oregon
    • California
    • Hawaii
    • Northern Mariana Islands (Tsunami only)
    • American Samoa (Tsunami only)
    • Guam (Tsunami only)
    • Puerto Rico
    • U.S. Virgin Islands (Tsunami only)

If the user selects Tsunami or Tsunami + Earthquake for their study region, the state list in the aggregation wizard will be filtered to these states. Please note at this time, standalone earthquake analysis is not complete for the U.S. territories and should not be run independent of tsunami analysis. The functionality to run the standalone earthquake analysis is available for the territories, but results should not be used until development and testing on that analysis component is complete

  • If an Earthquake + Tsunami study region is aggregated for any of the states listed above, the user will be asked to select which hazard to open first in the study region. Hazus will default to Earthquake and users must first run the Earthquake analysis before switching to Tsunami to produce combined losses.
  • Hazus supports aggregation of multi-hazard study regions (Earthquake, Flood, Hurricane and Tsunami), however, the user can streamline study region size and aggregation if hazards are separated

Users will notice the following changes to the Hazus Earthquake Module:

  • An existing defect in the AEBM Individual Building Report was resolved; the report now displays correctly
  • A change was made to the buffers surrounding ShakeMap grid cells. Previously, there is existed a possibility for overlap of the buffers, causing point structures (EF or UDF) to report falsely inflated PGA values
  • A friendly reminder to avoid using the EQ study region interface to add or edit UDF data. It is recommended to use the AEBM module through CDMS as much as possible. Any UDF which must be imported through the study region must be in spatial table (feature class) MDB format. Access MDBs are no longer supported for import directly into the study region

Users will notice the following changes to the Hazus Shell and Utilities:

  • The entire Hazus application is currently compatible with ArcGIS 10.4. Additional changes were made in Hazus 3.2 to minimize the dependency on ArcGIS versions. For this reason, Hazus may be installed on and used on versions later than 10.4; however, these versions are not certified or supported by the Hazus program. Installation and use of Hazus on ArcGIS 10.4.1 or later versions are done at the user’s risk, with no guarantee Hazus 4.0 or Tsunami will run on 10.4.1 or later

Users will notice the following changes to the Hazus Datasets:

  • New state data is available for the Tsunami states and territories. Please download from MSC before running Tsunami. If using old data, your tsunami study region won’t aggregate
  • Sample case study data is available for all analysis levels on the MSC download site, to demonstrate best practices in preparing tsunami hazard data. For notes on file preparation, please see Appendix A of the User Release Notes available with the download of the software

Pre-existing defects:

  • A list of key defects and issues known to occur in Hazus 4.0 is provided in the User Release Notes available with the download of the software

Useful Links

Hazus 3.2

Release Date: October 31, 2016

As part of an effort to continue modernizing Hazus, we are excited to announce the release of Hazus 3.2. This release is a full-versioned software release that implements a number of changes, including:

  • ArcGIS Upgrade: Hazus 3.2 is now compatible with ArcGIS 10.4. The new version also reduces overall version dependency within Hazus, such that the software can be installed on versions of ArcGIS other than 10.4 (Note: The Hazus Help Desk team will only be supporting 10.4)
  • USGS ShakeMap: The Hazus Earthquake module has been integrated with the United States Geological Survey’s (USGS) ShakeMap in order to pull in ground motion and shaking intensity maps from significant earthquake events for preparedness and disaster planning
  • Enhanced Reports: Existing Hazus reports have been improved to Crystal Reports 2011, allowing for better data visualization and more ways to analyze and view your Hazus results

NOTE: You must uninstall any existing versions of Hazus and all Microsoft SQL components from your computer before downloading and ensure that you have ArcGIS 10.4 on your computer. When installing ArcGIS 10.4, a patch must be applied for Hazus 3.2 to properly display ArcGIS attribute tables from the ArcMap Table of Contents. Additional details are available in the User Release Notes as part of the Hazus Installation package. The patch is available at: http://support.esri.com/download/7427. Please read the Getting Started Guide in the HAZUS_APP folder from the MSC download for further details..

Users wishing to preserve their study regions and transfer them to Hazus 3.2 may do so, but only if they are operating on the most recent version of Hazus (3.1). They will be able to follow the steps outlined in the Getting Started Guide available with the download to extract their study regions in Hazus 3.1 and then upload them into 3.2 once it is downloaded. For questions or issues, feel free to contact the Hazus Help Desk at hazus-support@riskmapcds.com.

What Has Changed?

Users will notice the following major changes to installation:

When upgrading Hazus 3.1 to 3.2 users should follow these steps:

  • When upgrading Hazus 3.1 to 3.2, users must first upgrade ArcGIS 10.2.2 to ArcGIS 10.4
  • When installing ArcGIS 10.4, a patch must be applied for Hazus 3.2 to properly display ArcGIS attribute tables from the ArcMap Table of Contents. The patch is available at: http://support.esri.com/download/7427
  • After uninstalling Hazus 3.1 or any other version of Hazus, it is always recommended to uninstall all Microsoft SQL Server components as well. To do this, go to Windows Control Panel à Uninstall Programs and remove any instances of Microsoft SQL Server or related products
  • Users should use a location other than the root C:\ drive for extracting the HAZUS_APP zip. When extracting the zip file, extract the files to an existing folder, or a new folder such as C:\HazusApp. 

Users will notice the following changes to the Hazus Flood Module:

  • During testing, a latent defect in the Census Data was discovered where census blocks with a value of zero for MedianYearBuilt were not producing results. Analysis results from previous versions of Hazus going back beyond the Census 2010 data updates may be impacted by this. Users are advised to download the new state data provided with this release for all analyses moving forward. Note there are a small number of census blocks which contain exposure but will still produce zero-value results because of their very small size (eg. major highway interchanges). For the methodology used to correct the data, see Appendix D. 
  • The User Defined Facilities Report under Results à Summary Reports was updated so that losses now display in the $1000s, instead of actual dollars as before
  • Content values and resulting losses for UDFs are now based on user-supplied input for contents
  • A glitch caused by the apostrophe in O’Brien County, IA was fixed to remove an error thrown in the Flood Specific Occupancy Mapping dialog
  • The Agriculture Exposure Report now populates correctly with results, instead of showing blank as before
  • Intermittent issues with SQL locking and denying access to some files were addressed; this should reduce errors or crashes within the Hydrology and Hydraulics analysis
  • All reports were upgraded to Crystal Reports 2011 and enhanced to include updated Hazus logo graphics. The Global Summary Report was further enhanced to include graphical representations of results

Users will notice the following changes to the Hazus Earthquake Module:

  • The Debris Summary Report now opens correctly. Previously, some users saw a blank Fire Following Earthquake report
  • All reports were upgraded to Crystal Reports 2011 and enhanced to include updated Hazus logo graphics. The Global Summary Report was further enhanced to include graphical representations of results
  • A new hazard interface was added to the Earthquake Scenario Wizard to allow direct import of USGS ShakeMap products with an internet connection. Please note: USGS limits the types of ShakeMaps available for download into Hazus. By default, Hazus will search for events occurring within the last 90 days and with a magnitude of 5.0 or greater. The 90 day window can be manually adjusted within Hazus (see Step 2 below), however it may benefit the user to check the USGS ShakeMap download archive (https://earthquake.usgs.gov/data/shakemap/) for event availability prior to setting up a study region.

Users will notice the following changes to the Hazus Hurricane Module:

  • All reports were upgraded to Crystal Reports 2011 and enhanced to include updated Hazus logo graphics. The Global Summary Report was further enhanced to include graphical representations of results
  • Please note, the following error may occur after clicking “Run” for Hurricane Analysis:

“Error loading type library/DLL”

This is a Windows issue and is not caused by Hazus. To remove the error, please ensure all Windows updates and patches have been applied to the machine

Users will notice the following changes to the Hazus Shell and Utilities:

  • The entire Hazus application was upgraded to be compatible with ArcGIS 10.4. Additional changes were made to minimize the dependency on ArcGIS versions. For this reason, Hazus may be installed on and used on versions later than 10.4; however, these versions are not certified or supported by the Hazus program. Installation and use of Hazus on ArcGIS 10.4.1 is done at the user’s risk
  • In the backend code, ArcObject calls were reduced and replaced as much as possible to help modernize and simplify the software architecture. In earthquake, the calls were replaced with stored procedures. In flood, calls were replaced with ArcGIS Geoprocessing (GP) Tools. This eliminates duplication with the code, and allows troubleshooting and fixes to takes place in centralized procedures then propagate to parts of Hazus code where they are required.

Users will notice the following changes to the Hazus Datasets:

  • Major enhancements were made to CDMS data import capabilities
  • Due to ongoing issues with ArcGIS and recent changes made to CDMS import capability, the option to import MDB format UDF databases through the study region is no longer supported. Users wishing to import UDF data directly to the study region without CDMS must now convert their MDB file to a feature class using ArcCatalog. For instructions for exporting pipeline/lifeline data to a geodatabase from CDMS, see Appendix C
  • Import issues to the California state database were fixed
  • All state data has been updated to include a value for the Median Year Built field based on the methodology described in Appendix D
  • Study region aggregation was failing for places where <null> values were present in the BackupPower field; a default value of “0” was added instead of <null>
  • For user data in a study region, Hazus limits the number of records visible at one time. This limit is set to 100,000 in Hazus 3.2. 

Pre-existing defects:

  • Opening a layer attribute table through the Table of Contents within Hazus has occasionally caused Hazus to crash in previous versions. With the upgrade to ArcGIS 10.4, Esri identified a bug where the attribute table crashes became much more frequent. A patch was provided by Esri for use in Hazus 3.2, and is now incorporated into this release. However, users should be aware that this issue may continue to occur on rare occasion. If the attribute table data is needed, a manual export of the data to a program outside of ArcMap or Hazus may be necessary
  • A latent defect exists in the Hazus flood model which prevents Hazus from appropriately determining whether a riverine or coastal damage function should be used for a user-defined facility (UDF) in a combined riverine-coastal or coastal-only scenario. When working in coastal regions, an incorrect default damage function will be applied to an individual facility
  • CDMS users at the FEMA’s Emergency Management Institute (EMI) and users with similar workstation security settings may be unable to export to Excel. Please contact the Hazus Help Desk for a workaround: hazus-support@riskmapcds.com

Useful Links

Hazus 3.1

Release Date: April 4, 2016

This release is a full-versioned software release that implements 6 enhancements and addresses 21 defects. These changes include improvements to the installation process, inclusion of Average Annualized Loss (AAL) analysis, and backend code fixes to the software architecture that help improve overall performance. To see a full list of changes with this version, please read the User Release Notes that are available with the download package of the software.

NOTE: The instructions for uninstalling your old version of Hazus and installing Hazus 3.1 have changed. Please read the Getting Started Guide in the HAZUS_APP folder from the MSC download for details.

Users wishing to preserve their study regions and transfer them to Hazus 3.1 may do so, but only if they are operating on the most recent version of Hazus (3.0). They will be able to follow the steps outlined in the Getting Started Guide available with the download to extract their study regions in Hazus 3.0 and then upload them into 3.1 once it is downloaded. For questions or issues, feel free to contact the Hazus Help Desk at hazus-support@riskmapcds.com.

What Has Changed?

Users will notice the following major changes to installation:

Installation was improved by separating installation of the SQL instance from the application, behind the scene. This prevents numerous common SQL errors that users encountered during installations of previous Hazus versions.

When upgrading Hazus 3.0 to 3.1 users should follow these steps:

  • Uninstall Hazus 3.0 through Windows Control Panel à Uninstall Programs
  • Open ArcGIS Administrator and confirm your license information is visible. If a blank screen is shown in ArcGIS Administrator, go to Windows Control Panel à Uninstall Programs and click on Uninstall/Change for ArcGIS. Select the “Repair” radio button and proceed. Once the Repair function is complete, confirm your license information is visible in ArcGIS Administrator
  • Open the HAZUS_APP folder for 3.1, downloaded from MSC. Select the InstallHazus.exe file, right click, and choose Run as Administrator. The setup.exe file with dark blue icon should no longer be used.

Users should use a location other than the root C:\ drive for extracting the HAZUS_APP zip. When extracting the zip file, extract the files to an existing folder, or a new folder such as C:\HazusApp. 

Users will notice the following changes to the Hazus Flood Module:

  • Average Annualized Loss (AAL) analysis is now available for full suite of return periods for User Defined Facilities (UDF). After running General Building Stock (GBS) UDF analysis, users can now go to Analysis à Average Annualized Loss and select option for UDF. A report is generated under Results à Summary Reports à Buildings tab
  • Occupancy Loss table is now populated with correct results for combined wind/surge analysis and is viewable in either Flood or Hurricane

Users will notice the following changes to the Hazus Earthquake Module:

  • Backend VB6 code converted to .NET and C#
  • UDFs added outside the study region boundary no longer produce results

Users will notice the following changes to the Hazus Hurricane Module:

  • SLOSH basins with updated vertical datum were obtained from NOAA and incorporated with Hazus Surge to reduce analysis failures
  • SLOSH basins no longer fail for counties where FIPS code begins with “0”
  • Errors occurring during the manual addition of UDFs were fixed and removed

User will notice the following changes to the Hazus Shell and Utilities:

Note: Testing and validation has not been conducted on Windows 10, and Help Desk support is not available for users running Hazus on Windows 10 operating system.

  • Backend VB6 code replaced with .NET and C#
  • Upgraded SQL Server database from 2008 to 2014
  • Replaced MS Access Jet Engine with Access Database Engine (ACE)
  • Removed Registry keys usage and replaced it with XML configuration file at C:\ProgramFiles(x86)\Hazus-MH. Edits can be made to the XML document at the user’s risk. If edits do not follow correct XML formatting, the Hazus application may not work properly

User will notice the following changes to the Hazus Datasets:

  • Essential facilities has been added to the Hawaii state data MDF
  • Census boundary data for Colorado has been updated to allow aggregation of earthquake study regions
  • Dasymetric field properties of certain census block for Pennsylvania have been updated to match their corresponding blocks in the homogeneous data

Pre-existing defects:

  • A latent defect exists in the Hazus flood model which prevents Hazus from appropriately determining whether a riverine or coastal damage function should be used for a user-defined facility (UDF) in a combined riverine-coastal scenario. In some instances when working with UDFs, an incorrect default function may be applied to an individual facility. Workarounds can be found in the User Release Notes for this release, available with the download of the software
  • CDMS users at the FEMA’s Emergency Management Institute (EMI) and users with similar workstation security settings may be unable to export to Excel. Please contact the Hazus Help Desk for a workaround: hazus-support@riskmapcds.com

Useful Links

Hazus 3.0

Release Date: November 16, 2015

A number of architectural changes were made to the Hazus code structure with the release of Hazus 3.0. This release contained a number of underlying software architectural changes, including:

  • Migration of the current database structure away from the Personal Geodatabase (pGDB) format to SQL Server Spatial format
  • Migration of all VB6 code in the Flood model to a combination of C# and .NET
  • Support at the state level for both homogeneous and dasymetric state data, with dasymetric data now serving as the default for analysis
  • Alignment with the Benefit Cost Analysis (BCA) tool (pushed from Task 2)
  • SQL Server-compatible version of CDMS
  • Repair of four major defects in block-level aggregation in the Flood and Hurricane models

What Has Changed?

Users will notice the following changes to the Hazus Flood Module:

  • Conversion of VB6 code into C# - This serves as mostly an architectural change, but users will notice quicker analyses and run-times for their study regions, while the interface will remain largely similar to previous versions

Alignment with FEMA’s Benefit Cost Analysis (BCA) Tool – FEMA’s BCA depth damage functions (DDF), used for mitigation investment decisions, had diverged from Hazus in the past, but the Hazus Flood Module has now been better aligned with the BCA. 

Users will notice the following changes to the Hazus Earthquake Module:

  • No major functionality or visual changes were made to the Earthquake Module
  • The Fire Following Earthquake (FFE) tool has been disabled with this release

Users will notice the following changes to the Hazus Hurricane Module:

  • No major functionality or visual changes were made to the Hurricane Module
  • A number of small fixes from previous defect lists were made, including: Global Summary Report for the state of Florida; “This field name is not known” error in Crystal Reports Viewer for Hospital damage; Error in certain essential facilities falling outside dasymetric Census Block boundaries

User will notice the following changes to the Hazus Shell and Utilities:

  • No major functionality or visual changes were made to the Hazus Shell or additional Utilities
  • CDMS support for state databases in the new SQL Server Format was added; for more details and steps in how to manipulate the state data in the new format, check out the User Release Notes

User will notice the following changes to the Hazus Datasets:

  • Migration of the current database structure from personal Geodatabases (pGDB) to SQL Server spatial format – This change will greatly reduce run times for study regions and improves overall Hazus performance and functionality
  • Dasymetric data set as default – While previously, Hazus users would have to download separate datasets for homogeneous and dasymetric state data, the dasymetric data has now been made the default for download; users can download both datasets with one link on the Hazus download page. Detailed directions on how to switch from the default dasymetric to the homogeneous dataset are included in the User Release Notes. A detailed guide and flyer for how to decide between which dataset to use for your analysis is provided in the FEMA Document Library

Pre-existing defects:

  • Puerto Rico was not an option for hurricane in Hazus 3.0. Risk MAP PTS Contractor RAMPP had developed coastline data (and hurricane data) for PR in 2013-2014 and delivered it to FEMA Region II. The expectation was that this data had been integrated into the Hazus 3.0 release
  • Users cannot create study regions that start with a number or are entirely numeric as the study region name (Such as a county FIPs or Watershed). For example, the name cannot be ‘12100201’ or ‘12County,’ but it can be named as ‘_12100301,’ ‘HUC12100301,’ or ‘County12’
  • Users cannot create study regions using state name abbreviation (i.e., CA, NY, DE)
  • Using the Hazus DEM download tool, when the window opens asking if you want to save the file, it opens up directly behind the DEM Extent window. We’ve encountered this using Chrome, Firefox and IE and in Windows 7 and 8.1. Be sure to move the window to see the download window
  • Hawaii Hurricane model is not functional due to code and data changes that are needed; this will be addressed with a patch after Hazus 3.0 release
  • Default Scenario Soil Type (D) is over ridden by the PGA/PGV Soil type; workaround – open current Scenario wizard and confirm all defaults; this will likely be addressed with a patch after Hazus 3.0 release

Useful Links

Hazus 2.2 (SP01)

Release Date: May 11, 2015

Hazus 2.2 SP01 was a service pack release of the software. The release contained one functional update to the Flood Model. Operating system and ArcGIS version compatibility is identical to that of Hazus 2.2, and no other functional changes were included for the Hurricane or Earthquake models. In addition to the software release, an updated version of the Hazus default data was also released concurrently with Hazus 2.2 SP01. The new default data included defect fixes to the current state data available for public download, and the addition of a dasymetric dataset for use in the Flood model. The new dasymetric state datasets will be available as a separate download on the MSC Hazus data download page; the non-dasymetric state datasets will henceforth be referred to as the homogeneous state data. Hazus 2.2 SP01 was deployed as a service pack through the auto-update tool built into Hazus. Users need only launch Hazus while connected to the internet and accept the automated patch installation to receive SP01. The updated homogeneous state data and the new dasymetric state data were released via the Map Service Center Hazus download webpage for free, public download. Note: Since the release of Hazus 3.0 in November of 2015, the dasymetric dataset has been made the default for Hazus, so users are no longer able to download two separate datasets on the Map Service Center. The homogeneous data tables are still present in the download and users can see the Hazus 3.0 User Release Notes to learn how to switch between the two datasets.

What Has Changed?

Users will notice the following changes to the Hazus Flood Module:

  • Study region aggregation at community level – Users can now aggregate their study regions at jurisdiction, tribal, or special use (such as townships) levels for study region aggregation in the Flood Module

Users will notice the following changes to the Hazus Earthquake Module:

  • No major functionality or visual changes were made to the Earthquake Module

Users will notice the following changes to the Hazus Hurricane Module:

  • No major functionality or visual changes were made to the Hurricane Module

Users will notice the following changes to the Hazus Shell and Utilities:

  • No major functionality or visual changes were made to the Hazus Shell or additional Utilities

Users will notice the following changes to the Hazus Datasets:

  • Dasymetric data is now available for download separately for use in the Flood Module. The download links will be available on the Hazus download page. (Note: the separate download feature for homogenous and dasymetric datasets has been discontinued as of the release of Hazus 3.0. All datasets are now included in one state download link, with both homogeneous and dasymetric datasets included in the download.)

Pre-existing defects:

  • When using dasymetric data, some essential facilities may fall outside the dasymetric block/analysis area due to geocoding errors in the source database for these facilities. Locations of individual facilities may be manually adjusted to correct this if desired. For assistance, please contact the Hazus Help Desk: hazus-support@riskmapcds.com 
  • When aggregating study regions at the block level using dasymetric data, an increase in aggregation time may be experienced. This includes only applies to study regions aggregated at the Community, or Watershed levels. Some of these study regions may require several hours to complete.
  • During testing of this service pack discrepancies between expected and observed loss values were noted when changing foundation types. The details and specific cause are being investigated and will be addressed with the next (Hazus 3.0) release later this year.
  • A latent defect exists in the Hazus flood model which prevents Hazus from appropriately determining whether a riverine or coastal damage function should be used for a user-defined facility (UDF) in a combined riverine-coastal scenario. In some instances when working with UDFs, an incorrect default function may be applied to an individual facility. Two workarounds are available:
    • Determine the correct function ID (3-digit unique identifier) from the damage function library according to the UDF characteristics, and whether a riverine or coastal hazard is being applied. Specify the function ID in the provided column within the UDF data entry window. Confirm the specific occupancy of the function matches that of the UDF
    • In the damage function library, search for the desired depth damage function. Select this function (selected function will display in green in the preview window above the list of functions). Selected functions will also appear highlighted in yellow on the Structure/Contents/Inventory summary tabs. Hazus will apply the selected functions to the UDF list. Confirm the specific occupancy of the function matches those of the UDFs

Useful Links

Hazus 2.2

Release Date: January 12, 2015

Hazus 2.2 was a full release of the software. The release contained identical functionality to Hazus 2.1, but is compatible with ArcGIS 10.2.2 and Windows 8. Compatibility with ArcGIS 10.0 and Windows XP will no longer be supported for Hazus 2.2. In addition to the software release, an updated version of the Hazus default data was also released concurrently with Hazus 2.2. The new default data was sourced primarily from Census 2010 data, and includes updated data for the General Building Stock (GBS) and other resources. Both Hazus 2.2 and the updated default data were released via the Map Service Center Hazus download webpage for free, public download. Upon deployment of Hazus 2.2 and the Census 2010 data, Hazus 2.1 and Census 2000 data was no longer available for download. To request a copy of Hazus 2.1 or previous versions of the software and/or data, please contact the FMIX at 1-877-FEMA-MAP or FEMAMapSpecialist@riskmapcds.com.

What Has Changed?

Users will notice the following changes to the Hazus Flood Module:

  • Changes to riverine hydraulics to make use of spatial computation changes in ArcGIS 10.2, such that reaches and depth grids are calculated similarly to Hazus 2.1
  • Changes to the Quick Look and Enhanced Quick Look functionality to ensure analysis completion
  • Updates to the Shelter and Agricultural parameters menus to allow full functionality in ArcGIS 10.2
  • Updates to the USGS DEM automated import, such that DEM import into Hazus is successful

Users will notice the following changes to the Hazus Earthquake Module:

  • Changes to the MapControl functionality to ensure proper display and usage of the ArcGIS mapping interface
  • Addition of primary key values for multiple, simultaneous layer editing
  • A number of key Earthquake data changes were made to use recent Environmental Impact Assessment (EIA) data; check out the User Release Notes for more information

Users will notice the following changes to the Hazus Hurricane Module:

  • New surface roughness coefficients were developed using NLCD 2011 LULC and tree canopy layers
  • Tree coverage data was updated using the 2013 USFS Forest Inventory Analysis (FIA) Database (for tree type, tree height, and maximum stems per acre), the 2011 NLCD tree canopy percentages (to reduce the stems per acre in non-forested LULC pixels), and 2013 US Census TIGER data (for tree collection factors)
  • NLCD 2001 was used for Hawaii, since this state was not included in NLCD 2006 or 2011 datasets
  • Probabilistic hurricane wind speeds were updated based on a new hurricane event set very similar to the model used to build the current ASCE 7 maps, but the new Hazus event set is based on a few more years of climatology data for storm genesis points, sea surface temperatures, and wind shear

Users will notice the following changes to the Hazus Shell and Utilities:

  • Hazus registry changed to recognize ArcGIS 10.2.2 startup process
  • Updates made to Crystal Reports to allow full report functionality on Windows 8 operating systems, and reflect Census 2010 data usage

Users will notice the following changes to the Hazus Datasets:

  • Demographic, boundary (county, tract, block), and GBS data updated based on Census 2010. Specific source data for each data type is available in the metadata files included with each state.
  • Dam data included in previous Hazus default data were removed due to new sensitivity requirements for critical infrastructure. This data will not be included in this release and is no longer publicly available.
  • Street lengths included in previous Hazus default were not updated and will not be included in this release.

Pre-existing Defects:

  • Quantitative results obtained using the Hazus 2.2 Flood module may vary slightly from results obtained in 2.1 due to minor changes made by Esri in 10.2 spatial computation methods.
  • Census blocks containing large percentages of water, which were removed from previous default Hazus data, will be included in this release.
  • Some state data contains default security settings of read-only. During state wide data update operation using CDMS, ensure that the state data file (*.mdb) has read-write permission enabled. Right click on the file to view properties. Verify that the attribute read-only is unchecked on the state data file. Repeat this for the user's TEMP folder.
  • Data topology settings within ArcGIS have changed between Census 2000 and Census 2010 data. Topology values in Census 2010 may not match those in Census 2000. These differences may result in slight gaps or overlaps between census boundary polygons. The scale of these discrepancies is minimal and is not expected to impact analysis.
  • Default mapping schemes for Iowa are incorrect; a correct version and instructions for replacement are available through the Hazus Help Desk
  • Default flood mapping schemes, census block types for flood, and entry NFIP dates are incorrect; a corrected version will be available to users in the near future 

Useful Links

Last Updated: 
06/01/2018 - 11:25