WMS:Differences From Earlier Versions (Version 6.0 and earlier): Difference between revisions

From XMS Wiki
Jump to navigationJump to search
No edit summary
No edit summary
Line 9: Line 9:
*User can specify [[WMS:Flow Paths and Barrier Coverages|flood barriers as features in the flood barrier coverage]] and the new method incorporates those features during flood depth computation.  
*User can specify [[WMS:Flow Paths and Barrier Coverages|flood barriers as features in the flood barrier coverage]] and the new method incorporates those features during flood depth computation.  


*Computed flood depths are stored as TIN data set and saved along with the TIN.  
*Computed flood depths are stored as TIN dataset and saved along with the TIN.  


*Multiple flood depth data sets can be created in a TIN from multiple events.
*Multiple flood depth datasets can be created in a TIN from multiple events.


*In addition to displaying flood depth as contours, this method can also create flood extent and [[WMS:Flood Depth Map|classified flood depth coverage]].  
*In addition to displaying flood depth as contours, this method can also create flood extent and [[WMS:Flood Depth Map|classified flood depth coverage]].  

Revision as of 19:54, 4 March 2013

The new method differs from the previous method in several aspects. The locations of water levels and their section criteria for interpolation are more flexible than the previous method. Ability to incorporate user defined flood barriers as coverage provides an excellent opportunity to overcome the limitations inherent in digital terrain models. It also becomes useful in evaluating “what if” or post project scenarios. The new method provides several options to present flood depth data that are not available in the older method. In addition to conceptual and computational differences between two methods, you will also notice following changes while using the new method:

  • The method does not require “streams” in the TIN.
  • Multiple events or water level time series can be read as oppose to a single event. User can choose an event while delineating floodplain.
  • Computed flood depths are stored as TIN dataset and saved along with the TIN.
  • Multiple flood depth datasets can be created in a TIN from multiple events.
  • Finally flood extent, classified flood depth, and flood impact coverages can be exported as shapefiles for reporting or other flood management purposes.


Related Topics