Download pdf - Developing A Stormwater Asset Inventory A …ngis.mygeoportal.gov.my/sites/default/files/Media/ngis4/...INSPIRING CREATIVE & INNOVATIVE MINDS Developing A Stormwater Asset Inventory

INSPIRING CREATIVE & INNOVATIVE MINDS

Developing A Stormwater Asset Inventory

– A Practical Experience In Implementing

MS 1759

By

Assoc Prof Sr Mohamad Nor Said1

Mohamad Ghazali Hashim1

Kamarul Azlan Mohd Nasir2

1 Faculty of Geoinformation Science & Engineering2 Faculty of Civil Engineering

Universiti Teknologi Malaysia

28 June 2010


Outline

Background

Stormwater Asset Inventory

Feature & Attribute Coding

Issues

Suggestions

Conclusion


Background

Natural Disaster: A Lesson For Future

Development Planning

• Development patterns greatly impact the

existence & function of natural systems;

e.g. rivers

• Destruction can pose risks to life and

property & greatly increase the cost of

development

• Johor flooding (Dec 2006 & Jan 2007)

• public facility damages: RM 1.5 billion

• Iskandar Malaysia - downfall: 350mm

(2006); 400mm (2007)

• Very important to understand the

interrelationship of urbanization and

natural, economic and cultural resources

• Many agencies are now very concerned on

how to deal with stormwater in a manner

which is healthier, safer, and more in

balance with the natural environment


Background

Stormwater Asset Inventory

Part of (core component) JPS’s ‘Detailed

Design of Stormwater Management

Facilities’ projects:

- Senai; Kulai; Pandan; Tmn Anggerik;

Buntan; Rinting

Mainly to tackle flash floods

A similar development for ‘Flood Mitigation

Master Plan Study For WPI’ (Iskandar

Malaysia):

- Sg Skudai, Sg Pulai, Sg Pendas, Sg

Melayu, Sg Masai, Sg Kim Kim, Sg Kong

Kong

To develop using GIS

To conform/ comply with MS 1759 : 2004

Assets:- Waterways: rivers/ drains

- Structures: bridges; culverts; weirs; tidal

gauge; barrage; garbage traps; drop

structures; outfalls; sewage treatment plants

(STP)


Background


Background


Background

Stormwater Management For Healthier, Safer & More Balanced

With Natural Environment


Stormwater Assets

River Feature: Inland Water

A relatively large natural stream of water

Associated Attributes:

• Structure (Riverbank Protection Type)

• Reserve

Drain Feature: Inland Water

A channel that carries away storm water

to control flooding

Associated Attributes

• Category (e.g. main; roadside)

• Structure (e.g. outfall; culvert)

• Usage (flood mitigation)


Stormwater Assets

Bridge Feature: Land Transportation

A structure erected over a depression or an

obstruction such as river, road or railway and

having a passageway which allows traffic to cross

from one side to the other

Associated Attributes: • Crossing Category (Road/ Railway/ Pedestrian)

• Material

• Abutment Type

• Size (width/ length)

Bridge – Railway Crossing

Bridge – Road Crossing

Bridge – Pedestrian Crossing


Stormwater Assets

Culvert Feature: River Structure

A transverse drain or waterway structure that

crosses beneath a road, railway, canal or through

an embankment by means of a pipe or enclosed


• Material

• Geometry Type

• Size


Stormwater Assets

Outfall Feature: Shoreline Structure

A structure extending into a body of water for

the purpose of discharging sewage, storm

runoff, or cooling water


• Source (e.g. residential; industrial;

oxidation pond)


Stormwater Assets

Weir Feature: River Structure

A barrier constructed to control the flow or

raise the level of water

Pond Feature: Inland Water

An open body of water smaller than a lake

which is either naturally formed or man

made


• Type (e.g. detention; wastewater/

oxidation)


Stormwater Assets

Sewage Treatment Plant Feature: Sewerage

Site that contains facilities for treating

sewage

May introduce outfall into river


• Type (e.g. communal septic tank;

oxidation pond)


Stormwater Assets

Trap Boom (Garbage Trap) Feature: River Structure

Barrier across a river in an urban area to

trap floating rubbish for collection and

disposal


• Type (e.g. screen)


MS 1759: 2004

MS 1759

• Provides specification: data producers and

users may exchange digital spatial data

• Minimize duplication of effort in database

development

• Describes encoding of real world: in terms

of features and attributes

• Features - real world objects; attributes –

properties/ characteristics associated with

objects

• 12 feature categories:1. Aeronautical

2. Built Environment

3. Demarcation

4. Geology

5. Hydrography

6. Hypsography

7. Soil

8. Transportation

9. Utility

10. Vegetation

11. Special Use (Dataset Specific)

12. General


Example of Feature Code (1):

Inland Water HH0040 - River

Example of Feature Code (2):

River Structure HJ0020 – Riverbank Protection

MS 1759 – Organization of Feature & Attribute Codes

Example of Attribute Code:

Riverbank Protection Type (RPT)

MS 1759: 2004

Major Category

Subcategory


MS 1759 – Example of Coding River Structure (1)

Example: Riverbank Protection Type (RPT)

Example: River Structure HJ0020 – Riverbank Protection

Example: Riverbank Protection Type (RPT)

MS 1759: 2004


ExampleFeature : Bridge

Feature Category : Transportation (T)

Feature Sub-Category : Land (TA)

Feature Code : TA0240

Attribute Code : BAT 2 [Bridge Abutment Type = Retaining Wall]

MS 1759: 2004

MS 1759 – Example of Coding River Structure (2)


Methodology

Preliminary Study• Site Investigation

Database Design• Identification of Map Layers

• Recognition of Attributes – Coded &

Non-coded Attributes

• Creation Of Master Data List

Database Development• Compilation and Conversion of

Existing Data

• Field Data Verification and Collection

• Coordinate Transformation

• Attribute (Non-coded) Data Entry

Feature Coding • Code Assignment (Entry): Feature &

Attribute Codes

Development of Stormwater Asset Inventory



River Catchment – e.g. Sg Senai

The Use of Aerial Photograph

– e.g. Anak Sg Skudai (Senai)



Field Data Collection/ Updating/ Verification



The Inventory Database

Main Datasets Rivers (banks)

Drain (open/ covered)

Bridges (roads/ railways/ abutment)

Culverts (single/ double/ circular/ box)

Weir

Barrage

Tidal Gate

Garbage Trap

Sewage Treatment Plant (STP)

Outfalls (source)

Pond (detention/ wastewater)

Other (Supporting) Datasets Catchment boundary

Landuse (e.g. residential, commercial,

industrial, agricultural)

Roads (main and local)

Highways

Railway



Data Sources

Existing topographic maps (hard &

digital copies)

Aerial photographs

Google Earth satellite images

Surveyed detailed drawings

JPBD’s local plan

Global Positioning System (GPS)




Stormwater Feature & Attribute Codes



Supporting Datasets: Feature & Attribute Codes



Supporting Datasets: Feature & Attribute Codes





Issues

Currency of Data

• Features may have changed in

position due to development

• How frequent checking is or

supposed to be made

• As-built data should be made

available for database updating

• Any maintenance should be

recorded – and hence database

updated

• Effect: feature & attribute codes;

previously ‘earth drain’ could

have now been ‘concrete drain’


Issues

Identification/ Recognition of Features

• Textual description sometimes does not

provide clear definition; photograph/

picture may help

• Ordinary GIS operators may not be able

to accurately code certain features; may

be better done or assisted by hydrology

experts

• Example: ‘drop structure’

“a manmade structure, typically small and built on

minor streams, to pass water to a lower elevation

while controlling the energy and velocity of the

water as it passes over”

• Some features not in the list – needs

regular revision of MS document

Drop Structure


Issues

Feature Representation

• A particular reference to linear

features

• Single versus double line – e.g.

different protection types of

riverbank sides

- One side: Concrete/ Well guard

- Another side: Non-protected/

Earth

• Creation of different records (two

lines instead of one) will introduce

error in measurement (e.g.

summation of length of a river)

Concrete/ Well Guard

Non-Protected/ Earth


Issues

Confusion In Feature Category

• A particular reference to Landuse dataset

• Demarcation vs Transportation

• E.g. Road Reserve Area (Demarcation) vs Road (Transportation)

Case 1: Feature seen as a land area for road (Road Reserve)

Category: Demarcation

Case 2: Feature seen as usage (Road)

Category: Transportation


Issues


Issues

Confusion In Feature Sub-Category

• Inland Water (HH) vs River Structure (HJ)

• Example:

- A river is classified as an Inland Water Sub-

Category (coded as HH0040)

- When riverbank is to be coded, the sub-

category has to be River Structure (coded

as HJ0020)

- A river segment cannot have two feature

codes


Issues

Attribute Codes May Be Redundant

• Feature code already represents a particular attribute

• Example:

- Category: Built Environment

- Feature Code: BA0010 (Residential Building)

- Attribute Code: ZOC 1 (Zoning Category: Residential)


Suggestions

Feature definition to be made both in textual & pictorial

forms – to help users more accurately recognizing the

features

The MS should be made more flexible to cater for a general

mapping purposes as opposed to more detailed ones;

Example:

1. general landuse map (with attribute of landuse category)

2. a more detailed/ specific landuse (e.g. residential

building with its own attributes)

Review for any duplication between Feature Code and the

Attribute Code of a particular feature

Produce a standard template of database schema for a

particular application (e.g. one for JPS, JPBD, etc.)


Conclusion

Enforcing consultants to develop geospatial feature

inventory (with MS1759 compliance) as part of project TOR

is one (right) way to implement standard feature coding

Accurate feature identification/ recognition is very important

to ensure the reliability of assigned codes – field (hands-on)

experience is advantageous

Inclusion of feature characteristics (as detailed out in MS

1759 guideline) in surveyor’s detailed drawing helps;

surveyors should be made aware and play more roles

A thorough study may be necessary to investigate various

issues related to practical implementation of MS 1759

Issue on data currency should be parallelly resolved to

ensure the integrity of the database (that comes with feature

and attribute codes)


Thank You…