where the discharge data was gathered going down to
the outlet of the river. Once done, the generated river
digital plot in Keyhole Markup Language (KML) file
format was converted to a vector file.
2.2 Preprocessing
In generating the flood model, the LiDAR DEM and
the river digital plot were prepared for processing the
physical features of the river. The LiDAR DEM was
initialized as the elevation data while the river digital
plot was used to define the extent of the river. The
digitized river lines were grouped into river data,
containing the centerline, River banks data,
containing the left bank and right bank, and flowpaths
data, containing the right flow path, left flow path,
and centerline of the river. The river centerline was
assigned with a river code and a reach code to provide
a name for the river. To define the flow direction of
the river, each paths from the flowpaths data were
assigned whether a right flow path, a left flow path,
or a channel path. Using the LiDAR DEM as terrain
and the river data as the centerline of the stream, the
stream profile was generated to extract the changes in
elevation along the river channel from upstream to
downstream locations.
After generating the geometric attributes along the
rivercenterline, the construction of the cross-section
cutlines followed. Each cross-section cutline
represents a station in the river where the data for the
one-dimensional flood simulation was based on.The
initial set of cross-section cutlines were uniformly
distributed along the river centerline. Furthermore,
these were adjusted so that there were no lines
intersecting another line and that they have crossed a
river bank only once. This was to avoid the
overlapping of flood inundation among stations.
Having the river data as the centerline of the stream,
LiDAR DEM as terrain, and cross-section cutlines,
the cross-section cutline profile was generated to
extract the elevation data across the river in each
station. In preparation for the export of the GIS data
for HEC-RAS modeling, the generated datasets were
initialized including the terrain, centerline of the
stream, cross-section cutlines, cross-section cutline
profiles, bank lines, flow path, and stream profiles.
2.3 Flood Modeling
The previously generated GIS Data in flood model
preprocessing was converted into geometric data with
a metric system of Système international d'unités or
SI. The Manning’s n values were supplied and Cross
Section Point Filter was set in the process to initialize
the roughness value and reduce the elevation data
points that can be processed by HEC-RAS model for
each river station, respectively. For the simulation,
unsteady flow were used in utilising the discharge
data and simulated 5, 25, and 100 Year Rain Return
hypothetical scenarios of the target river. On the other
hand, a friction slope value of 0.001 was set. Once all
the previous parameters were set properly,
computation of unsteady flow simulation followed.
Afterwards, the result of the flood model simulation
was produced. Lastly, generation of a flood
inundation was done.
2.4 Identifying Flood Prone
Communities
The 5, 25, and 100 Year flood inundation maps that
were generated were overlaid to the feature extracted
vector files of Padada floodplain to identify the flood
prone communities. These were done in ArcMap
10.2.2.
3 RESULTS AND DISCUSSION
The digitization of the river digital plot started from
Diversion Bridge (06°40’35.4”N, 125°19’47.9”E).
The LiDAR elevation datasets used in preprocessing
the RAS Model has a 1-meter resolution with 20cm
vertical accuracy and is covering the Padada
floodplain as in Figure 3. For the development of the
model, the discharge data used was gathered in the
same bridge with a base flow discharge of 3.35 m
3
/s
and was specifically set as input as the normal flow
of Padada River.
Figure 3: LiDAR Coverage of Padada River floodplain.
Riverbed cross-sections or the XS-Cutlines of the
target watershed are crucial in the setup of HEC-RAS