Changeset 2735
- Timestamp:
- Apr 20, 2006, 4:42:33 PM (18 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
inundation/report_generation/report_fesa_project_v1.tex
r2703 r2735 17 17 \usepackage{lscape} %landcape pages support 18 18 %\input{definitions} 19 20 \title{Tsunami impact modelling for NW shelf}19 %\paperwidth 20 \title{Tsunami impact modelling for the NW shelf} 21 21 \date{} 22 22 … … 42 42 understand impact and risk to tsunami hazard. 43 43 44 The current results represent ongoing work and may change in the future.45 44 46 45 The software tool, ANUGA, has been used to develop the inundation extent … … 49 48 wave equation using the finite volume technique (described in [1]). 50 49 An advantage of this technique is that the cell resolution can be changed 51 according to areas of interest. 52 53 The following set of information is necessary input to undertake the tsunami 54 impact modelling. 50 according to areas of interest. ANUGA is under constant development and 51 validation investigations. As such, the current results represent ongoing work 52 and may change in the future. 53 54 The following set of information is required input to undertake the tsunami 55 impact modelling and will be discussed in following sections. 55 56 56 57 \begin{itemize} … … 60 61 \end{itemize} 61 62 63 The inundation results for the two scenarios are described in section \ref{sec:results}. 64 62 65 \section{Data sources} 66 \label{sec:data} 63 67 64 68 The runup height and resulting inundation ashore is determined by the input 65 topographic and bathymetric data, the forcing terms as well as the initial 66 and boundary conditions. It would be ideal if the data adequately captures 67 all complex features of the underlying bathymetry and topography. 68 69 What can we say about the data used here? How happy? 70 69 topographic and bathymetric data, the forcing terms, the initial 70 and boundary conditions, as well as the cell resolution. 71 It would be ideal if the data adequately captures 72 all complex features of the underlying bathymetry and topography and that 73 the cell resolution be commensurate with the underlying data. Errors in any of 74 these areas will affect the accuracy of the final model result. 75 76 A number of sources have supplied data for these two studies. With respect to the 77 onshore data, the Defence Imagery and Geospatial Organisation (DIGO) supplied the 78 DTED (Digital Terrain Elevation Data) Level 2 data which 79 has been authorised for Australian Tsunami Warning System use only. This data has a resolution of 80 1 second (about 30 metres), produced from 1:50 000 contours, elevations and drainage. 81 The Department of Land Information (DLI) has provided a 20m DEM and orthophotography 82 covering the NW Shelf. This data set is not bare earth and as a result, we have 83 chosen to use the 30m DTED Level 2 data due to its bare earth thingo. 84 85 With respect to the offshore data, the Department of Planning and Infrastructure have provided 86 state digital fairsheet data around Onslow. 87 This data covers only a very small geographic area. 88 (Note, similar data has also been provided for Broome.) 89 The Port Hedland Port Authority has provided digital data from a multibeam survey of the 90 Port Hedland channel. The Australian Hydrographic Office fairsheet data has also been utilised. 91 92 The coastline has been generated from the DIGO DTED2 and modified using the aerial photography and the two detailed 93 surveys provided by WA Department of Planning and Infrastructure. The extent of the data used 94 for the tsunami impact modelling can be seen in the following two figures. 95 96 \begin{figure}[hbt] 97 98 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 99 100 \caption{Data extent for Onslow scenario} 101 \label{fig:onslow_area} 102 \end{figure} 103 104 \begin{figure}[hbt] 105 106 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 107 108 \caption{Data extent for Pt Hedland scenario} 109 \label{fig:pt_hedland_area} 110 \end{figure} 111 112 113 In summary, 114 115 116 \begin{tabular}{|l|l}} \hline 117 Data & Detail \hline 118 DIGO DTED Level 2 DIGO & Onshore, 1 second (\approx 30m) \hline 119 DLI & Onshore, 20m DEM and orthophotography \hline 120 DPI & Offshore, fairsheet data around Onslow \hline 121 Pt Hedland Port Authority & offshore, digital multibeam survey \hline 122 123 \end{tabular} 124 125 126 What can we say about the data used here? How happy? Need to put in some words 127 here from Hamish on the data - any issues etc. 128 Do we have to combine any data? If so, comment. 129 130 %\input{data_issues} 71 131 72 132 \section{Tsunami scenarios} 73 74 \begin{figure}[hbt] 75 76 %\centerline{ \includegraphics[width=75mm, height=75mm]{examples/.eps}} 133 \label{sec:tsunami_scenarios} 134 135 need to say something about the event, i.e. Mw 8.5 event initiated along the 136 Java Trench (get from David) 137 138 \begin{figure}[hbt] 139 140 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 77 141 78 142 \caption{Source zones of influence} … … 81 145 82 146 83 84 147 \section{Inundation modelling results} 85 86 Do we have to combine any data? If so, comment. 87 %\include{interpretation.tex} 88 \begin{figure}[hbt] 89 90 %\centerline{ \includegraphics[width=75mm, height=75mm]{examples/.eps}} 148 \label{sec:results} 149 150 To initiate the modelling, the computational mesh is constructed to cover the available data. 151 The resolution is chosen to balance computational time and desired resolution in areas of interest, 152 particularly in the interface between the on and offshore. 153 The following series of figures illustrate the study extent for the two 154 scenarios and the resulting computational mesh, highlighting areas of 155 refinement around areas of particular interest. 156 157 \begin{figure}[hbt] 158 159 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 91 160 92 161 \caption{Study area for scenario 1: Onslow} … … 94 163 \end{figure} 95 164 96 \begin{figure}[hbt] 97 98 %\centerline{ \includegraphics[width=75mm, height=75mm]{examples/.eps}} 165 166 \begin{figure}[hbt] 167 168 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 99 169 100 170 \caption{Computational mesh for Onslow study area} … … 104 174 \begin{figure}[hbt] 105 175 106 %\centerline{ \includegraphics[width=75mm, height=75mm]{ examples/.eps}}176 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 107 177 108 178 \caption{Study area for scenario 2: Pt Hedland} … … 110 180 \end{figure} 111 181 112 \begin{figure}[hbt] 113 114 %\centerline{ \includegraphics[width=75mm, height=75mm]{examples/.eps}} 182 183 \begin{figure}[hbt] 184 185 %\centerline{ \includegraphics[width=75mm, height=75mm]{figures/.eps}} 115 186 116 187 \caption{Computational mesh for Pt Hedland study area} … … 118 189 \end{figure} 119 190 120 Time series at relevant gauge locations - INSERT RESULTS HERE ( insert generated 121 latex file) 122 191 %\input{interpretation} 192 193 194 \input{tex_output_test} 123 195 124 196 \section{Summary}
Note: See TracChangeset
for help on using the changeset viewer.