DataModel

 

Network model

 

The network is build within Administrative areas to afford updating by responsible  local authorities.

Administrative areas

Polygon feature class AdministrativeArea
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry	Yes
AdminAreaID	ShortInteger	No			0			Identifier of the Administrative Area
ISO	String	Yes		ISOCode			3	ISO code of the Administrative Area
NameEnglish	String	Yes					80	English name of the Administrative Area
NameLocal	String	Yes					80	Local name of the Administrative Area
AreaType	ShortInteger	Yes		AreaCode	0			One-digit area type code
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the link
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data
GlobalID	GUID	No			0			Global Unique Identifier
Shape_length	Double	Yes			0	0
Shape_area	Double	Yes			0	0

 

Coded value domain AreaCode
Code	Description
1	Country
2	Region
3	District
4	Commune

 

Coded value domain ISOCode
Code	Description
1	NUTS0
2	NUTS1
3	NUTS2
4	NUTS3

 

Transport areas

 

The Transport Network is part of Transport areas.

 

Polygon feature class TransportArea
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry	Yes
Transport-AreaID	ShortInteger	No			0			Identifier of the Transport Area
Transport-AreaType	ShortInteger	Yes		TransportAreaType	0			One-digit area type code
Transport-AreaNamID	ShortInteger	Yes			0			Identifier of the TransportArea Names
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the link
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data
GlobalID	GUID	No			0			Global Unique Identifier
Shape_length	Double	Yes			0	0
Shape_area	Double	Yes			0	0

 

 

Coded value domain TransportAreaType
Code	Description
1	RoadArea
2	RoadServiceArea
3	RailwayArea
4	RaiwayStationArea
5	RailwayYardArea
6	WaterwayArea
7	PortArea

 

Transportation Network

 

The Transportation Network consists of ComplexEdgeFeatures and SimpleJunctionFeatures. The ComplexEdgeFeatures correspond to one or more JunctionsFeatures. They are specified as Centerlines. Subclasses of Centerlines are Road, Rail, WaterWay, BicyclePath and WalkingPath. The SimpleJunctionFeatures are specified to be Intersections. Subtypes are at-grade intersection where two or more routes meet,  railroad grade crossing where a route cross a railroad, access point, which represents a location on a route where a nonmapped facility connects to mapped facility like shopping center driveway. Together these objects form the Geometric Network.

 

 

 

 

 

Like the definition in the traditional networks the Edgefeatures are called Links and the Junctionfeatures Nodes.

 

 

Centerlines

 

Simple feature class Link
Field name	Data type		Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry		Yes
TransportSubclasses	Short Integer		No			0			Subclasses
LinkID	String		No					80	Identifier of link
FromNode	String		No					80	Starting node
ToNode	String		No					80	Ending node
AdministativeAreaID	String		No					80	Identifier of the Administrative Area
LinkNameID		Long Integer	Yes			0			Identifier of the traffic facility  names
LinkCourse		Short Integer	Yes		LinkCourde	0			Type of course
LinkType	Short Integer		Yes	1	LinkTypes	0			Transport function
Brunnel	Short Integer		Yes	1	Brunnel	0
LRMPositionID	Long Integer		Yes			0			Identifier of LRM position
Direction	Short Integer		Yes	1	DirectionTypes	0			Direction
RecordDate	Date		Yes						Date record was created
RecordStatus	Short Integer		Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer		Yes	1	EntityCodes	0			Status of the link
FromDate	Date		Yes						Starting date of validity
ToDate	Date		Yes						Ending date of validity
DataOrigin	Short Integer		Yes		DataOriginCodes	0			Origin of the data
GlobalID	GUID		No			0			Global Unique Identifier
Shape_length	Double

 

Each links has a permanent Identity LinkID build  by the Identifier of the regional Administrative area and x-coordinate of the starting point (FromNode) and the y-coordinate of the ending point (ToNode).

 

The LinkNameID refers to a table with a collection of road names.

 

There are different kind of LinkNames, e.g EuroRoadNumber like “E45”, StateRoadName like “A 9” or “B 10”, and StreetName like “Westerndorfer Straße”. The LinkNameTable  collects all these names of each link.

 

 

 

 

 

 

 

                                                

 

Table LinkNames
Field name	Data type		Allows nulls		Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
LinkNameID	GUID		Yes				0			Identifier of the link name collection
EuroRoadNumber	String		Yes						50	Name of the Europe road
StateRoadName		String		Yes					50	Administrative road name
StreetName	String		Yes						50	Street name
Name	String		Yes						50	Other link name
RecordDate	Date		Yes							Date record was created
RecordStatus	Short Integer		Yes		1	RecordCodes	0			Status of record
EntityStatus	Short Integer		Yes		1	EntityCodes	0			Status of the link
FromDate	Date		Yes							Starting date of validity
ToDate	Date		Yes							Ending date of validity
DataOrigin	Short Integer		Yes			DataOriginCodes	0			Origin of the data

 

Relationship class LinkHasNames
Type	Simple
Cardinaly	One to one	Forward label Has
Notification	None	Backward label Represents
Origin table		Destination table
Name           Link Primary key LinkNameID Foreign key LinkNameID		Name LinkNames

 

Coded value domain LinkTypes  Code Description 1 Motorway 2 Trunk 3 Primary 4 Secondary 5 Tertiary 6 Local Street 7 Service Road 8 Track 9 Bridleway 10 Cycleway 11 Footway 12 Path 13 Floors 14 Stairs 15 Lifts			Coded value domain LinkCourse  Code Description 1 Transport facility 2 Transport facility equal carriageway 3 Carriageway 4 Lane 5 Shoulder 6 Ramp 7 Roundabout 10 Main track 11 Multi- track
Coded value domain LinkTypes
Code	Description
20	Rail
21	Commuter railway
22	Underground railway
23	Tram
30	Other

 

 

Coded value domain LinkTypes
Code	Description
30	Stream
31	River
32	Canal
33	Drain

 

 

Coded value domain Brunnel
Code	Description
1	Bridge
2	Tunnel

Intersections

 

The Nodes are build to serve information about road and rail intersections, administrative border  crossing as well as identities and names of the connected links. This information can be used e.g. for TPEG messages.

 

Simple feature class Node
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry	Yes
NodeID	String	No					80	Identifier of the Node
NodeType	Short Integer	No	1	Node Code	0			Type of node
NodeName	String						80
LinkType	ShortInteger	No	1	LinkType	0			Type of highest connected Link
AdministrativeAreaID	String	No					80	Identifier of the Administrative Area
LinkNameID	Long Integer	Yes			0			Identifier of the collection of names of connected streets or roads
LinkNoID	Long Integer	Yes			0			Identifier of the collection of linkIDs of connected streets or roads
LRMPositionID	Long Integer	Yes			0			Identifier of LRM position
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the node
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data
GlobalID	GUID	No			0			Global Unique Identifier

 

 

 

 

Cded value domain NodeType
Code	Description
1	Intersection transport facility
2	Intersection transport facility equal carriageway
3	Intersection carriageway
4	Administrative line
5	Bridge/tunnel enter
6	Cul de sac
7	Center of Circle
8	Border Crossing
20	Other

 

Cded value domain NodeType
Code	Description
10	Station
11	Tram stop
20	Other

 

The NodeID is a function of Latitude and Longitude

 

round(int(@Value(_x)*1000000))*100000000+int(@Value(_y)*1000000)

 

 

Table LinkToNodeID
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
NodeID	String	Yes					80	Identifier of the node
LinkID	String	Yes					80	Identifier of the link

 

 

Relationship class NodeHasLinks
Type	Simple
Cardinaly	One to many	Forward label Has
Notification	None	Backward label Represents
Origin table		Destination table
Name           Node Primary key NodeID Foreign key NodeID		Name LinkToNodeID

 

 

Coded value domain EntityCodes  Code Description 1 Proposed 2 Under review 3 In design 4 Under construction 5 Substantial completion 6 Open to traffic 7 Accepted, in service 11 Damaged 12 Under repair 21 Jurisdiction transferred 31 Closed to traffic 32 Removed from service 33 Abandoned 34 Surplused 35 Stored 86 Demolished	Coded value domain RecordCodes  Code Description 0 Work in progress 1 Proposed 2 Withdrawn 3 Rejected 4 Accepted 5 Active 6 Replaced 7 Retired
Coded value domain DirectionTypes  Code Description 0 To-From travel permitted 1 To travel permitted 2 From travel permitted	Coded value domain DataOriginCodes  Code Description 1 Open Street Map 2 Basis-DLM (AAA) 3 NavTeq 4 Tele Atlas 11 IPM geoNet
Coded value domain SideCode  Code Description L Left side only R Right side only B Both sides & street S Street only N Both sides & not street	Coded value domain Referents  Code Description 0 None 1 Edge of pavement 2 Face of curb 3 Back of curb 4 Back of sidewalk 5 Edge of right of way 6 Centerline of road 7 Centerline of ditch

 

 

Coded value domain OffsetDir
Code	Description
0	None
1	In
2	Out
3	North
4	East
5	South
6	West
7	Toward
8	Away from

 

 

 

 

 

Linear Referencing

 

A sequence of Links in one direction are building a directed Polyline called Route. This linear object together with an implementation of a linear referencing system (LRS) allows the use of different kinds of linear referencing methods (LRM) like dynamic segmentation.

 

The table LinkSequence represents a many-to-many relationship that can be used to identify all segments participating in a route and also when one segment is shared by multiple (overlapping) routes

 

Table LinkSequence
Field name	Data type	Allows nulls	Default Value	Domain		Precision	Scale	Length
OBJECTID	Object ID
LinkID	String	Yes						80	Identifier of the Link
RouteID	String	Yes						80	Identifier of the route
TraversalID	String	Yes						80	Identifier of the traversal
RecordDate	Date	Yes							Date record was created
RecordStatus	Short Integer	Yes	1		RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1		EntityCodes	0			Status of the link
FromDate	Date	Yes							Starting date of validity
ToDate	Date	Yes							Ending date of validity
DataOrigin	Short Integer	Yes			DataOriginCodes	0			Origin of the data

 

 

Relationship class LinksHaveSequence
Type	Simple
Cardinaly	One to many	Forward label Sequence
Notification	None	Backward label Links
Origin table		Destination table
Name           Links Primary key LinkID Foreign key LinkID		Name LinksSequence

 

 

 

The use of directed lines and polylines with linear measures is to find exactly the position of objects and events on and at main roads, railways and waterways like:

 

·         Building sites

·         Measuring points

·         Traffic information (accident, weather)

 

Simple feature class Route
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry	Yes
RouteID	String	No					80	Identifier of the route
RouteName	String	Yes					80	Route name
RouteType	Short Integer	No		RouteTypes	0
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the link
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data
GlobalID	GUID	No			0			Global Unique Identifier
Shape_length	Double

 

Coded value domain RouteTypes
Code	Description
1	Road
2	Railroad
3	Navigable waterway
4	Transit pattern
5

 

Relationship class RoutesHaveLinkSequence
Type	Simple
Cardinaly	One to many	Forward label Route
Notification	None	Backward label Sequence
Origin table		Destination table
Name           Route Primary key RouteID Foreign key RouteID		Name LinkSequence

The LRMpositionID allows multiple datums  to be accommodated, for both Linear Referencing Methods like miles from a selected StartNode and geographic positions in coordinates. An attributed relationship class handles the LRM position to geographic equivalencies, as this is a many to many relationship. So every Route can be build out of n links, and any link can be related to m Routes.

 

 

Table LRMPosition
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry	Yes
LRMPositionID	String	No					80	Identifier of LRM position
LRMType	Short Integer	Yes		LRMTypes	0			Type of LRM
RouteID	String	No					80
FromMeasure	Double	Yes			7	3		Starting LRM measure
ToMeasure	Double	Yes			7	3		Ending LRM measure
SideOfRoad	String	Yes		SideCode			1	Side of road
OffsetReferent	Short Integer	Yes		Referents	0			Lateral offset referent
OffsetDirection	Short Integer	Yes		OffsetDir	0			Lateral offset direction
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the link
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data

 

The LinksHaveLRMPositions table is the relationship between the Links and their position on a route. All the position values are stored in the LRMPosition table, but because there is a many-to-many relationship between these two tables, the data is maintained in a bridge table.

 

Table LinksHaveLRMPositions
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
LinkID	String	Yes					80	Identifier of the Link
LRMPositionID	GUID	Yes			0			Identifier of the LRM position

 

Relationship class LinksToLinksHaveLRMPositions
Type	Simple
Cardinaly	One to many	Forward label LinksHaveLRMPositons
Notification	None	Backward label Links
Origin table		Destination table
Name           Links Primary key LinkID Foreign key LinkID		Name LinksHaveLRMPositions

 

 

 

Table Geoposition
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
GeoPositionID	GUID	Yes			0			Identifier of the coordinate
Datum	Short Integer	Yes		Datums	0			Type of datum
Latitude	Double	Yes			7	3		Latitude coordinate
Longitude	Double	Yes			7	3		Longitude coordinate
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the link
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data

 

Attributed Relationship class LRMPositionHasGeoPosition
Type	Simple
Cardinaly	Many to many			Forward label Has
Notification	None			Backward label Locates
Origin table				Destination table
Name           LRMPosition Primary key LRMPositionID Foreign key LRMPositionID				Name GeoPosition
Field name		Data type	Allows nulls	Precision	Scale	Length
OBJECTID		Object ID
LRMPositionID		GUID	Yes	0
GeoPositionID		GUID	Yes	0

 

 

Coded value domain LRMTypes  Code Description 1 Route milelog 2 Note-offset 3   4 Other

Coded value domain Datums  Code Description 1 WGS84 2   3   4

 

 

 

 

Objects

 

All kind of point and line objects can be referenced to the  PermanentNet like

 

·         POI

·         Devices (detectors)

·         TMCLocations

·         Other geometric networks

 

 

Simple feature class PointObjects
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
Shape	Geometry	Yes
ObjectID	String	No					80	Identifier of the object
ObjectName	String	Yes					80	Name of object
LRMPositionID	Long Integer	Yes			0			Identifier of LRM position
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the station
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data
GlobalID	GUID	No			0			Global Unique Identifier

 

They can be referenced to the route with an Event table.

 

Table Event
Field name	Data type	Allows nulls	Default Value	Domain	Precision	Scale	Length
OBJECTID	Object ID
EventID	GUID	Yes			0			Identifier of the event
LRMPositionID	Long Integer	Yes			0			Identifier of LRM position
RecordDate	Date	Yes						Date record was created
RecordStatus	Short Integer	Yes	1	RecordCodes	0			Status of record
EntityStatus	Short Integer	Yes	1	EntityCodes	0			Status of the link
FromDate	Date	Yes						Starting date of validity
ToDate	Date	Yes						Ending date of validity
DataOrigin	Short Integer	Yes		DataOriginCodes	0			Origin of the data

 

The same structure of Event tables can be used for point and line objects, because the LRMPosition represents the FromMeasure and ToMeasure value, but a point event has only a FromMesure value in the LRMPosition table.