Successful floodplain planning requires an understanding of the implications of flooding on the community and development. Occasionally, this can be garnered from actual flood events, but more commonly, this understanding needs to come from computer hydraulic models, representing flood behaviour for a range of flood magnitudes.
Traditional deliverables from a flood modelling project include static “snapshots” of model results, taken at the peak of the flood as well as derived hydraulic parameters such as peak water levels, peak velocities, velocity times depth (VxD), and hydraulic hazards.
The limitation of such deliverables is that they do not provide the flexibility a planner requires to “slice and dice” the results, or to consider the complex combinations of hydraulic parameters required to adequately classify a floodplain or determine the affectation of flooding.
How a flood develops over time is also key to good planning outcomes. For example, does an area first become isolated prior to inundation?
waterRIDE™ FLOOD Manager (and Viewer) provide planners with dedicated tools for interrogating their full time-varying model results set from any model, in a live GIS system, a feature unique to the waterRIDE™ environment, irrespective of the users “flood modelling” skills or background.
Sophisticated processing tools such as exporting smoothed flood extents, determining flood planning areas (flood sensitive areas) as the defined flood plus freeboard, and automatically generating flood certificates are designed to make it easier for planners to use model results!
Some of the capability available in waterRIDE™ that is applicable to Planners includes:
Thematic Flood Surfaces – a library of design flood surfaces at your fingertips. Readily interrogate terrain, water level, depth, velocity, VxD, hazard, Froude and shear at any location in the model, across the full flood hydrograph!
Single Interface – interrogate any of your model results with the convenience of a single interface
GIS Backdrop – enhance your understanding of the model results using rich and familiar GIS datasets as backdrops.
Flood Extents – rapidly generate GIS flood extents for ready identification of flood affected properties and exporting to any GIS package, with sophisticated smoothing options.
Floodway, Flood Storage, Flood Fringe – Boolean logic queries allow you to identify zones where velocity and depth meet certain criteria to assist with definition of floodways, flood storage areas and the flood fringe
GIS Integration – easily populate GIS layers with data from your model results (such as translating peak flood levels and flood hazard to land parcels), or use your GIS data in conjunction with the model results to calculate values such as depth of over floor flooding.
Flood Planning Level – automatically add a buffer to peak flood levels to derive a flood planning surface (or flood sensitive areas surface), readily showing those properties within the flood planning zone and the required minimum floor levels.
Seamless Integration of Multiple Surfaces – Create a seamless surface representing, say, the maximum 100yr design flood level across all flooding mechanisms (eg storm surge, riverine flooding and overland flow).
Metadata – tag all of your model results with additional information (such as source report, results date, comments etc) for quality assurance purposes.
Quality Assurance – common interface to interrogating any flood model, ensuring consistent interpretation of model results.
Automated Flood Certificates – setup a system to automatically prepare flood certificates
Share Flooding Data – share flooding information across the organisation in a quality controlled, “view only” manner with waterRIDE™ FLOOD Viewer.
Property Photos – integrate flood levels with scaled property photos to provide a realistic representation of flooding at an individual property and greatly enhance community flood awareness and understanding
Difference Mapping – clearly view the impact of proposed developments, flood mitigation options or climate change scenarios through difference mapping. The surfaces do not even need to be on the same framework (eg you could prepare a difference surface between the new 2D model results and the old 1D model results!).