<?xml version="1.0" encoding="UTF-8"?>
<record
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://www.loc.gov/MARC21/slim http://www.loc.gov/standards/marcxml/schema/MARC21slim.xsd"
    xmlns="http://www.loc.gov/MARC21/slim">

  <leader>02920ntm a2200277 a 4500</leader>
  <controlfield tag="001">vtls000102622</controlfield>
  <controlfield tag="003">KUKTEM</controlfield>
  <controlfield tag="005">20251117113359.0</controlfield>
  <controlfield tag="008">171226s2017    my dab f am   000 0 eng d</controlfield>
  <datafield tag="020" ind1=" " ind2=" ">
    <subfield code="a">THE0000229(Local)</subfield>
  </datafield>
  <datafield tag="039" ind1=" " ind2="9">
    <subfield code="a">201905141453</subfield>
    <subfield code="b">nazirah</subfield>
    <subfield code="y">201712261008</subfield>
    <subfield code="z">saini</subfield>
  </datafield>
  <datafield tag="040" ind1=" " ind2=" ">
    <subfield code="a">UMP</subfield>
  </datafield>
  <datafield tag="090" ind1=" " ind2=" ">
    <subfield code="a">FKASA .A35 2017 r Bc.</subfield>
  </datafield>
  <datafield tag="100" ind1="0" ind2=" ">
    <subfield code="a">Adilah Nurain Ahmad</subfield>
  </datafield>
  <datafield tag="245" ind1="1" ind2="0">
    <subfield code="a">Comparison of watershed boundaries delineation for Kuantan River Basin /</subfield>
    <subfield code="c">Adilah Nurain Ahmad</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="a">Kuantan, Pahang :</subfield>
    <subfield code="b">UMP,</subfield>
    <subfield code="c">2017</subfield>
  </datafield>
  <datafield tag="300" ind1=" " ind2=" ">
    <subfield code="a">xii, 66 p. :</subfield>
    <subfield code="b">ill. (some col.), charts ;</subfield>
    <subfield code="c">30 cm. +</subfield>
    <subfield code="e">1 CD-ROM</subfield>
  </datafield>
  <datafield tag="500" ind1=" " ind2=" ">
    <subfield code="a">Faculty of Civil Engineering and Earth Resources</subfield>
  </datafield>
  <datafield tag="502" ind1=" " ind2=" ">
    <subfield code="a">Project Paper (Bachelors of Civil Engineering) -- Universiti Malaysia Pahang &#x2013; 2017</subfield>
  </datafield>
  <datafield tag="504" ind1=" " ind2=" ">
    <subfield code="a">Bibliography : p. 63-66</subfield>
  </datafield>
  <datafield tag="520" ind1="3" ind2=" ">
    <subfield code="a">Watershed also known as river basin is a part that covered every piece of land on the Earth because of water always moves off land to downstream point where it collects in a water body. Additionally, watershed modelling is an important step in preparation of data for modelling. This study is to delineate watershed boundaries using 3 different Digital Elevation Models (DEMs) and evaluate the accuracy of watershed boundaries derived from 3 difference sources for Kuantan River Basin. The software that was used to delineate watershed boundaries is Geographical Information System (GIS), ArcGIS version 10.2. The data was derived from 3 different DEMs, Shuttle Radar Topography Mission (SRTM) which consist two resolutions that is 1 arc-second (30-m) resolution and 3 arc-second (90-m) resolution and Advanced Spaceborne Thermal Emission and Reflection Radiometer (ASTER) with (30-m) resolution. Next the analysis is done by using Euclidean Distance in ArcGIS to obtain the differences in distance between DEMs boundaries and manual boundaries (DID). The result will be compared with the Kuantan River Basin that retrieved from Department of Irrigation and Drainage (DID). From the analysis, SRTM-30 m data have several advantages such as provide important fundamental data for topographic analysis in many fields. Not only that, it has the highest resolution topographic dataset ever produced for the Earth&#x2019;s land surface. As for SRTM-90 m, it has a slight different from SRTM-30 m due to the different in resolution. Meanwhile, ASTER data has higher spatial resolution and wider coverage than the SRTM-30 m but have negative bias toward flat region. Thus, the accuracy of watershed boundaries derived from 3 different sources depends on the accuracy of the Digital Elevation Model (DEM) will be discuss in this paper.</subfield>
  </datafield>
  <datafield tag="610" ind1="2" ind2="0">
    <subfield code="a">Faculty of Civil Engineering and Earth Resources</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Universities and Colleges</subfield>
    <subfield code="x">Dissertations</subfield>
  </datafield>
  <datafield tag="650" ind1=" " ind2="0">
    <subfield code="a">Theses</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2019-09-04</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">FKASA .A35 2017 r Bc.</subfield>
    <subfield code="p">0000120844</subfield>
    <subfield code="r">2019-09-04 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2019-09-04</subfield>
    <subfield code="y">PSM</subfield>
  </datafield>
  <datafield tag="952" ind1=" " ind2=" ">
    <subfield code="0">0</subfield>
    <subfield code="1">0</subfield>
    <subfield code="4">0</subfield>
    <subfield code="7">1</subfield>
    <subfield code="a">10000</subfield>
    <subfield code="b">10000</subfield>
    <subfield code="d">2019-09-04</subfield>
    <subfield code="l">0</subfield>
    <subfield code="o">CD 10968 | FKASA .A35 2017 r Bc.</subfield>
    <subfield code="p">0000120845</subfield>
    <subfield code="r">2019-09-04 00:00:00</subfield>
    <subfield code="t">1</subfield>
    <subfield code="w">2019-09-04</subfield>
    <subfield code="y">PSM</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="a">VIRTUA40</subfield>
    <subfield code="c">7687</subfield>
    <subfield code="d">7693</subfield>
  </datafield>
  <datafield tag="999" ind1=" " ind2=" ">
    <subfield code="a">VTLSSORT0080*0200*0400*0900*1000*2450*2600*3000*5000*5020*5040*5200*6100*6500*6501*9992</subfield>
  </datafield>
</record>
