Difference between revisions of "SMT201 AY2019-20G2 EX2 Kim Chang Heon"

From Geospatial Analytics for Urban Planning
Jump to navigation Jump to search
Line 26: Line 26:
 
{| align=center width = 100%
 
{| align=center width = 100%
  
| style="text-align:justify; width:20em; height: 1em; font-size:17px; font-family: Times New Roman !important; background-color:White; color: black;"| .
+
| style="text-align:justify; width:20em; height: 1em; font-size:17px; font-family: Times New Roman !important; background-color:White; color: black;"| By clipping the buildings layer provided by OSM with the subzone planning area of Gombak, the layer containing only the buildings within the Gombak planning area was achieved. From there, by using the symbology function in QGIS, buildings with different uses were classified to achieve the output map on the top left.
 
|}
 
|}
  
Line 40: Line 40:
 
{| align=center width = 100%
 
{| align=center width = 100%
  
| style="text-align:justify; width:20em; height: 1em; font-size:15px; font-family: Times New Roman !important; background-color:White; color: black;"| Roads.
+
| style="text-align:justify; width:20em; height: 1em; font-size:15px; font-family: Times New Roman !important; background-color:White; color: black;"| First, road data from OSM was clipped with the Gombak planning subzone area. Then, only the roads that were Service and Track roads were selected using attribute tables, and then exported into the geopackage as a new layer. This layer was then classified into Track (purple) and Service (green) roads separately as shown in the bottom left map using symbology.
 
|}
 
|}
  
Line 56: Line 56:
 
{| align=center width = 100%
 
{| align=center width = 100%
  
| style="text-align:justify; width:20em; height: 1em; font-size:17px; font-family: Times New Roman !important; background-color:white; color: black;"| .
+
| style="text-align:justify; width:20em; height: 1em; font-size:17px; font-family: Times New Roman !important; background-color:white; color: black;"| Similar to the past 2 maps, the OSM data was clipped with the planning boundary of Gombak, and then classified using symbology. Attribute table was checked to see if the natural features consisted of forests, parks and water bodies.
 
|}
 
|}
  
Line 69: Line 69:
 
{| align=center width = 100%
 
{| align=center width = 100%
  
| style="text-align:justify; width:20em; height: 1em; font-size:17px; font-family: Times New Roman !important; background-color:white; color: black;"| .
+
| style="text-align:justify; width:20em; height: 1em; font-size:17px; font-family: Times New Roman !important; background-color:white; color: black;"| Using the elevation data provided during lessons (ASTER GDEM), the Raster function 'Clip Raster by Extent' was used with the extent of Gombak's planning area. The output pixel size was set to 30 by 30 meters as it was the limitation of the data provided. This resulted in the map in the bottom right, which depicts the elevation of Gombak.
 
|}
 
|}

Revision as of 16:47, 9 November 2019

OVERVIEW PROXIMITY MAPS CRITERION SCORES AHP RECOMMENDATION
Map Layout View of basic features


BUILDINGS
By clipping the buildings layer provided by OSM with the subzone planning area of Gombak, the layer containing only the buildings within the Gombak planning area was achieved. From there, by using the symbology function in QGIS, buildings with different uses were classified to achieve the output map on the top left.



ROADS
First, road data from OSM was clipped with the Gombak planning subzone area. Then, only the roads that were Service and Track roads were selected using attribute tables, and then exported into the geopackage as a new layer. This layer was then classified into Track (purple) and Service (green) roads separately as shown in the bottom left map using symbology.



NATURAL FEATURES
Similar to the past 2 maps, the OSM data was clipped with the planning boundary of Gombak, and then classified using symbology. Attribute table was checked to see if the natural features consisted of forests, parks and water bodies.


DIGITAL ELEVATION MODEL
Using the elevation data provided during lessons (ASTER GDEM), the Raster function 'Clip Raster by Extent' was used with the extent of Gombak's planning area. The output pixel size was set to 30 by 30 meters as it was the limitation of the data provided. This resulted in the map in the bottom right, which depicts the elevation of Gombak.