ROAD - Spatial Data Model - Specification

Contents

1. Overview
2. Class Diagram
3. Class Details
4. Relationships
5. Code Lists
6. Miscellaneous Information

1. Overview

The ROAD data model has the following characteristics:

Name:	ROAD
Description:	The Road data model for the LIST Project
Database Type:	ODBC
Dataset:	ROAD
Unit of Measure:	meters

2. Class Diagram

3. Class Details

The following classes are part of the ROAD data model. The characteristics and attributes of each of the classes is described.

3.1. Class: Blt_Area

This class is defined as follows:

Name:	Blt_Area
Screen Text:	Built Area
Plural:	Built Areas
Description:	A area of greater than 0.5ha where 50% or more of the land area has been built upon.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.1.1. Attribute: bltarea_id

Name:	bltarea_id
Screen Text:	Built Area ID
Description:	The unique identifier for an occurrence of a Built Area.
Plural:	Built Area IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.1.2. Attribute: bltarea_ty

Name:	bltarea_ty
Screen Text:	Built Area Type
Description:	The type of Built Area.
Plural:	Built Area Types
SQL Type:	varchar(2)
Width:	2
Code List:	BltType
Field Position (Width):	2
Mandatory:	Yes

3.1.3. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The area as computed by SDE.
Plural:	Computed Areas
SQL Type:	numeric(9,3)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.1.4. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	A flag to indicate whether the area feature is valid or represents a null area.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.1.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	Unique Feature Identifier
Plural:	Unique Feature Identifiers
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes
Unique:	Yes

3.1.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	FMP's
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.1.7. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.1.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.2. Class: Brdg_Nd

This class is defined as follows:

Name:	Brdg_Nd
Screen Text:	Bridge Node
Plural:	Bridge Nodes
Description:	A Road Node that represents all or part of a Bridge.
Spatial:	No
Feature Types:	p

It contains the following attributes:

3.2.1. Attribute: rdnd_id

Name:	rdnd_id
Screen Text:	Road Node ID
Description:	Road Node ID
Plural:	Road Node IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Indexed:	Yes
Unique:	Yes

3.2.2. Attribute: bridge_id

Name:	bridge_id
Screen Text:	Bridge_ID
Description:	The unique identifier in the LIST for a Bridge.
Plural:	Bridge_IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.2.3. Attribute: rdseg_id1

Name:	rdseg_id1
Screen Text:	Road Segment 1
Description:	The first of 2 Road Segment ID's which join to a Bridge Node.
Plural:	Road Segment 1s
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.2.4. Attribute: rdseg_id2

Name:	rdseg_id2
Screen Text:	Road Segment 2
Description:	The second of 2 Road Segment ID's which join to a Bridge Node.
Plural:	Road Segment 2s
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.2.5. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.2.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.3. Class: Brdg_Seg

This class is defined as follows:

Name:	Brdg_Seg
Screen Text:	Bridge Segment
Plural:	Bridge Segments
Description:	A Road Segment that represents all or part of a Bridge.
Spatial:	No
Feature Types:	l

It contains the following attributes:

3.3.1. Attribute: roadseg_id

Name:	roadseg_id
Screen Text:	Road Segment ID
Description:	The unique number for a Road Segment within the State.
Plural:	Road Segment IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Indexed:	Yes
Unique:	Yes

3.3.2. Attribute: bridge_id

Name:	bridge_id
Screen Text:	Bridge_ID
Description:	The unique identifier in the LIST for a Bridge.
Plural:	Bridge_IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.3.3. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.3.4. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.4. Class: Bridge

This class is defined as follows:

Name:	Bridge
Screen Text:	BRIDGE
Plural:	BRIDGEs
Description:	A structure erected over a depression or obstacle to carry road traffic.
Spatial:	No
Feature Types:	ps

It contains the following attributes:

3.4.1. Attribute: bridge_id

Name:	bridge_id
Screen Text:	Bridge_ID
Description:	The unique identifier in the LIST for a Bridge.
Plural:	Bridge_IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.4.2. Attribute: bridge_ty

Name:	bridge_ty
Screen Text:	Bridge Type
Description:	The type of bridge.
Plural:	Bridge Types
SQL Type:	smallint
Width:	6
Code List:	BridgeTy
Field Position (Width):	6
Unique:	Yes

3.4.3. Attribute: load_limit

Name:	load_limit
Screen Text:	Load Limit
Description:	The constructed load limit of a bridge in Tonnes.
Plural:	Load Limits
SQL Type:	smallint
Width:	6
Field Position (Width):	6

3.4.4. Attribute: width

Name:	width
Screen Text:	Width
Description:	The width of the Road.
Plural:	Widths
SQL Type:	numeric(2,1)
Width:	4
Field Position (Width):	4

3.4.5. Attribute: meas_len

Name:	meas_len
Screen Text:	Length
Description:	Length in metres
Plural:
SQL Type:	numeric(4,1)
Width:	6
Field Position (Width):	6

3.4.6. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique number in the nomenclature database which relates to the named feature.
Plural:	Nomenclature register numbers
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Unique:	Yes

3.4.7. Attribute: clearance

Name:	clearance
Screen Text:	Clearance
Description:	The minimum height restriction nominated for vehicles traveling through of under a height restricted feature.
Plural:	Clearances
SQL Type:	numeric(2,1)
Width:	4
Field Position (Width):	4

3.4.8. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.4.9. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.5. Class: Carriage

This class is defined as follows:

Name:	Carriage
Screen Text:	Carriageway
Plural:	Carriageways
Description:	A section of road which is contained within a link and does not include physically separate directions of travel.
Spatial:	Yes
Feature Types:	lM

It contains the following attributes:

3.5.1. Attribute: carrig_no

Name:	carrig_no
Screen Text:	Carriageway Number
Description:	The number of the carriageway within the context on the link.
Plural:	Carriageway Numbers
SQL Type:	smallint
Width:	6
Field Position (Width):	6
Mandatory:	Yes

3.5.2. Attribute: carrig_ty

Name:	carrig_ty
Screen Text:	Carriageway Type
Description:	The type of carriageway based on DOT approach.
Plural:
SQL Type:	varchar(1)
Width:	1
Code List:	CarrigTy
Field Position (Width):	1
Mandatory:	Yes

3.5.3. Attribute: link_no

Name:	link_no
Screen Text:	Link Number
Description:	The number which identifies a Link on a Road.
Plural:	Link Numbers
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.5.4. Attribute: road_no

Name:	road_no
Screen Text:	Road Number
Description:	A unique number assigned to a Road.
Plural:
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.5.5. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	Nomenclature Register Number
Plural:	Nomenclature Register Numbers
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.5.6. Attribute: start_chg

Name:	start_chg
Screen Text:	Start Link Chainage
Description:	The chainage on the associated Link at which the Carriageway starts.
Plural:	Start Link Chainages
SQL Type:	numeric(2,2)
Width:	5
Field Position (Width):	5
Mandatory:	Yes

3.5.7. Attribute: end_chg

Name:	end_chg
Screen Text:	End Link Chainage
Description:	The chainage of the associated Link at which the carriageway ends.
Plural:	Start Link Chainages
SQL Type:	numeric(2,2)
Width:	5
Field Position (Width):	5
Mandatory:	Yes

3.5.8. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance as computed by SDE.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.5.9. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	Unique Feature Identifier
Plural:	Unique Feature Identifiers
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes
Unique:	Yes

3.5.10. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	FMP's
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.5.11. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.5.12. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.6. Class: Illegal

This class is defined as follows:

Name:	Illegal
Screen Text:	Illegal Turns
Plural:	Illegal Turns
Description:	A table to record vehicle turns which are not allowed at Road Nodes where they are variable.
Spatial:	No

It contains the following attributes:

3.6.1. Attribute: rdnd_id

Name:	rdnd_id
Screen Text:	Road Node ID
Description:	Road Node ID
Plural:	Road Node IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Indexed:	Yes
Unique:	Yes

3.6.2. Attribute: rdseg_id1

Name:	rdseg_id1
Screen Text:	Road Segment 1
Description:	The first of 2 Road Segment ID's which join to a Bridge Node.
Plural:	Road Segment 1s
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.6.3. Attribute: rdseg_id2

Name:	rdseg_id2
Screen Text:	Road Segment 2
Description:	The second of 2 Road Segment ID's which join to a Bridge Node.
Plural:	Road Segment 2s
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.6.4. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.6.5. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.7. Class: Link

This class is defined as follows:

Name:	Link
Screen Text:	Link
Plural:	Links
Description:	A section of a Road to which linear information can be related.
Spatial:	No

It contains the following attributes:

3.7.1. Attribute: road_no

Name:	road_no
Screen Text:	Road Number
Description:	A unique number assigned to a ROAD.
Plural:
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.7.2. Attribute: link_no

Name:	link_no
Screen Text:	Link Number
Description:	The number which identifies a Link on a Road.
Plural:	Link Numbers
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Unique:	Yes

3.7.3. Attribute: ch_length

Name:	ch_length
Screen Text:	Ch_length
Description:	The length of the link according to related chainage data.
Plural:	Ch_lengths
SQL Type:	numeric(3,2)
Width:	5
Field Position (Width):	5
Mandatory:	Yes

3.7.4. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.7.5. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.8. Class: Road

This class is defined as follows:

Name:	Road
Screen Text:	Road
Plural:	Roads
Description:	An open way for the passage of vehicles, persons or animals on land. [DR97068]
Spatial:	No

It contains the following attributes:

3.8.1. Attribute: road_no

Name:	road_no
Screen Text:	Road Number
Description:	A unique number assigned to a ROAD.
Plural:
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.8.2. Attribute: proc_name

Name:	proc_name
Screen Text:	Proclaimed Name
Description:	The unique number in the nomenclature database which relates to the primary name of the road.
Plural:	Nomenclature register Nos
SQL Type:	varchar(30)
Width:	30
Field Position (Width):	30
Unique:	Yes

3.8.3. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.8.4. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.9. Class: RoadNode

This class is defined as follows:

Name:	RoadNode
Screen Text:	Road Node
Plural:	Road Nodess
Description:	A point at which a Road Segment stops.
Spatial:	Yes
Feature Types:	p

It contains the following attributes:

3.9.1. Attribute: rdnd_id

Name:	rdnd_id
Screen Text:	Road Node ID
Description:	Road Node ID
Plural:	Road Node IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.9.2. Attribute: rdnd_feat

Name:	rdnd_feat
Screen Text:	Road Node Feature
Description:	The type of feature represented by the Road Node
Plural:	Road Node Features
SQL Type:	smallint
Width:	6
Code List:	RdNdFeat
Field Position (Width):	6
Mandatory:	Yes

3.9.3. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique number in the nomenclature database which relates to the named feature.
Plural:	Nomenclature Register Numbers
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Unique:	Yes

3.9.4. Attribute: junc_turn

Name:	junc_turn
Screen Text:	Junction turns
Description:	A broad description of the turning options at a Road Node.
Plural:	Junction turns
SQL Type:	char(1)
Width:	1
Code List:	JuncTurn
Field Position (Width):	1

3.9.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	Unique Feature Identifier
Plural:	Unique Feature Identifiers
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes
Unique:	Yes

3.9.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	FMP's
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.9.7. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.9.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.10. Class: Road_Acc

This class is defined as follows:

Name:	Road_Acc
Screen Text:	Road Accident Site
Plural:	Road Accident Sites
Description:	A site at which some form of traffic accident has occurred.
Spatial:	Yes
Feature Types:	p

It contains the following attributes:

3.10.1. Attribute: accsite_id

Name:	accsite_id
Screen Text:	Accident Site ID
Description:	The identifier for a particular accident event.
Plural:
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.10.2. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	Unique Feature Identifier
Plural:	Unique Feature Identifiers
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes
Unique:	Yes

3.10.3. Attribute: dqp

Name:	dqp
Screen Text:	DQP
Description:	Data Quality Pointer
Plural:	DQPs
SQL Type:	varchar(12)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.10.4. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.10.5. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.11. Class: Road_Bar

This class is defined as follows:

Name:	Road_Bar
Screen Text:	Road Barrier
Plural:	Road Barriers
Description:	A potential obstruction against the flow of traffic on a road.
Spatial:	No
Feature Types:	p

It contains the following attributes:

3.11.1. Attribute: rd_bar_id

Name:	rd_bar_id
Screen Text:	Road Barrier ID
Description:	Road Barrier ID
Plural:	Road Barrier IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Indexed:	Yes
Unique:	Yes

3.11.2. Attribute: rdnd_id

Name:	rdnd_id
Screen Text:	Road Node ID
Description:	Road Node ID
Plural:	Road Node IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.11.3. Attribute: width

Name:	width
Screen Text:	Width
Description:	The width of the barrier.
Plural:	Widths
SQL Type:	numeric(2,1)
Width:	4
Field Position (Width):	4

3.11.4. Attribute: bar_height

Name:	bar_height
Screen Text:	Barrier Height
Description:	The height limit of a Road Barrier.
Plural:	Barrier Heights
SQL Type:	numeric(2,1)
Width:	4
Field Position (Width):	4

3.11.5. Attribute: rd_bar_ty

Name:	rd_bar_ty
Screen Text:	Road Barrier Type
Description:	The type of Road Barrier.
Plural:	Road Barrier Types
SQL Type:	smallint
Width:	6
Code List:	BarType
Field Position (Width):	6
Mandatory:	Yes

3.11.6. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique number in the nomenclature database which relates to the named feature.
Plural:	Nomenclature register numbers
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Unique:	Yes

3.11.7. Attribute: road_no

Name:	road_no
Screen Text:	Road Number
Description:	A unique number assigned to a ROAD.
Plural:
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.11.8. Attribute: link_no

Name:	link_no
Screen Text:	Link Number
Description:	The number which identifies a Link on a Road.
Plural:	Link Numbers
SQL Type:	varchar(10)
Width:	10
Field Position (Width):	10
Unique:	Yes

3.11.9. Attribute: chainage

Name:	chainage
Screen Text:	Chainage
Description:	Chainage along link that barrier exists at
Plural:	Chainages
SQL Type:	numeric(3,2)
Width:	6
Field Position (Width):	6

3.11.10. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.11.11. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.12. Class: Road_Seg

This class is defined as follows:

Name:	Road_Seg
Screen Text:	Road Segment
Plural:	Road Segments
Description:	A portion of a road which starts and finishes on a Road Node.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.12.1. Attribute: roadseg_id

Name:	roadseg_id
Screen Text:	Road Segment ID
Description:	The unique number for a Road Segment within the State.
Plural:	Road Segment IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.12.2. Attribute: rdsg_feat

Name:	rdsg_feat
Screen Text:	Road Segment Feaure
Description:	The type of feature represented by a Road Segment.
Plural:	Road Segment Feaures
SQL Type:	smallint
Width:	6
Code List:	RdSgFeat
Field Position (Width):	6
Mandatory:	Yes

3.12.3. Attribute: rd_class

Name:	rd_class
Screen Text:	Rd Class
Description:	A general classification for roads developed from an amalgum of local classifications.
Plural:
SQL Type:	smallint
Width:	6
Code List:	RdClass
Field Position (Width):	6
Mandatory:	Yes

3.12.4. Attribute: tour_class

Name:	tour_class
Screen Text:	Tourist Route Class
Description:	The Class and number under the Tourist Route Classification managed by DOT.
Plural:	Tourist Route Classes
SQL Type:	varchar(4)
Width:	4
Field Position (Width):	4

3.12.5. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register No
Description:	The unique number in the nomenclature database which relates to the name of the Road Segment.
Plural:	Nomenclature Register No
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Unique:	Yes

3.12.6. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance as computed by SDE.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.12.7. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	Unique Feature Identifier
Plural:	Unique Feature Identifiers
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes
Unique:	Yes

3.12.8. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	FMP's
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.12.9. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.12.10. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.13. Class: Route

This class is defined as follows:

Name:	Route
Screen Text:	Route
Plural:	ROUTEs
Description:	A sequence of Road Segments regularly used for the passage of vehicles.
Spatial:	No

It contains the following attributes:

3.13.1. Attribute: route_id

Name:	route_id
Screen Text:	Route ID
Description:	A unique identifier for a Route.
Plural:	Route IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.13.2. Attribute: route_pur

Name:	route_pur
Screen Text:	Route Purpose
Description:	The purpose for a particular Route.
Plural:
SQL Type:	smallint
Width:	6
Code List:	RoutePur
Field Position (Width):	6
Mandatory:	Yes

3.13.3. Attribute: route_lev

Name:	route_lev
Screen Text:	Route Level
Description:	Whether the Route is a part of another Route.
Plural:
SQL Type:	smallint
Width:	6
Field Position (Width):	6

3.13.4. Attribute: parrout_id

Name:	parrout_id
Screen Text:	Parent Route ID
Description:	A link to the Parent Route.
Plural:	Parent Route IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11

3.13.5. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.13.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.14. Class: Tnnl_Nd

This class is defined as follows:

Name:	Tnnl_Nd
Screen Text:	Tunnel Node
Plural:
Description:	A Road Node that represents all or part of a Tunnel.
Spatial:	No
Feature Types:	p

It contains the following attributes:

3.14.1. Attribute: rdnd_id

Name:	rdnd_id
Screen Text:	Road Node ID
Description:	Road Node ID
Plural:	Road Node IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Indexed:	Yes
Unique:	Yes

3.14.2. Attribute: tunnel_id

Name:	tunnel_id
Screen Text:	Tunnel ID
Description:	The unique identifier for a Tunnel in the LIST.
Plural:	Tunnel IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.14.3. Attribute: rdseg_id1

Name:	rdseg_id1
Screen Text:	Road Segment 1
Description:	The first of 2 Road Segment ID's which join to a Bridge Node.
Plural:	Road Segment 1s
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.14.4. Attribute: rdseg_id2

Name:	rdseg_id2
Screen Text:	Road Segment 2
Description:	The second of 2 Road Segment ID's which join to a Bridge Node.
Plural:	Road Segment 2s
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.14.5. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.14.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.15. Class: Tnnl_Seg

This class is defined as follows:

Name:	Tnnl_Seg
Screen Text:	Tunnel Segment
Plural:	Tunnel Segments
Description:	A Road Segment that represents all or part of a Tunnel.
Spatial:	No
Feature Types:	l

It contains the following attributes:

3.15.1. Attribute: roadseg_id

Name:	roadseg_id
Screen Text:	Road Segment ID
Description:	The unique number for a Road Segment within the State.
Plural:	Road Segment IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Indexed:	Yes
Unique:	Yes

3.15.2. Attribute: tunnel_id

Name:	tunnel_id
Screen Text:	Tunnel ID
Description:	The unique identifier for a Tunnel in the LIST.
Plural:	Tunnel IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.15.3. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.15.4. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.16. Class: Tunnel

This class is defined as follows:

Name:	Tunnel
Screen Text:	Tunnel
Plural:
Description:
Spatial:	No

It contains the following attributes:

3.16.1. Attribute: tunnel_id

Name:	tunnel_id
Screen Text:	Tunnel ID
Description:	The unique identifier for a Tunnel in the LIST.
Plural:	Tunnel IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.16.2. Attribute: width

Name:	width
Screen Text:	Width
Description:	Width
Plural:	Widths
SQL Type:	numeric(2,1)
Width:	4
Field Position (Width):	4

3.16.3. Attribute: tunnel_ty

Name:	tunnel_ty
Screen Text:	Tunnel Type
Description:	The type of Tunnel.
Plural:
SQL Type:	smallint
Width:	6
Code List:	TunnelTy
Field Position (Width):	6
Mandatory:	Yes

3.16.4. Attribute: meas_len

Name:	meas_len
Screen Text:	Length
Description:	Length in metres
Plural:	Lengths
SQL Type:	numeric(4,1)
Width:	6
Field Position (Width):	6

3.16.5. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique number in the nomenclature database which relates to the named feature.
Plural:	Nomenclature register numbers
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Unique:	Yes

3.16.6. Attribute: clearance

Name:	clearance
Screen Text:	Clearance
Description:	The minimum height restriction nominated for vehicles traveling through of under a height restricted feature.
Plural:	Clearances
SQL Type:	numeric(2,1)
Width:	4
Field Position (Width):	4

3.16.7. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.16.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

4. Relationships

The relationships are listed together as a 'pair' between classes. Further details on each individual relationship 'direction' is also provided.

4.1. Relationship Pair: Brdg_Nd (Brdg_Nd_to_Road_node) and RoadNode (Road_node_to_Bridge_Nd)

Each record in Brdg_Nd is always related to one (and only one) record in RoadNode. Each record in RoadNode can be related to (optionally) one record in Brdg_Nd. This relationship pair is represented spatially.

4.1.1. From Brdg_Nd To RoadNode

Name:	Brdg_Nd_to_Road_node
Screen Text:	Road Bridge 0D To Road Node
Plural:	Road Bridge 0D To Road Nodes
Description:	Road Bridge 0D To Road Node

4.1.2. From RoadNode To Brdg_Nd

Name:	Road_node_to_Bridge_Nd
Screen Text:	Road Node To Road Bridge 0D
Plural:	Road Node To Road Bridge 0Ds
Description:	Road Node To Road Bridge 0D

4.1.3. Spatial Representation

Class Brdg_Nd is represented via point features. Class RoadNode is represented via point features. The features are related together via the following boundary/interior intersections:

Point-Point (0-0): The following "OR"-ed together:

Boundary of Brdg_Nd intersects with boundary of RoadNode.

4.2. Relationship Pair: Brdg_Nd (Brdg_Nd_to_Bridge) and Bridge (Bridge_to_Brdg_Nd)

Each record in Brdg_Nd is always related to one (and only one) record in Bridge. Each record in Bridge is related to zero or more records in Brdg_Nd.

4.2.1. From Brdg_Nd To Bridge

Name:	Brdg_Nd_to_Bridge
Screen Text:	Road Br0 To Bridge
Plural:	Road Br0 To Bridges
Description:	Road Br0 To Bridge
Primary Class:	Bridge
Foreign Class:	Brdg_Nd

4.2.2. From Bridge To Brdg_Nd

Name:	Bridge_to_Brdg_Nd
Screen Text:	Bridge To Road Br0
Plural:	Bridges To Road Br0
Description:	Bridge To Road Br0
Primary Class:	Bridge
Foreign Class:	Brdg_Nd

4.3. Relationship Pair: Brdg_Seg (Brdg_Seg_to_Road_segment) and Road_Seg (Road_segment_to_Brdg_Seg)

Each record in Brdg_Seg is always related to one (and only one) record in Road_Seg. Each record in Road_Seg can be related to (optionally) one record in Brdg_Seg. This relationship pair is represented spatially.

4.3.1. From Brdg_Seg To Road_Seg

Name:	Brdg_Seg_to_Road_segment
Screen Text:	Road Bridge To Road Segment
Plural:	Road Bridge To Road Segments
Description:	Road Bridge To Road Segment

4.3.2. From Road_Seg To Brdg_Seg

Name:	Road_segment_to_Brdg_Seg
Screen Text:	Road Segment To Road Bridge
Plural:	Road Segment To Road Bridges
Description:	Road Segment To Road Bridge

4.3.3. Spatial Representation

Class Brdg_Seg is represented via simple line features. Class Road_Seg is represented via simple line features. The features are related together via the following boundary/interior intersections:

Line-Line (1-1): The following "OR"-ed together:

Boundary of Brdg_Seg intersects with boundary of Road_Seg AND interior of Brdg_Seg intersects with interior of Road_Seg.


Additionally, the following restrictions apply:


Between Brdg_Seg and Road_Seg: LA

4.4. Relationship Pair: Brdg_Seg (Brdg_Seg_to_Bridge) and Bridge (Bridge_to_Brdg_Seg)

Each record in Brdg_Seg is always related to one (and only one) record in Bridge. Each record in Bridge is related to zero or more records in Brdg_Seg.

4.4.1. From Brdg_Seg To Bridge

Name:	Brdg_Seg_to_Bridge
Screen Text:	Road Br1 To Bridge
Plural:	Road Br1 To Bridges
Description:	Road Br1 To Bridge
Primary Class:	Bridge
Foreign Class:	Brdg_Seg

4.4.2. From Bridge To Brdg_Seg

Name:	Bridge_to_Brdg_Seg
Screen Text:	Bridge To Road Br1
Plural:	Bridges To Road Br1
Description:	Bridge To Road Br1
Primary Class:	Bridge
Foreign Class:	Brdg_Seg

4.5. Relationship Pair: Bridge (Bridge_to_Brdg_Seg) and Brdg_Seg (Brdg_Seg_to_Bridge)

See Relationship Pair: Brdg_Seg (Brdg_Seg_to_Bridge) and Bridge (Bridge_to_Brdg_Seg)}.

4.6. Relationship Pair: Bridge (Bridge_to_Brdg_Nd) and Brdg_Nd (Brdg_Nd_to_Bridge)

See Relationship Pair: Brdg_Nd (Brdg_Nd_to_Bridge) and Bridge (Bridge_to_Brdg_Nd)}.

4.7. Relationship Pair: Carriage (Carriageway_to_Link) and Link (Link_to_Carriageway)

Each record in Carriage is always related to one (and only one) record in Link. Each record in Link is related to one or more records in Carriage.

4.7.1. From Carriage To Link

Name:	Carriageway_to_Link
Screen Text:	Carriageway To Link
Plural:	Carriageways To Link
Description:	Carriageway To Link
Primary Class:	Carriage
Foreign Class:	Link

4.7.2. From Link To Carriage

Name:	Link_to_Carriageway
Screen Text:	Link To Carriageway
Plural:	Links To Carriageway
Description:	Link To Carriageway
Primary Class:	Carriage
Foreign Class:	Link

4.8. Relationship Pair: Carriage (Carriageway_to_Road_segment) and Road_Seg (Road_segment_to_Carriageway)

Each record in Carriage is related to one or more records in Road_Seg. Each record in Road_Seg is always related to one (and only one) record in Carriage. This relationship pair is represented spatially.

4.8.1. From Carriage To Road_Seg

Name:	Carriageway_to_Road_segment
Screen Text:	Carriageway To Road Segment
Plural:	Carriageways To Road Segment
Description:	Carriageway To Road Segment

4.8.2. From Road_Seg To Carriage

Name:	Road_segment_to_Carriageway
Screen Text:	Road Segment To Carriageway
Plural:	Road Segment To Carriageways
Description:	Road Segment To Carriageway

4.8.3. Spatial Representation

Class Carriage is represented via simple line and measures features. Class Road_Seg is represented via simple line features. The features are related together via the following boundary/interior intersections:

Line-Line (1-1): The following "OR"-ed together:

Boundary of Carriage intersects with boundary of Road_Seg AND interior of Carriage intersects with interior of Road_Seg.


Additionally, the following restrictions apply:


Between Carriage and Road_Seg: LA

4.9. Relationship Pair: Illegal (JuncTurn_to_RoadNode) and RoadNode (RoadNode_to_JuncTurn)

Each record in Illegal is always related to one (and only one) record in RoadNode. Each record in RoadNode is related to zero or more records in Illegal.

4.9.1. From Illegal To RoadNode

Name:	JuncTurn_to_RoadNode
Screen Text:	JuncTurn To RoadNode
Plural:	JuncTurns To RoadNode
Description:	JuncTurn To RoadNode
Primary Class:	RoadNode
Foreign Class:	Illegal

4.9.2. From RoadNode To Illegal

Name:	RoadNode_to_JuncTurn
Screen Text:	RoadNode To JuncTurn
Plural:	RoadNodes To JuncTurn
Description:	RoadNode To JuncTurn
Primary Class:	RoadNode
Foreign Class:	Illegal

4.10. Relationship Pair: Link (Link_to_Road) and Road (Road_to_Link)

Each record in Link is always related to one (and only one) record in Road. Each record in Road is related to one or more records in Link. This relationship pair is represented spatially.

4.10.1. From Link To Road

Name:	Link_to_Road
Screen Text:	Link To Road
Plural:	Links To Road
Description:	Link To Road

4.10.2. From Road To Link

Name:	Road_to_Link
Screen Text:	Road To Link
Plural:	Roads To Link
Description:	Road To Link

4.10.3. Spatial Representation

Class Link is represented via features. Class Road is represented via features. The features are related together via the following boundary/interior intersections:


Additionally, the following restrictions apply:


Between Link and Road: LA

4.11. Relationship Pair: Link (Link_to_Carriageway) and Carriage (Carriageway_to_Link)

See Relationship Pair: Carriage (Carriageway_to_Link) and Link (Link_to_Carriageway)}.

4.12. Relationship Pair: Link (Link_to_Road_barrier) and Road_Bar (Road_barrier_to_Link)

Each record in Link is related to zero or more records in Road_Bar. Each record in Road_Bar can be related to (optionally) one record in Link.

4.12.1. From Link To Road_Bar

Name:	Link_to_Road_barrier
Screen Text:	Link To Road Barrier
Plural:	Links To Road Barrier
Description:	Link To Road Barrier
Primary Class:	Link
Foreign Class:	Road_Bar

4.12.2. From Road_Bar To Link

Name:	Road_barrier_to_Link
Screen Text:	Road Barrier To Link
Plural:	Road Barrier To Links
Description:	Road Barrier To Link
Primary Class:	Link
Foreign Class:	Road_Bar

4.13. Relationship Pair: Road (Road_to_Link) and Link (Link_to_Road)

See Relationship Pair: Link (Link_to_Road) and Road (Road_to_Link)}.

4.14. Relationship Pair: RoadNode (Road_node_1_Road_segment) and Road_Seg (Road_segment_Road_node_1)

Each record in RoadNode is related to one or more records in Road_Seg. Each record in Road_Seg is always related to one (and only one) record in RoadNode. This relationship pair is represented spatially.

4.14.1. From RoadNode To Road_Seg

Name:	Road_node_1_Road_segment
Screen Text:	Road Node 1 Road Segment
Plural:	Road Node 1 Road Segments
Description:	Road Node 1 Road Segment

4.14.2. From Road_Seg To RoadNode

Name:	Road_segment_Road_node_1
Screen Text:	Road Segment Road Node 1
Plural:	Road Segment Road Node 1s
Description:	Road Segment Road Node 1

4.14.3. Spatial Representation

Class RoadNode is represented via point features. Class Road_Seg is represented via simple line features. The features are related together via the following boundary/interior intersections:

Point-Line (0-1): The following "OR"-ed together:

Boundary of RoadNode intersects with boundary of Road_Seg.

4.15. Relationship Pair: RoadNode (Road_node_2_Road_segment) and Road_Seg (Road_segment_Road_node_2)

Each record in RoadNode is related to zero or more records in Road_Seg. Each record in Road_Seg is always related to one (and only one) record in RoadNode. This relationship pair is represented spatially.

4.15.1. From RoadNode To Road_Seg

Name:	Road_node_2_Road_segment
Screen Text:	Road Node 2 Road Segment
Plural:	Road Node 2 Road Segments
Description:	Road Node 2 Road Segment

4.15.2. From Road_Seg To RoadNode

Name:	Road_segment_Road_node_2
Screen Text:	Road Segment Road Node 2
Plural:	Road Segment Road Node 2s
Description:	Road Segment Road Node 2

4.15.3. Spatial Representation

Class RoadNode is represented via point features. Class Road_Seg is represented via simple line features. The features are related together via the following boundary/interior intersections:

Point-Line (0-1): The following "OR"-ed together:

Boundary of RoadNode intersects with boundary of Road_Seg.

4.16. Relationship Pair: RoadNode (Road_node_to_Bridge_Nd) and Brdg_Nd (Brdg_Nd_to_Road_node)

See Relationship Pair: Brdg_Nd (Brdg_Nd_to_Road_node) and RoadNode (Road_node_to_Bridge_Nd)}.

4.17. Relationship Pair: RoadNode (Road_node_to_Tnnl_Nd) and Tnnl_Nd (Tnnl_Nd_to_Road_node)

Each record in RoadNode can be related to (optionally) one record in Tnnl_Nd. Each record in Tnnl_Nd is always related to one (and only one) record in RoadNode. This relationship pair is represented spatially.

4.17.1. From RoadNode To Tnnl_Nd

Name:	Road_node_to_Tnnl_Nd
Screen Text:	Road Node To Road Tunnel 0D
Plural:	Road Node To Road Tunnel 0Ds
Description:	Road Node To Road Tunnel 0D

4.17.2. From Tnnl_Nd To RoadNode

Name:	Tnnl_Nd_to_Road_node
Screen Text:	Road Tunnel 0D To Road Node
Plural:	Road Tunnel 0D To Road Nodes
Description:	Road Tunnel 0D To Road Node

4.17.3. Spatial Representation

Class RoadNode is represented via point features. Class Tnnl_Nd is represented via point features. The features are related together via the following boundary/interior intersections:

Point-Point (0-0): The following "OR"-ed together:

Boundary of RoadNode intersects with boundary of Tnnl_Nd.

4.18. Relationship Pair: RoadNode (Roadnode_to_Road_barrier) and Road_Bar (Road_barrier_to_Road_node)

Each record in RoadNode can be related to (optionally) one record in Road_Bar. Each record in Road_Bar can be related to (optionally) one record in RoadNode. This relationship pair is represented spatially.

4.18.1. From RoadNode To Road_Bar

Name:	Roadnode_to_Road_barrier
Screen Text:	Roadnode To Road Barrier
Plural:	Roadnodes To Road Barrier
Description:	Roadnode To Road Barrier

4.18.2. From Road_Bar To RoadNode

Name:	Road_barrier_to_Road_node
Screen Text:	Road Barrier To Road Node
Plural:	Road Barrier To Road Nodes
Description:	Road Barrier To Road Node

4.18.3. Spatial Representation

Class RoadNode is represented via point features. Class Road_Bar is represented via point features. The features are related together via the following boundary/interior intersections:

Point-Point (0-0): The following "OR"-ed together:

No intersection between RoadNode and Road_Bar allowed.

4.19. Relationship Pair: RoadNode (RoadNode_to_JuncTurn) and Illegal (JuncTurn_to_RoadNode)

See Relationship Pair: Illegal (JuncTurn_to_RoadNode) and RoadNode (RoadNode_to_JuncTurn)}.

4.20. Relationship Pair: Road_Acc (Accident_site_to_Road_segment) and Road_Seg (Road_segment_to_Accident_site)

Each record in Road_Acc can be related to (optionally) one record in Road_Seg. Each record in Road_Seg is related to zero or more records in Road_Acc. This relationship pair is represented spatially.

4.20.1. From Road_Acc To Road_Seg

Name:	Accident_site_to_Road_segment
Screen Text:	Accident Site To Road Segment
Plural:	Accident Site To Road Segments
Description:	Accident Site To Road Segment

4.20.2. From Road_Seg To Road_Acc

Name:	Road_segment_to_Accident_site
Screen Text:	Road Segment To Accident Site
Plural:	Road Segment To Accident Sites
Description:	Road Segment To Accident Site

4.20.3. Spatial Representation

Class Road_Acc is represented via point features. Class Road_Seg is represented via simple line features. The features are related together via the following boundary/interior intersections:

Point-Line (0-1): The following "OR"-ed together:

No intersection between Road_Acc and Road_Seg allowed.

4.21. Relationship Pair: Road_Bar (Road_barrier_to_Road_node) and RoadNode (Roadnode_to_Road_barrier)

See Relationship Pair: RoadNode (Roadnode_to_Road_barrier) and Road_Bar (Road_barrier_to_Road_node)}.

4.22. Relationship Pair: Road_Bar (Road_barrier_to_Link) and Link (Link_to_Road_barrier)

See Relationship Pair: Link (Link_to_Road_barrier) and Road_Bar (Road_barrier_to_Link)}.

4.23. Relationship Pair: Road_Seg (Road_segment_Road_node_1) and RoadNode (Road_node_1_Road_segment)

See Relationship Pair: RoadNode (Road_node_1_Road_segment) and Road_Seg (Road_segment_Road_node_1)}.

4.24. Relationship Pair: Road_Seg (Road_segment_Road_node_2) and RoadNode (Road_node_2_Road_segment)

See Relationship Pair: RoadNode (Road_node_2_Road_segment) and Road_Seg (Road_segment_Road_node_2)}.

4.25. Relationship Pair: Road_Seg (Road_segment_to_Brdg_Seg) and Brdg_Seg (Brdg_Seg_to_Road_segment)

See Relationship Pair: Brdg_Seg (Brdg_Seg_to_Road_segment) and Road_Seg (Road_segment_to_Brdg_Seg)}.

4.26. Relationship Pair: Road_Seg (Road_segment_to_Tnnl_Seg) and Tnnl_Seg (Tnnl_Seg_to_Road_segment)

Each record in Road_Seg can be related to (optionally) one record in Tnnl_Seg. Each record in Tnnl_Seg is always related to one (and only one) record in Road_Seg. This relationship pair is represented spatially.

4.26.1. From Road_Seg To Tnnl_Seg

Name:	Road_segment_to_Tnnl_Seg
Screen Text:	Road Segment To Road Tunnel
Plural:	Road Segment To Road Tunnels
Description:	Road Segment To Road Tunnel

4.26.2. From Tnnl_Seg To Road_Seg

Name:	Tnnl_Seg_to_Road_segment
Screen Text:	Road Tunnel To Road Segment
Plural:	Road Tunnel To Road Segments
Description:	Road Tunnel To Road Segment

4.26.3. Spatial Representation

Class Road_Seg is represented via simple line features. Class Tnnl_Seg is represented via simple line features. The features are related together via the following boundary/interior intersections:

Line-Line (1-1): The following "OR"-ed together:

Boundary of Road_Seg intersects with boundary of Tnnl_Seg AND interior of Road_Seg intersects with interior of Tnnl_Seg.


Additionally, the following restrictions apply:


Between Road_Seg and Tnnl_Seg: LA

4.27. Relationship Pair: Road_Seg (Road_segment_to_Route) and Route (Route_to_Road_segment)

Each record in Road_Seg is related to zero or more records in Route. Each record in Route is related to one or more records in Road_Seg.

4.27.1. From Road_Seg To Route

Name:	Road_segment_to_Route
Screen Text:	Road Segment To Route
Plural:	Road Segment To Routes
Description:	Road Segment To Route
Primary Class:	Road_Seg
Foreign Class:	Route

4.27.2. From Route To Road_Seg

Name:	Route_to_Road_segment
Screen Text:	Route To Road Segment
Plural:	Routes To Road Segment
Description:	Route To Road Segment
Primary Class:	Road_Seg
Foreign Class:	Route

4.28. Relationship Pair: Road_Seg (Road_segment_to_Accident_site) and Road_Acc (Accident_site_to_Road_segment)

See Relationship Pair: Road_Acc (Accident_site_to_Road_segment) and Road_Seg (Road_segment_to_Accident_site)}.

4.29. Relationship Pair: Road_Seg (Road_segment_to_Carriageway) and Carriage (Carriageway_to_Road_segment)

See Relationship Pair: Carriage (Carriageway_to_Road_segment) and Road_Seg (Road_segment_to_Carriageway)}.

4.30. Relationship Pair: Route (Route_to_Road_segment) and Road_Seg (Road_segment_to_Route)

See Relationship Pair: Road_Seg (Road_segment_to_Route) and Route (Route_to_Road_segment)}.

4.31. Relationship Pair: Route (Route_to_Sub_route) and Route (Sub_route_to_Route)

Each record in Route is related to zero or more records in Route. Each record in Route is always related to one (and only one) record in Route.

4.31.1. From Route To Route

Name:	Route_to_Sub_route
Screen Text:	Route To Sub Route
Plural:	Routes To Sub Route
Description:	Route To Sub Route
Primary Class:	Route
Foreign Class:	Route

4.31.2. From Route To Route

Name:	Sub_route_to_Route
Screen Text:	Sub Route To Route
Plural:	Sub Route To Routes
Description:	Sub Route To Route
Primary Class:	Route
Foreign Class:	Route

4.32. Relationship Pair: Route (Sub_route_to_Route) and Route (Route_to_Sub_route)

See Relationship Pair: Route (Route_to_Sub_route) and Route (Sub_route_to_Route)}.

4.33. Relationship Pair: Tnnl_Nd (Tnnl_Nd_to_Road_node) and RoadNode (Road_node_to_Tnnl_Nd)

See Relationship Pair: RoadNode (Road_node_to_Tnnl_Nd) and Tnnl_Nd (Tnnl_Nd_to_Road_node)}.

4.34. Relationship Pair: Tnnl_Nd (Tunnel_Nd_to_Tunnel) and Tunnel (Tunnel_to_Tnnl_Nd)

Each record in Tnnl_Nd is always related to one (and only one) record in Tunnel. Each record in Tunnel is related to zero or more records in Tnnl_Nd.

4.34.1. From Tnnl_Nd To Tunnel

Name:	Tunnel_Nd_to_Tunnel
Screen Text:	Road Tn0 To Tunnel
Plural:	Road Tn0 To Tunnels
Description:	Road Tn0 To Tunnel
Primary Class:	Tunnel
Foreign Class:	Tnnl_Nd

4.34.2. From Tunnel To Tnnl_Nd

Name:	Tunnel_to_Tnnl_Nd
Screen Text:	Tunnel To Road Tn0
Plural:	Tunnels To Road Tn0
Description:	Tunnel To Road Tn0
Primary Class:	Tunnel
Foreign Class:	Tnnl_Nd

4.35. Relationship Pair: Tnnl_Seg (Tnnl_Seg_to_Road_segment) and Road_Seg (Road_segment_to_Tnnl_Seg)

See Relationship Pair: Road_Seg (Road_segment_to_Tnnl_Seg) and Tnnl_Seg (Tnnl_Seg_to_Road_segment)}.

4.36. Relationship Pair: Tnnl_Seg (RoadTn1_to_Tunnel) and Tunnel (Tunnel_to_RoadTn1)

Each record in Tnnl_Seg is always related to one (and only one) record in Tunnel. Each record in Tunnel is related to zero or more records in Tnnl_Seg.

4.36.1. From Tnnl_Seg To Tunnel

Name:	RoadTn1_to_Tunnel
Screen Text:	RoadTn1 To Tunnel
Plural:	RoadTn1s To Tunnel
Description:	RoadTn1 To Tunnel
Primary Class:	Tunnel
Foreign Class:	Tnnl_Seg

4.36.2. From Tunnel To Tnnl_Seg

Name:	Tunnel_to_RoadTn1
Screen Text:	Tunnel To RoadTn1
Plural:	Tunnels To RoadTn1
Description:	Tunnel To RoadTn1
Primary Class:	Tunnel
Foreign Class:	Tnnl_Seg

4.37. Relationship Pair: Tunnel (Tunnel_to_RoadTn1) and Tnnl_Seg (RoadTn1_to_Tunnel)

See Relationship Pair: Tnnl_Seg (RoadTn1_to_Tunnel) and Tunnel (Tunnel_to_RoadTn1)}.

4.38. Relationship Pair: Tunnel (Tunnel_to_Tnnl_Nd) and Tnnl_Nd (Tunnel_Nd_to_Tunnel)

See Relationship Pair: Tnnl_Nd (Tunnel_Nd_to_Tunnel) and Tunnel (Tunnel_to_Tnnl_Nd)}.

5. Code Lists

Code lists are lists of legal values which you can in your programs to ensure that the user picks from a fixed list and which the system uses to define uniquely each subclass of a superclass.

The code lists are listed here with all the codes which make up each code list.

5.1. Code List: BarType

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	Unknown
1	Gate	A barrier which can be swung in a horizontal plane across the road.
2	Boom Gate	A barrier which can be swung in a vertical plane across a road.
3	Signalled Level Crossing	A point at which a railway crosses a road and which is controlled by signals.
4	Non-signalled Level Crossing	A point at which a railway crosses a road without control by signals.
5	Ford	A point at which a road crosses a watercourse without a bridge.
6	Signalled Pred Crossing	Signalled Predestrian Crossing
7	Non Signalled Pred Cross	Non Signalled Predestrian Cros

5.2. Code List: BltType

This list contains the following items:

Name	Screen Text	Description
R	Residential	A Built Area which is predominantly residential.
C	Commercial	A Built Area which is predominantly commercial.

5.3. Code List: BridgeTy

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	Unknown
1	Single Lane	A bridge over which one vehicle can travel at a time.
2	Double Lane	A bridge over which traffic can travel in both directions simultaneously.

5.4. Code List: CarrigTy

This list contains the following items:

Name	Screen Text	Description
A	Both directions	A carriageway with traffic flow in both directions.
B	Chainage direction	A Carriageway with traffic flow in the direction of the chainage.
C	Reverse chainage direction	A Carriageway with traffic flow against the direction of the chainage.
R	Ramp	A ramp.

5.5. Code List: JuncTurn

This list contains the following items:

Name	Screen Text	Description
A	All turns possible	All turning options are possible.
S	Some turns possible	Some turning options are possible. (refer to separate turnings table)
N	No turns possible	No turns are possible.
U	Turn status unknown	Turn status for this intersection has not been determined

5.6. Code List: RdClass

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	Unknown
1	National/State Highway	All weather formed roads which connect major regions or significant towns.
2	Major Arterial Road	All weather formed roads which connect National/State Highways.
3	Arterial Road	Roads providing access to local communities or high volume residential roads.
4	Access Road	Roads providing access to properties both suburban and rural.
5	Single Lane Access Road	Generally all weather roads of reduced width capable of carrying heavy vehicles.
6	Vehicular Track - 2WD	Unformed road navigatable most of the time.
7	Vehicular Track - 4WD	Unformed road navigatable generally by 4 wheel drive vehicles.
8	Track	Non vehicular access for foot, bike or horse traffic.
9	Unclassified	Unknown classification.

5.7. Code List: RdNdFeat

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	Unknown
0	Normal node	A node that is not associated with any particular feature.
1	Road End	The end of a ROAD SEGMENT
2	Signalised Intersection	An intersection at which traffic is controlled by some form of signalling device
3	Small roundabout	A node which represents a small roundabout
4	Large Roundabout	A node which is placed at the centre of a large roundabout.
5	Mountable Roundabout	A small roundabout which a vehicle can drive over if required.
6	Road Bridge	A road bridge which is depicted as a single point.
7	Road Tunnel	A Road Tunnel which is depicted as a single point.
8	Road Barrier	Some form of barrier or potential barrier across a road.
9	Bridge & Tunnel	A point at which a road crosses another road at a different level.
10	Bridge & Barrier	A point at which a barrier and bridge are coincident.
11	Tunnel & Barrier	A point at which a tunnel and barrier are coincident.
12	Bridge & Tunnel & Barrier	A point at which a Bridge, Tunnel & Barrier are coincident.

5.8. Code List: RdSgFeat

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	Unknown
0	Normal Road Segment	A Road Segment that is not associated with a particular feature.
1	Bridge	A Road Segment which is also a Bridge.
2	Tunnel	A Road Segment which is lso a Tunnel.
3	Road Connector	A Road Segment which is also a Road Connector.
4	One way	A Road Segment representing a section of road on which traffic travels in one di
5	Private	A Road Segment representing a privately owned road.
6	Proposed	The road segment represents a proposed road.
7	Under Construction	Road Under Construction

5.9. Code List: RoutePur

This list contains the following items:

Name	Screen Text	Description
1	Tourist Route	Tourist Route
2	Metro Bus Route	Metro Bus Route
3	Tiger Line Bus Route	Tiger Line Bus Route
-1	Unknown	Unknown

5.10. Code List: TunnelTy

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	Unknown
1	Circular	A tunnel with a circular profile
2	Box	A tunnel with a rectangular profile.
3	Gantry	A structure which has been built across a road and which restricts the height.
4	Overhead Line	Some form of overhead line for power or other purpose.

6. Miscellaneous Information

The miscellaneous settings which are part of the data model currently refer only to system variables.

6.1. Defined System Variables

These are listed as follows:

Name	Setting