31a4ced78352444196fa54f9c47729fb

STANDARDS AND SPECIFICATIONS FOR PLANNING DATA SUBMISSION
(PLOT, ROADS, TRANSIT & SERVICE CORRIDORS)
) (
VERSION 1.0
DECEMBER 2013
TABLE OF CONTENTS
Chapter Page
ACRONYM & ABBREVIATION .................................................................................... iii LIST OF TABLES ....................................................................................................... iv LIST OF FIGURES ...................................................................................................... v 1. INTRODUCTION................................................................................................... 1 2. PURPOSE ............................................................................................................ 2 3. LIST OF DOCUMENTS ......................................................................................... 3 4. CAD SPECIFICATIONS ........................................................................................ 5 4.1 4.2 4.3 4.4 4.5 4.6 4.7 Electronic File Format ....................................................................................... 5 File Naming ....................................................................................................... 5 Scale and Units ................................................................................................. 6 Drawing Coordinates......................................................................................... 7 AutoCAD Block Attributes ................................................................................. 8 Title block .......................................................................................................... 8 Drawings Layers ............................................................................................... 9
4.7.1. DWG File: Plot ............................................................................................. 10 4.7.2. DWG File: Roads......................................................................................... 10 4.7.3. DWG File: ServiceCorridor .......................................................................... 11 5. DATA CAPTURING RULE................................................................................... 12 6. ATTRIBUTE BLOCKS ......................................................................................... 14 6.1 DWG File: Plot ................................................................................................ 14
6.1.1 Plot .............................................................................................................. 14 6.1.2 Sector .......................................................................................................... 14 6.1.3 Zone ............................................................................................................ 15 6.2 DWG FILE: ROADS ........................................................................................ 16
6.2.1 RoadCentreLine .......................................................................................... 16 6.2.2 Road Edge .................................................................................................. 17 6.2.3 RoadEntrance.............................................................................................. 18

Standards & Specifications For Planning Data Submission (Plot, Roads & Service Corridors) Version 1.0 Department of Transport, Abu Dhabi, Integrated Planning Division Page i
6.2.4 Parking Area ................................................................................................ 19 6.2.5 Road Layby ................................................................................................. 20 6.2.6 Road Hump ................................................................................................. 21 6.2.7 Foot Bridge .................................................................................................. 22 6.2.8 Road Tunnel ................................................................................................ 23 6.2.9 Bridge .......................................................................................................... 24 6.2.10 6.2.11 6.2.12 6.2.13 6.2.14 6.2.15 6.2.16 6.2.17 6.2.18 6.3 Underpass ............................................................................................... 25 Parking Space.......................................................................................... 26 Pavement Detail ....................................................................................... 27 Landscape Area ....................................................................................... 28 Road Marking........................................................................................... 29 Road Shoulder ......................................................................................... 30 Road Arrow .............................................................................................. 31 Transit ...................................................................................................... 32 Inventory Signal ....................................................................................... 33
DWG FIle: SERVICES .................................................................................... 34
6.3.1 Service Corridor........................................................................................... 34 6.3.2 Reserved Strip ............................................................................................. 35 APPENDIX 1: DOT REFERENCE DATA COLLECTION PROCESS............................ 37
Standards & Specifications For Planning Data Submission (Plot, Roads & Service Corridors) Version 1.0 Department of Transport, Abu Dhabi, Integrated Planning Division
Page ii
ACRONYM & ABBREVIATION

ACRONYM / ABBREVIATION
DOT ADM TPS SDD DWG UPD CDP CPD GIS CAD QC
MEANING
Department of Transport Abu Dhabi Municipality Town planning Sector Spatial Data Division AutoCAD native drawing file format Urban Planning Division Community Development Portal Construction Permits Division Geographic Information System Computer Aided Drafting Quality Control
Page iii
LIST OF TABLES
Table Page
Table 1. List of External Attachment Files. ...................................................................... 3 Table 2. Matrix showing submission formats of the dataset ............................................. 5 Table 3. Coordinate System Definition ............................................................................ 7 Table 4. Project Title Block Details .................................................................................. 8 Table 5. PLOT Drawing Layers & corresponding Block Attribute ................................... 10 Table 6. Road Drawing Layers & corresponding Block Attribute .................................... 10 Table 7. Service Corridor Drawing Layers & corresponding Block Attribute ................... 11
Page iv
LIST OF FIGURES
Figure Page
Figure 1: Unit Settings in AutoCAD ................................................................................. 6 Figure 2: Transform Arc to Polyline ............................................................................... 12 Figure 3: Block Attribute insertion points within polygon example .................................. 13 Figure 4: Block Attribute insertion points within polyLine example ................................. 13 Figure 5: Capturing Service Corridor and Reserved Strip .............................................. 35
Page v
1.
INTRODUCTION
Planning data such as Master Plans, Roads, and Service Corridor are often prepared by consultants working for various government department and submitted to the Department of Transport (DoT) of Abu Dhabi for study and approval. This document give the standard and specifications set by the Integrated Planning Division at the Department of Transport DoT to facilitate the CAD data capture of planning datasets Plot, Roads and Service Corridors and Transit data, in such a way that the resulting data can be easily stored in the DoT Department corporate GIS database to serve the departments clients. Any submission through the TIS online system shall follow the same process standard. For the Abu Dhabi Department of Transport the planning drawings must be submitted together with all necessary documents directly to the Transportation Impact Studies section (TIS) within the Integrated Transportation Planning Division (ITP). The deliveries will be quality controlled by the TIS & the GIS staff respectfully who will then officially inform the concerned client whether their data submittal is accepted or not. The TIS section expects data submissions to be in CAD format i.e. AutoCAD DWG format not later than 2012 release. The specifications set the various parameters and guidelines to compile these features following a specific methodology in AutoCAD DWG format. Any planning data submitted and found not complying with the specifications given in this document will be rejected. The specifications are designed taking AutoCAD environment into consideration thus facilitating drafting and submitting drawings that fulfills the TIS and GIS data submission requirements. In this regard tools for quality checking and uploading of planning data are developed based on these specifications and therefore all submission which do not pass the QC test will not be regarded as valid submittal. Any queries regarding specification can be addressed via email to the Department of Transport at the mailing address of the TIS online Service Desk tis.system@dot.abudhabi.ae
Page 1
2.
PURPOSE
The purpose of this document is to furnish consultants and contractors working in Abu Dhabi by clear and concise specifications to be followed in preparation of planning data i.e. Plot, Roads & Service Corridors, Transit which aimed to be submitted to the Department of Transport for approval. Therefore this document is designed to facilitate the CAD data capture of planning datasets (Plot, Roads and Service Corridors, Transit) in such a unified way that the resulting data can be easily stored in the Department GIS database to serve DOT clients. This document was developed as a joint effort between DOT & Abu Dhabi Municipality (ADM)
Page 2
3.
LIST OF DOCUMENTS
To facilitate users with the compilation of the drawings the Department of Transport - Abu Dhabi has prepared pre-defined drawing templates, Quality Control tool and other documents in full compliance with the specifications given in this document. The templates, QC tool, QC tool user manual and all other documents and files are provided by the Department as external files attachments to this document to all clients. These clients therefore must obtain all the attachments listed in this document and the responsibility of acquiring this document and its attachments remains on them. These documents should be thoroughly reviewed and properly used to successfully compile and deliver the drawings according to specifications. The external attachment files of this document are listed and described in the Table 1. Table 1. List of External Attachment Files. Document Name <Drawing File Template>_v.dwg Document Type DWG file CAD drawing template in DWG format representing planning features developed according to specifications. The template contains pre-defined layers structures, drawing title block, pre-defined attributes blocks structures etc. The pre-defined attributes blocks structures must be used by the users as is. No changes shall be made to the structure of the block attributes. Each project should have 3 separate drawing files for following datasets <QC Tool>_v.fas AutoCAD compiled LISP program Plot Roads Service Corridors Description
This is an AutoCAD macro based QC Tool developed to check the drawing in the AutoCAD environment. The users on completion of their drawings have the ability to directly QC their work prior delivery, ensuring that the drawings are free of errors. This is the initial check and the final check will be done at ADM. The tool might be subject to updates and improvements hence the letter v in the tool file name represents the Version of the
Page 3
Document Name
Document Type
Description release. Generally the version of the tool bear the same version as of the specification and template
<QC Tool User Manual>.pdf
Manual
The
User
Manual
provides
the
necessary
operational guidelines to use the QC Tool and guidelines to interpret the error messages report which is generated to correct the drawing
Plot And Corridors Classification_v1.1.xlsx
Domain Values
This excel file provides lists of: 1. plot land use category and usage type; and 2. service corridor type for reference and data entry. These lists can change as per discretion from Department Of Transport prior any notice. Hence ensure to collect the latest updated lists.
Note: - Users can contact DOT TIS Online Service Desk at tis.system@dot.abudhabi.ae for any queries or updates
Page 4
4.
4.1
CAD SPECIFICATIONS
ELECTRONIC FILE FORMAT
The CAD drawing files must be submitted in full compliance with AutoCAD software which is not later than 2012 version. The drawings file format must be .DWG format1. The specification uses basic AutoCAD objects which were available in much earlier releases of AutoCAD software facilitating users to quickly adapt themselves with these guidelines. Depending of the project the submitted data may represent maximum three themes, namely plot; roads; and service corridors. Consequently the submission must contain maximum three (3) individual drawing files for these themes as shown in Table 2: Table 2. Matrix showing submission formats of the dataset No. 1 2 3 Dataset PLOT ROADS SERVICES Drawing File? Yes Yes Yes
Therefore, the submission shall be comprised of two types of data such as: Individual DWG files for datasets Plot, Roads & Services One DWG file containing additional layers and any other information necessary for the planners. This file need not comply with this specification and it will be used only as a reference.
4.2
FILE NAMING
The DWG file name for the above data sets must be composed by combining Project Code, Date, Drawing Type and Type of the dataset as per the format given below
DWG File
<ProjectID>_<YYYYMMDD>_<AP/MP>_<ProjectName>_<Plot/Roads/Services>_<ADM/ DOT>.dwg
For the sake of clarity the name AutoCAD in these specifications always implies AutoCAD 2012 or earlier versions
Standards & Specifications For Planning Data Submission (Plot, Roads & Service Corridors) Version 1.0 Department of Transport, Abu Dhabi, Integrated Planning Division Page 5
<ProjectID>:- Unique Project code to which the drawing belongs <YYYYMMDD>: - Date in Year, Day and Month format <AP/MP>: - Type of the Drawing file i.e. As Planned (AP) or Master Plan (MP) <ProjectName>: - Name of the area of the project <Plot/Roads/services>: - Type of the dataset i.e. Plot or Roads or service corridor <ADM/DOT>: - Specifies if the DWG file is as per DOT or ADM CAD specifications
Note: - The character <> is meant only for syntax and the file name must not have this special character Example: CP-001_20131013_AP_Maqtaa-Area_Roads_DOT.dwg CP-001_20131013_AP_Maqtaa-Area_Services_DOT.dwg CP-001_20131013_AP_Maqtaa-Area_additional_DOT.dwg
Any submitted drawing file not conforming to the naming structure shall be rejected.
4.3
SCALE AND UNITS
All CAD drawing shall be drafted at full scale in architectural metric units where one drawing unit equals one meter as depicted in the below Figure 1.
Figure 1: Unit Settings in AutoCAD
Page 6
4.4
DRAWING COORDINATES
The drawing files must follow Abu Dhabi Global coordinate system which is described in Table 3. Features created in arbitrary coordinate system shall not be accepted. However in order to facilitate users, Department of Transport GIS Section has designed a data acceptance workflow by which the consultant and contractor must collect reference data directly from GIS Section prior to planning. Using this reference data they will ensure that their plan is following coordinate system and projection used by ADM. Please refer to the "Appendix 1: DOT-ITP Reference Data Collection Process" for further details. The table presented below is only for reference. Table 3. Coordinate System Definition Horizontal Coordinate Reference System parameters Projection: False_Easting: False_Northing Central_Meridian For Zone 39: Central_Meridian For Zone 40: Scale_Factor: Latitude_Of_Origin: Linear Unit: Zone : Universal Transverse Mercator (UTM) 500000.000000 0.000000 51.000000 57.000000 0.999600 0.000000 Meter (1.000000) 40 North GCS_WGS_1984 Degree (0.017453292519943299) Greenwich (0.000000000000000000) WGS_1984 WGS_1984 6378137.000000000000000000 6356752.314245179300000000 298.257223563000030000
Underlying Geographic Coordinate System:

Angular Unit: Prime Meridian: Datum: Spheroid: Semimajor Axis: Semiminor Axis: Inverse Flattening:
Page 7
4.5
AUTOCAD BLOCK ATTRIBUTES
In AutoCAD an attribute block is a label that attaches data to a block. Each feature class has two associated layers, one for the geometry and the other for listing its details as an attribute block. Each feature table has its own distinct set of attributes grouped in an attribute block. Detailed list of layers and attribute block for each feature is listed in the subsequent section "Attribute Block" NOTE: The user must insert an attribute block for each feature as specified in Section 5 below. The user shall use the template containing predefined layers and attribute block and shall NOT change or modify Any Parts of these predefined Attributes Blocks
4.6
TITLE BLOCK
Apart from the feature attribute blocks, each CAD file submitted shall have one additional title Attribute Block. The drawing Title attributes block shall contain essential information to identify project and drawing details as specified in the Table 4. In AutoCAD model space, the title attributes block shall be placed with its lower left hand corner point inserted at a coordinate location according to the drawing plot coordinates. Table 4. Project Title Block Details Mandatory Field No No Yes No Use Yes No Yes Yes Yes
Page 8
Information Field Consultant Name Contractor Name Project Name DoT Liaison Engineer Name Land Use Information Trip Generation Values Construction Date Region Name Street Name
Description Name of the consultant. Provide if available Name of the contractor. Provide if available Name of the Project. Provide Name of the DoT Liaison. Provide if available Information Information. Information regarding the Trip Generation Values. Provide if available Date when the project would be constructed. Provide Name the region where the project is located. Provide Name the Street where the project is located. Provide regarding the proposed Land
Information Field Parking Supply Parking Demand Parking Shortage
Description Information regarding the supply parking in the area. Provide if available Information regarding the Demand parking in the area. Provide if available Information regarding the Shortage parking in the area. Provide if available Describe the type of study: Circulation Plan, Transportation Impact Study or Transportation Master Plan. Provide Information regarding the Opening year of the proposed site. Provide
Mandatory Field No No No
Study Type
Yes
Open Year
Yes
Note: - Submitted drawing must have consultant name or a contractor name or both. Drawing submitted without any of the name shall be rejected
4.7
DRAWINGS LAYERS
To create the CAD drawings the users must use the layers with the specified characteristics listed in Tables 5, 6 & 7. Layers and corresponding block attribute share the same name for example layer name Plot is combined with block attribute PlotDetail. As mentioned above in Section 4.2 the (File Naming) there are 3 DWG files for 3 different datasets i.e. Plot, Roads and Services. Hence each DWG file has distinct set of layers which are listed in the Tables 5, 6 & 7. Note: Layer "DimensionLine" must contain AutoCAD dimensions as per the dimension style given in the template Layer Title must contain drawing details such as title, border, other textual details and the attribute block as specified in "Title Block" Section
Page 9
4.7.1.
DWG FILE: PLOT
Table 5. PLOT Drawing Layers & corresponding Block Attribute No 1 2 3 4 5 6 7 8 Layer Name Plot PlotDetail Sector SectorDetail Zone ZoneDetail DimensionLine Title Topology Polyline Point Polyline Point Polyline Point NA Polyline Constraint Closed Attribute Block Closed Attribute Block Closed Attribute Block NA Closed Color 51 51 3 3 7 7 4 7 Line Type Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Line Weight Default (0.25) Default (0.25) 0.30 Default (0.25) 0.40 Default (0.25) Default (0.25) Default (0.25)
4.7.2.
DWG FILE: ROADS
Table 6. Road Drawing Layers & corresponding Block Attribute No 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Layer Name RoadEdge RoadEdgeDetail RoadCenterLine RoadCenterLineDetail RoadEntrance RoadEntranceDetail ParkingArea ParkingAreaDetail RoadLayBy RoadlayByDetail RoadHump RoadHumpDetail FootBridge FootBridgeDetail RoadTunnel RoadTunnelDetail Bridge BridgeDetail Topology Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Constraint NA Attribute Block NA Attribute Block Closed Attribute Block Closed Attribute Block Closed Attribute Block Closed Attribute Block Closed Attribute Block Closed Attribute Block Closed Attribute Block Color 8 8 6 6 30 30 2 2 43 43 3 3 140 140 51 51 5 5 Line Type Continuous Continuous Dashed Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Line Weight Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25)
Page 10
No 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38
Layer Name UnderPass UnderPassDetail Pavement PavementDetail ParkingSpace ParkingSpaceDetail LandscapeArea LandscapeAreaDetail RoadMarking RoadMarkingDetail RoadShoulder RoadShoulderDetail RoadArrow RoadArrowDetail Transit TransitDetail InventorySignal InventorySignalDetail Title DimensionLine
Topology Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline Point Polyline NA
Constraint Closed Attribute Block Closed Attribute Block Closed Attribute Block Closed Attribute Block NA Attribute Block NA Attribute Block Closed Attribute Block NA Attribute Block NA Attribute Block Closed NA
Color 9 9 42 42 7 7 73 73 254 254 40 40 254 254 26 26 123 123 7 4
Line Type Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Dashed Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous Continuous
Line Weight Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25)
4.7.3.
DWG FILE: SERVICECORRIDOR
Table 7. Service Corridor Drawing Layers & corresponding Block Attribute No 1 2 3 4 5 6 Layer Name ServiceCorridor ServiceCorridorDetail ReservedStrip ReservedStrip Detail DimensionLine Title Topology Polyline Point Polyline Point NA Polyline Constraint Closed Attribute Block Closed Attribute Block NA Closed Color 2 2 5 5 4 7 Line Type Continuous Continuous Continuous Continuous Continuous Continuous Line Weight 0.30 Default (0.25) Default (0.25) Default (0.25) Default (0.25) Default (0.25)
Page 11
5.
DATA CAPTURING RULE
The layers specifications listed in Tables 5, 6 & 7 above, must strictly follow the data capturing rules set below: i. The geometries shall be topologically cleaned and shall not contain any undershoots, overshoots, zero length Polyline, overlapping objects, snapping errors, intersection errors, self intersection errors and duplicates ii. Snapping must be made only on vertices, snapping on edges must be avoided iii. The Polyline refers to AutoCAD LWPOLYLINE (light Weight Polyline) iv. Inner polygons or inner closed lines that constitute an island or a donut within the same polygon in the same layer shall not be created. Each closed Polyline object must be a single polygon v. Ellipse, Splines and Arcs shall not be used at all. In case arcs or ellipses needs to be created to shape drawing objects, these shall be converted into Polyline and should be digitized in such a way that the space between the vertexes along the length of the chord shall be consistent with the drawing object shape and size, as shown in Figure 2.
Figure 2: Transform Arc to Polyline
vi. Each block attribute (insertion) point must fall inside the area of the object polygon. The insertion point must spatially reside inside the corresponding polygon object, as shown below in Figure 3 below:
Page 12
Figure 3: Block Attribute insertion points within polygon example In case of linear objects that attribute block must be placed on the linear object snapped to one of its vertices, as shown below in Figure 4. Note: - Do not place the attribute block at intersection of the lines or at any point where two more lines are snapped
Figure 4: Block Attribute insertion points within polyLine example vii. The DWG file must not contain objects like hatch, solid, xref, xline, line, groups, unused blocks, unused line types, unused hatch styles etcetera viii. The drawing objects must not have elevation or width ix. The drawing file must not have any 3D objects such as 3D poly, heights, etc. x. The drawing file must not have any proxy objects, such as unreferenced insertion points
Page 13
6.
ATTRIBUTE BLOCKS
The following section lists the structure of the predefined Attribute Blocks which shall be used in these specifications. Each of these Attribute Blocks is available in the attached sample drawing template. The predefined structure of the Attribute Block must not be changed and shall be used in conjunction with the appropriate layer in each drawing file.
6.1
6.1.1
DWG FILE: PLOT

PLOT
PlotDetail Attribute Block containing plot details PlotDetail Attribute Details Attribute Data Type Character Character Character Character Mandatory Yes Yes Yes Yes Description Number of a plot Sector Number of a plot Plot category Type Plot Usage Type. This is dependent on the type of the usagecategorytype. The detailed list of usagecategorytype and usagetype is available in an excel file "Plot And Corridors Classification.xlsx" as a separate attachment which must be used.
Block Attribute Name Description Layer
PlotNumber SectorNumber UsageCategoryType UsageType
6.1.2
SECTOR
SectorDetail Attribute Block containing Sector details SectorDetail Attribute Details Attribute Data Type Character Character Character Mandatory Yes Yes Yes Description Sector Number Sector Name in English Sector Name in Arabic
Page 14
SectorNumber SectorNameEnglish SectorNameArabic
6.1.3
ZONE
ZoneDetail Attribute Block containing Zone details ZoneDetail Attribute Details Attribute Data Type Character Character Mandatory Yes Yes Description Zone Name in English Zone Name in Arabic
ZoneNameEnglish ZoneNameArabic
Page 15
6.2
6.2.1
DWG FILE: ROADS

ROADCENTRELINE
RoadCentreLineDetail Attribute Block containing RoadCentreLine details RoadCentreLineDetail Attribute Details Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
Block Attribute Name Description Layer Attribute Medium
surface, undefined
RoadSurfaceType Character Yes
air,
underground,
semiBuried,
Determines surface of the road. This attribute shall have following values:
tarmac, concrete, undefined

RoadType Character Yes Determines Type of the Road. This attribute shall have following values
Highway, sikka, undefined

RoadNameEnglish RoadNameArabic StreetID Mitigation Character Character Character Character No No No yes
majorArterial,
boulevard,
avenue,
interchange, street, trackRoute, accessLane, specialConditionStreet, mushtarak,
Road Name in English Road Name in Arabic. (This becomes mandatory if Road name in English is entered) Street Number Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed
Mitigation year
Character
yes
It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 16
6.2.2
ROAD EDGE
RoadEdgeDetail Attribute Block containing RoadEdge details RoadEdgeDetail Attribute Details Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
surface, air, underground, semiBuried, undefined

RoadSurfaceType Character Yes Determines surface of the road. This attribute shall have following values:

RoadType Character Yes Determines Type of the Road. This attribute shall have following values
Local Road, Minor Collector, Major Collector, Minor Arterial, Major Arterial, boulevard, trackRoute, Expressway, avenue, accessLane, mushtarak, Freeway,Highway, interchange, sikka, undefined
RoadSurfaceHatch Mitigation Character Character Yes yes Boundary area which determines the propose mitigation by a closed polygon. Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
street,
specialConditionStreet,
Page 17
6.2.3
ROADENTRANCE
RoadEntranceDetail Attribute Block containing Road Entrance details RoadEntranceDetail Attribute Details Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
surface, undefined
air,
underground,
semiBuried,

RoadEntranceType Character Yes Determines Type of the Road. This attribute shall have following values
Public, private
RoadEntranceHatch Mitigation Character Character Yes yes Boundary area which determines the propose mitigation by a closed polygon. Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 18
6.2.4
PARKING AREA
ParkingAreaDetail Attribute Block containing parking area details ParkingAreaDetail Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
Block Attribute Name Description Layer Attribute Details Attribute Medium
surface, undefined
air,
underground,
semiBuried,

ParkingType Character Yes Determines parking type. This attribute shall have following values:
public,
handicapped,
imam,
reserved,
emergency, police, hotelApartment, bank, private, valley, undefined

NumOfParkings ParkingHatch Mitigation integer Character Character Yes Yes yes Number of parking's in the parking bay Boundary area which determines the propose mitigation by a closed polygon. Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 19
6.2.5
ROAD LAYBY
RoadlaybyDetail Attribute Block containing Road Lay by details RoadLaybyDetail Attribute Details Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
surface, air, underground, semiBuried, undefined

RoadSurfaceType Character Yes Determines surface of the road. This attribute shall have following values:

RoadLaybyType Character Yes Determines type of the road lay by. This attribute shall have following values:
bus, taxi, busAndTaxi, undefined

RoadLaybayHatch Mitigation Character Character Yes yes Boundary area which determines the propose mitigation by a closed polygon. Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 20
6.2.6
ROAD HUMP
RoadHumpDetail Attribute Block containing Road Hump details RoadHumpDetail Attribute Details Data Type Float Character Mandatory Yes Yes Description Ground level height of the hump Determines type of the road hump. This attribute shall have following values:
Block Attribute Name Description Layer Attribute GroundLevelHeight RoadHumpType
pelican, speedTable, hump, undefined

Mitigation Character yes Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 21
6.2.7
FOOT BRIDGE
FootBridgeDetail Attribute Block containing Foot Bridge details FootBridgeDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the footbridge. This attribute shall have following values:
Block Attribute Name Description Layer Attribute FootBridgeType
concrete, metal, wood, undefined

FootBridgeClassification Character Yes Determines classification of the footbridge. This attribute shall have following values:
general, metro, tram, undefined

FootBridgeHatch Mitigation Character Character Yes yes Boundary Include all area which determines required the or propose mitigation by a closed polygon. improvements proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 22
6.2.8
ROAD TUNNEL
RoadTunnelDetail Attribute Block containing Road Tunnel details RoadTunnelDetail Attribute Details Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
surface, undefined
air,
underground,
semiBuried,
Determines
surface of
the road. This
attribute shall have following values:

RoadTunnelType Character Yes Determines type of the road tunnel. This attribute shall have following values:
roadTunnel, railwayTunnel, undefined

RoadTunnelHatch Mitigation Character Character Yes yes Boundary Include all area which determines required the or propose mitigation by a closed polygon. improvements proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 23
6.2.9
BRIDGE
BridgeDetail Attribute Block containing Bridge details BridgeDetail Attribute Details Data Type Character Character Character Mandatory Yes Yes Yes Description Name of the Bridge in English Name of the Bridge in Arabic Determines type of the bridge. This attribute shall have following values:
Block Attribute Name Description Layer Attribute NameEnglish NameArabic BridgeType
cantilevelBridge, undefined
GroundLevelHeight BridgeHatch Float Character Yes Yes
griderBridge,
Ground Level Height of the Bridge Boundary area which determines the propose polygon. mitigation by a closed
Mitigation
Character
yes
Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed
Mitigation year
Character
yes
Page 24
6.2.10
UNDERPASS
UnderpassDetail Attribute Block containing Underpass details UnderpassDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the underpass. This attribute shall have following values:
Block Attribute Name Description Layer Attribute UnderPassType
pedestrian, cars, pedestrianAndCars, undefined

UnderPassHatch Character Yes Boundary area which determines the propose polygon. Mitigation Character yes Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030 mitigation by a closed
Page 25
6.2.11
PARKING SPACE
ParkingSpaceDetail Attribute Block containing individual parking spaces details ParkingSpaceDetail Attribute Details Data Type Boolean Mandatory Yes Description Specify is parking in the bay is sheltered or not. This attribute shall have value Y or N
Block Attribute Name Description Layer Attribute IsSheltered
ParkingHatch
Character
Yes
Boundary area which determines the propose polygon. mitigation by a closed
Mitigation
Character
yes
Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed
Mitigation year
Character
yes
Page 26
6.2.12
PAVEMENT DETAIL
PavementDetail Attribute Block containing pavement details PavementDetail Attribute Details Data Type Character Mandatory Yes Description Determines medium of the road. This attribute shall have following values:
surface, undefined
PavementType Character Yes
air,
underground,
semiBuried,
Determines pavement type. This attribute shall have following values:
Tiled,
AccessType Character Yes
concreted,
asphalt,
unpaved,
undefined
Determines pavement access type. This attribute shall have following values:
public, private, undefined

PavementHatch Mitigation Character Character Yes yes Boundary Include all area which determines required the or propose mitigation by a closed polygon. improvements proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 27
6.2.13
LANDSCAPE AREA
LandscapeAreaDetail Attribute Block containing Landscape Area details LandscapeAreaDetail Attribute Details Data Type Character Mandatory Yes Description Determines landscape area type. This attribute shall have following values:
Block Attribute Name Description Layer Attribute AreaType
sand, treePlantation, grass, tile, gravel, other

LandscapeHatch Mitigation Character Character Yes yes Boundary Include all area which determines required the or propose mitigation by a closed polygon. improvements proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 28
6.2.14
ROAD MARKING
RoadMarkingDetail Attribute Block containing Road marking details RoadMarkingDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the road markings. This attribute shall have following values:
Block Attribute Name Description Layer Attribute RoadMarkingType
stopLine, giveWayLine, pedestrianCrossing, noPassingLine, parkingEnvelopeLine, rumbleStrips, enhancedDividingLine, emhancedLaneLine,

Mitigation Character yes Include all
channelizingLine, parkingSpaceLine, dividingLine, laneLine, chevron, hatch,

or
speedHump,
guideLine, continuityLine, visibilityPainting

improvements required proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 29
6.2.15
ROAD SHOULDER
RoadShoulderDetail Attribute Block containing Road shoulder details RoadShoulderDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the road shoulder. This attribute shall have following values:
Block Attribute Name Description Layer Attribute RoadShoulderType
Paved, unpaved
RoadShoulderUse Character Yes Determines usage of the road shoulder. This attribute shall have following values:
hardEmergencyLane, hardEmergencyStop, softShoulder

Page 30
6.2.16
ROAD ARROW
RoadArrowDetail Attribute Block containing Road Arrow details RoadArrowDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the road arrows. This attribute shall have following values:
Block Attribute Name Description Layer Attribute RoadArrowType
laneEndArrowStraight, laneEndArrowRightTurn, laneEndArrowLeftTurn, laneEndArrowStraight/Right, laneEndArrowStraight/Left, laneEndArrowRight/Left, laneEndArrow noParking, noStoppingBoxAtIntersection, areaOfPedestrianCrossing
Page 31
6.2.17
TRANSIT
TransitDetail Attribute Block containing Transit details TransitDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the Transit. This attribute shall have following values:
Block Attribute Name Description Layer Attribute TransitType
transitBus, transitLRT, transitMetro

Location Data Character Yes Determines information of the Transit. This attribute shall have following values:
Route name and Building Name

Page 32
6.2.18
INVENTORY SIGNAL
InventorySignalDetail Attribute Block containing Inventory Signal details InventorySignalDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the Inventory Signal. This attribute shall have following values:
Block Attribute Name Description Layer Attribute InventorySignalType
Arrow traffic, crossing signs, dead end, detour, Do Not enter, MUTCD, Private Road, Road Works, School Traffic, Slow Down, Stop, Traffic Yield, Highway, bike, Road Warning, city limits, guide, speed bump, speed humps, turn, wrong way and code signs
InventorySignalStructure Character Yes Determines structure of the Inventory Signal. This attribute shall have following values:
Plate, pole and foundation

InventorySignalItems Character Yes Determines new Items of the road. This attribute shall have following values:
Cone, Barriers and Traffic Signal

Page 33
6.3
6.3.1
DWG FILE: SERVICES

SERVICE CORRIDOR
ServiceCorridorDetail Attribute Block containing Service corridor details ServiceCorridorDetail Attribute Details Data Type Character Mandatory Yes Description Determines type of the service corridor. This attribute shall have following values:
Block Attribute Name Description Layer Attribute CorridorType
roadServiceReservation, buildingServiceReservation, specialServiceReservation, undefined

CorridorWidth ServiceCorridorHatch Mitigation Float Character Character Yes Yes yes Total Width of the corridor Boundary area which determines the propose mitigation by a closed polygon. Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed Mitigation year Character yes It is the year in which this project is conducted. This attribute shall have following values, Any value from Opening year, till 2030
Page 34
6.3.2
RESERVED STRIP
ReservedStripDetail Attribute Block containing utility reserved strip details ReservedStripDetail Attribute Details Data Type Character Mandatory Yes Description Type of the reserved strip . Detailed list is available in an excel file "Plot And Corridors Classification.xlsx" as a separate attachment which must be used
Block Attribute Name Description Layer Attribute ReservedStripType
ReservedStripWidth Mitigation
Float Character
Yes yes
Width of the reserved strip Include all improvements required or proposed as a result of this project. This attribute shall have following values, Proposed
Mitigation year
Character
yes
Service Corridor is a polygon feature which will contain utility Reserved Strips as individual polygons as depicted below in the Figure 5. Both the polygon features will have their own IDs following the block insertion rule as mentioned in data capturing rule section
Figure 5: Capturing Service Corridor and Reserved Strip

Standards & Specifications For Planning Data Submission (Plot, Roads & Service Corridors) Version 1.0 Department of Transport, Abu Dhabi, Integrated Planning Division Page 35
The Attribute Block shall strictly observe the following rules: i. Attributes blocks shall be inserted as per the drafting rules defined in "Data Capturing Rules" section ii. iii. iv. The block attribute predefined template must be used. Text entities shall not be used Attributes with predefined list of values (or domain values) shall contain only those values. These values are listed in the "Description" column and they are case sensitive (i.e. they must be used as it is) v. In each block attribute special characters, repeated characters, letters instead of numbers and vice versa shall be flagged as data entry errors. Care shall be taken in entering the block attributes values to avoid any data entry errors.
Page 36
APPENDIX 1: DOT REFERENCE DATA COLLECTION PROCESS
Page 37

31a4ced78352444196fa54f9c47729fb

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

31a4ced78352444196fa54f9c47729fb

Uploaded by

Copyright:

Available Formats

STANDARDS AND SPECIFICATIONS FOR PLANNING DATA SUBMISSION

(PLOT, ROADS, TRANSIT & SERVICE CORRIDORS)

DWG FIle: SERVICES .................................................................................... 34

ACRONYM & ABBREVIATION

<QC Tool User Manual>.pdf

Plot And Corridors Classification_v1.1.xlsx

SCALE AND UNITS

Figure 1: Unit Settings in AutoCAD

Underlying Geographic Coordinate System:

AUTOCAD BLOCK ATTRIBUTES

Information Field Parking Supply Parking Demand Parking Shortage

DWG FILE: PLOT

DWG FILE: ROADS

Color 9 9 42 42 7 7 73 73 254 254 40 40 254 254 26 26 123 123 7 4

DWG FILE: SERVICECORRIDOR

DATA CAPTURING RULE

Figure 2: Transform Arc to Polyline

DWG FILE: PLOT

Block Attribute Name Description Layer

PlotNumber SectorNumber UsageCategoryType UsageType

Block Attribute Name Description Layer

SectorNumber SectorNameEnglish SectorNameArabic

Block Attribute Name Description Layer

DWG FILE: ROADS

Block Attribute Name Description Layer Attribute Medium

tarmac, concrete, undefined

Highway, sikka, undefined

interchange, street, trackRoute, accessLane, specialConditionStreet, mushtarak,

Block Attribute Name Description Layer Attribute Medium

surface, air, underground, semiBuried, undefined

tarmac, concrete, undefined

Block Attribute Name Description Layer Attribute Medium

tarmac, concrete, undefined

Block Attribute Name Description Layer Attribute Details Attribute Medium

tarmac, concrete, undefined

emergency, police, hotelApartment, bank, private, valley, undefined

Block Attribute Name Description Layer Attribute Medium

surface, air, underground, semiBuried, undefined

tarmac, concrete, undefined

bus, taxi, busAndTaxi, undefined

Block Attribute Name Description Layer Attribute GroundLevelHeight RoadHumpType

pelican, speedTable, hump, undefined

Block Attribute Name Description Layer Attribute FootBridgeType

concrete, metal, wood, undefined

general, metro, tram, undefined

Block Attribute Name Description Layer Attribute Medium

the road. This

attribute shall have following values:

tarmac, concrete, undefined

roadTunnel, railwayTunnel, undefined

Block Attribute Name Description Layer Attribute NameEnglish NameArabic BridgeType

Block Attribute Name Description Layer Attribute UnderPassType

pedestrian, cars, pedestrianAndCars, undefined

Block Attribute Name Description Layer Attribute IsSheltered

Boundary area which determines the propose polygon. mitigation by a closed

Block Attribute Name Description Layer Attribute Medium

Determines pavement type. This attribute shall have following values:

public, private, undefined

Block Attribute Name Description Layer Attribute AreaType

sand, treePlantation, grass, tile, gravel, other

Block Attribute Name Description Layer Attribute RoadMarkingType

stopLine, giveWayLine, pedestrianCrossing, noPassingLine, parkingEnvelopeLine, rumbleStrips, enhancedDividingLine, emhancedLaneLine,

channelizingLine, parkingSpaceLine, dividingLine, laneLine, chevron, hatch,