Updated: 1/12/2007

Scales 1:25 000 &
1:100 000

RailTransport Anno

RailTransportAnno

RailTransport

Annotation

Type associated with the Rail Transport Feature Dataset

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

ANNOTATION CLASS IDENTIFER (ANNOTATIONCLASSID) [Integer;Yes;0;10;0;Pop_Aut] This is the Annotation Class Identifier which is used to define annotation subtypes.

The following annotation classes exist in RailTransportAnno;
Arial6ptItalicLeft
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptLeft
ArialNarrow7ptRight

FEATURE (FEATURE) [String;Yes;32;0;0;Pop_Req] The code which identifies the class of topographic feature represented by the annotation. This field must be a legitimate feature class name.

Acceptable Domain Entries from dm_RailTransportFCs;
RailwayBridgePoints
RailwayCrossingLines
Railways
RailwayStopPoints
RailwayTunnelLines
RailwayTunnelPoints

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specifcation documentation for ease of reference.

Only Annotation associated with, or derived from, entities in feature classes grouped within the RailTransport feature dataset should exist within the RailTransportAnno feature class.

Wherever possible annotation should be stored using the subclasses indicated under AnnotationClassID. Annotation stored as inline text should be kept to a minimum.

Type for large polygons and long linear features may be held in an annotation feature for each word to allow for spacing and differences in orientation, see Section 2 chapter 4.

Annotation should not contain any HTML tags within the blob element, nor should it contain any special characters.

Editing and placement of Annotation should be conducted in the appropriate MGA 1994 zone to ensure the spatial position of type on the map face can be correctly represented.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules


Related Features


Related Chapters

Section 2 Chapters 5, 9, 10

Related Products

NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway

Railways

RailTransport

Polyline

A transportation system using one or more rails to carry freight or passengers.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)     1250
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m) 125 500 1250

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the Railway Line. This item should be populated where name is known.

ROUTE NAME (ROUTENAME) [String;Yes;60;0;0;Pop_Dep] The name of the entire railway line route. This items should be populated where name is known.

SECTION NAME (SECTIONNAME) [String;Yes;60;0;0;Pop_Wk]

The name of the individual sections of railway lines.

GAUGE (GAUGE) [String;Yes(No);20;0;0;Pop_Req] Code for gauge;

Acceptable Domain Entries from dm_RailwayGauge at 25K and 100K as well as acceptable entries for the 250K field;
Not Applicable
Standard: 1435mm
Broad: 1600mm
Narrow: 1067mm
Light
Other
Unknown
Standard-Broad
Standard-Narrow

OWNER (OWNER) [String;Yes;60;0;0;Pop_Wk] The owner of feature/Facility;

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus at 25K and 100K as well as acceptable entries for the 250K field;
Operational
Abandoned
Under Construction
Dismantled - 25K and 100K scales only

TRACKS (TRACKS) [String;Yes(No);8;0;0;Pop_Req] Code for number of tracks;

Acceptable Domain Entries from dm_RailwayTracks at 25K and 100K as well as acceptable entries for the 250K field;
One
Multiple
Unknown

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity;

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

206 - Single or Unknown
210 - Multiple
208 - Light
209 - Abandoned
0 - Railway coincident with jetty, Railway Dismantled

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences. Dismantled railways, including those on the latest previous edition map or base data/material will be shown.

1:100 000

Size and any other selection criteria apply to all feature occurrences. Dismantled railways, including those on the latest previous edition map or base data/material will be shown.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist. Dismantled railways, including those on the latest previous edition map or base data/material will not be shown.

Short lengths of light railways in position only during the seasonal harvesting of crops will be omitted.

Where scale limits the depiction of all tracks, show only those that depict a general representative pattern.

General - All Scales

All railways and permanent sections of light railways will be shown.

Light railways are lightly constructed railways or tramways used for special purposes, for example scenic railways.

Where railways exist upon a jetty they must be coincident for the length of the railway.

All railways, including sidings and marshalling yards should be shown to scale if greater than the minimum size criteria.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Nodes will appear at all Railway intersections.

Railway Crossing Lines (feature class) will be coincident with the equivalent section of the Railway. There must be a vertex in the Railway feature at the exact location of the start and end points of the Railway Crossing Line (feature class). The Railway must continue outwards from both endpoints of the Railway Crossing Lines (feature class).

Railway Tunnel Line will be coincident with the equivalent section of the Railway. There must be a vertex in the Railway feature at the exact location of the start and end points of the Railway Tunnel Line. The Railway must continue outwards from both endpoints of the Railway Tunnel Line.

Railway Bridge Points must fall exactly over a vertex on the Railway feature.

Railway Stations will be coincident with a vertex on a Railway.

Railway Tunnel Points will be coincident with a Vertex on the associated Railway.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Railways cannot overlap the following (except when associated with a Railway Bridge Line);
Canal areas, Perennial lakes, Perennial watercourse areas, Flood Irrigation Storage, Town Rural Storage.

Railways cannot overlap;
Sea except when coincident with a Jetty.

Railways cannot intersect;
Discontinuties (feature class).

Map Rules

1:25 000

Railways will be labelled with their 'Route Name'.

1:100 000

Railways will be labelled with their 'Route Name'.

1:250 000

Railways will be labelled with their name.

General - All Scales

All railways, including sidings and marshalling yards should be shown to scale if greater than the minimum size criteria.

Where scale limits the depiction of all tracks, show only those that depict a general representative pattern.

Abandoned railways will be labelled 'abandoned'.

Railway lines will not be labelled with their gauge width.

Railways which are dismantled will not be shown on the map face.

Railways will be masked where black type unavoidably overprints the feature. The break measurement will be 0.2 mm on either side of the type where it crosses the feature. (Note: the feature will be masked only on the map and will be complete in the data.)

Related Features

Ferry Route Line, Prohibited Area Boundary Line, Railway Bridge Line, Railway Bridge Point, Railway Causeway, Railway Station, Railway Tunnel Line, Railway Tunnel Point, Reserve Boundary Line , Transition point

Related Chapters

Section 2 chapter 2.2.3
Section 3 chapter 5.3, 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway Bridge Line

RailwayCrossingLines

RailTransport

Polyline

A structure erected over a depression or obstacle to carry rail traffic.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m) 40 40 100
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m) 40 40 100

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Bridge Line

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature

1

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.

RailwayBridgeLine

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the railway bridge. This item should be populated where name is known.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus;
Abandoned
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

260
0 - Coincident road and rail bridge

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Width of symbol in millimetres;
0.15 - for bridge on light railway
0.25 - for bridge on other railways

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

For linear features, where the structure has been constructed only to prevent an intersection with other road or rail traffic the rail overpass feature type should be utilised instead of the rail bridge line feature type.

Bridges will be shown as points when they are shorter than 40 metres.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

For linear features, where the structure has been constructed only to prevent an intersection with other road or rail traffic the rail overpass feature type should be utilised instead of the rail bridge line feature type.

Bridges will be shown as points when they are shorter than 40 metres.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist (dismantled).

Only significant bridges will be shown. The significance of the bridge depends on the number of bridges in the vicinity, the importance of the road etc. As guidance, the selection from the latest previous edition map will be taken and a similar approach applied to any new bridges

Bridges will be shown as points when they are shorter than 100 metres.

General - All Scales

The railway line for which the bridge was made need no longer exist, however, to be shown the bridge must still exist.

Bridges of distinctive construction may be textnoted (e.g 'drawbridge','swing bridge').

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Bridge Lines will be coincident with the equivalent section of the Railway. There must be a vertex in the Railway feature at the exact location of the start and end points of the Railway Bridge Line. The Railway must continue outwards from both endpoints of the Railway Bridge Line.

Railway Bridge Lines may be shown off the rail network if they are on a dismantled railway.

Inter-Feature Relationship Rules - External to Associated Dataset

1:250 000

A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody.

General - All Scales

Bridges which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers.

Map Rules

1:25 000

A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody. This adjustment will be conducted in the Carto Generalisation Line feature type.

1:100 000

A bridge may be required to be extended to ensure that the map symbol endpoints (wings) effectively fall outside the width of its associated waterbody. This adjustment will be conducted in the Carto Generalisation Line feature type.

General - All Scales

Bridges of distinctive construction may be labelled (e.g 'drawbridge','swing bridge').

Railway bridges will be named, where name is known.

Only Railway bridges that are not 'dismantled' will be shown on the map.

Railway bridges 'under construction' will be labelled 'under construction'

Related Features

Railway , Road Bridge Line, Road Bridge Point

Related Chapters

Section 3 chapters 5.8 and 5.11.2
Appendix U chapter 2.2.5

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway Bridge Point

RailwayBridgePoints

RailTransport

Point

A structure erected over a depression or obstacle to carry rail traffic.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Bridge Point

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the railway bridge. This item should be populated where name is known.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus;
Abandoned
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity;

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

260
0 - Coincident road and rail bridge

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Width of symbol in millimetres;
0.15 - for bridge on light railway
0.25 - for bridge on other railways

ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise;

0 - 360

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Bridges will be shown as lines when they are equal to or greater than 40 metres.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

Bridges will be shown as lines when they are equal to or greater than 40 metres.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist (dismantled).

Only significant bridges will be shown. The significance of the bridge depends on the number of bridges in the vicinity, the importance of the road etc. As guidance, the selection from the latest previous edition map will be taken and a similar approach applied to any new bridges

Bridges will be shown as Lines when they are equal to or greater than than 100 metres.

General - All Scales

The railway line for which the bridge was made need no longer exist, however, to be shown the bridge must still exist.

Bridges of distinctive construction may be textnoted (e.g 'drawbridge','swing bridge').

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Bridge Points must fall exactly over a vertex on the Railway feature.

Railway bridges may be shown off the rail network if they are on a dismantled railway.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Bridges which carry both road and rail traffic will be held as coincident road bridge and railway bridge features in their respective layers.

Map Rules

General - All Scales

Bridges of distinctive construction may be labelled (e.g 'drawbridge','swing bridge').

Railway bridges will be named, where name is known.

Only Railway bridges that are not 'dismantled' will be shown on the map.

Railway bridges 'under construction' will be labelled 'under construction'

Related Features

Railway , Road Bridge Line, Road Bridge Point

Related Chapters

Section 3 chapters 5.3, 5.8, 5.9 and 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway Causeway

RailwayCrossingLines

RailTransport

Polyline

An embankment of earth or masonry erected across open water or area subject to inundation and carrying a railway.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m) 50 50 500
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m) 50 200 500

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Causeway

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature

2

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.

RailwayCauseway

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the railway causeway. This item should be populated where name is known.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus;
Abandoned
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

245 - Rail only
0 - Coincident road and rail causeway

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Width of symbol in millimetres;
0.15 - on light railway
0.25 - on other railways

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist (dismantled).

General - All Scales

The railway line for which the causeway was made need no longer exist, however, to be shown the causeway must still exist.

Causeways which carry both road and rail traffic will be held as coincident road causeway and railway causeway features in their respective layers.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Causeway will be coincident with the equivalent section of the Railway. There must be a vertex in the Railway feature at the exact location of the start and end points of the Railway Causeway. The Railway must continue outwards from both endpoints of the Railway Causeway.

Railway Causeways may be shown off the rail network if they are on a dismantled railway.

Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules

General - All Scales

Railway causeways will be labelled 'causeway'. Where road and railway causeways are coincident only one label 'causeway' will appear on the map face.

Only Railway Causeways that are not 'dismantled' will be shown on the map

Related Features

Railway , Road Causeway

Related Chapters

Section 3 chapter 5.8 and 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000 &
1:100 000

Railway Overpass

RailwayCrossingLines

RailTransport

Polyline

A separation of surface levels constructed to prevent direct intersection with other rail or road networks.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m) 10 10  
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m) 10 40  

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Overpass

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature

3

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.

RailwayOverpass

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the railway overpass. This item should be populated where name is known.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus;
Abandoned
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

266
0 - Coincident road overpass

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Width of symbol in millimetres;
0.15 - for overpass on light railway
0.25 - for overpass on other railways

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Overpass will be coincident with the equivalent section of the Railway. There must be a vertex in the Railway feature at the exact location of the start and end points of the Railway Overpass. The Railway must continue outwards from both endpoints of the Railway Overpass.

Railway overpasses may be shown off the rail network if they are on a dismantled railway.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Overpasses which carry both road and rail traffic will be held as coincident road overpass and railway overpass features in their respective layers.

Map Rules

General - All Scales

Railway overpasses will be named, where name is known.

Only Railway Overpasses that are not 'dismantled' will be shown on the map

Related Features

Railway , Road Bridge Line, Road Bridge Point, Road Overpass, Road and Rail Causeway

Related Chapters

Section 3 chapters 5.8 and 5.11.2

Related Products

GEODATA LITE TOPO100K, NTMS 100K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway Station

RailwayStopPoints

RailTransport

Point

A recognised stopping place for trains where passengers may board or alight or freight be loaded or unloaded. There may or may not be a platform. The railway station may not be in use.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Station

SUBTYPE NUMBER (TYPE) [Integer;Yes(No);0;5;0;Pop_Req] The numeric value assigned to sub classify the feature

1

DESCRIPTION OF SUBTYPE (TYPE_DESCRIPTION) [String; No; 32; Pop_Req] The textual description of the subtype classification.

RailwayStation

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the Railway Station. This item must be populated.

RAILWAY STATION STATUS (RAILSTATIONSTATUS) [String;Yes;40;0;0;Pop_Req] Railway Station Status in Relation to Railway Line

Acceptable Domain Entries from dm_RailStationStatus;
Abandoned on Abandoned Railway
Abandoned on Dismantled Railway
Abandoned on Operational Railway
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity;

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

222
0 - when situated on a underground railway

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise;

Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:250 000

All railway stations on operational and abandoned lines will be shown, including disused railway stations. An exception will be railway stations where there is clear evidence that the buildings and associated structures no longer exist (i.e. have been dismantled).

Railway stations on dismantled railway lines will not be shown as railway stations (see Inter Feature Relationship Rules -External to Associated Dataset for more information).

General - All Scales

Railway stations on underground lines will not be symbolised (e.g symbol = 0 non printing).

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Stations will be coincident with a vertex on a Railway.

Inter-Feature Relationship Rules - External to Associated Dataset

1:25 000

The names of dismantled Railway Stations and Railway stations on dismantled railway lines will be depicted as feature type 'Place Name' if the same name is not in use for another 'Place Name', 'Populated Place' or 'Built Up Area' feature. Unless there is clear evidence they no longer exist (i.e. have been dismantled), the buildings will be retained shown as Building Point and/or Building Area features as appropriate.

1:100 000

The names of dismantled Railway Stations and Railway stations on dismantled railway lines will be depicted as feature type 'Place Name' if the same name is not in use for another 'Place Name', 'Populated Place' or 'Built Up Area' feature. Unless there is clear evidence they no longer exist (i.e. have been dismantled), the buildings will be retained shown as Building Point and/or Building Area features as appropriate.

1:250 000

Dismantled Railway Stations and Railway stations on dismantled railway lines will not be shown as railway stations. Their names will be depicted as feature type 'Place Name' if the same name is not in use for another 'Place Name', 'Populated Place' or 'Built Up Area' feature. Unless there is clear evidence they no longer exist (i.e. have been dismantled), the buildings will be retained shown as Building Point and/or Building Area features as appropriate.

General - All Scales

A Railway Station situated on a Jetty must be coincident with a vertex on both the Jetty and its associated Railway Line.

Railway stations will be cloned as a Place Name if the same name is not in use for another Place name or Populated Place.

Map Rules

1:25 000

All railway stations will be named unless station is not symbolised.

1:100 000

All railway stations will be named unless station is not symbolised.

1:250 000

Railway stations within Built Up Areas will only be named where space permits, all other railway stations will be named unless station is not symbolised.

General - All Scales

Type for Railway stations which are cloned as Place Names will be as specified for Railway stations and not Place Names.

Abandoned railway stations on operational lines will be labelled 'abandoned' outside Builtup Areas. Abandoned Railway stations on abandoned lines will not be so labelled.

Related Features

Place Name , Railway, Populated Place, Built Up Area

Related Chapters

Section 1 chapter 3.8.1
Section 3 chapters 5.3, 5.11.1 and 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway Tunnel Line

RailwayTunnelLines

RailTransport

Polyline

An artificial underground or underwater passage carrying a railway.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m) 25 25 250
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m) 25 100 250

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Tunnel Line

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the Railway Tunnel.This item should be populated where name is known.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus;
Abandoned
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

205

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

DIMENSION (DIMENSION) [Double;Yes;0;15;0;Pop_Dep] This is the dimension of the linear feature in metres or the polygon feature in square metres as measured in the MGA94 projection of the appropriate zone. This field will be populated internally by Geoscience Australia and should not be altered in any form by producers.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Railway tunnels will be shown as points when they are shorter than 25m.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

All Railway tunnels will be represented in the TOPO100K NTDB either as a Railway Tunnel Line or as a Railway Tunnel Point. All railway tunnel less than 25m will be shown as Railway Tunnel Points. New Railway Tunnel Lines less than 100m will be shown as a Railway Tunnel Point. For existing tunnels between 25m and 100m the tunnel information will be retained in the same geometry as captured in the base material/digital data.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Dismantled railway tunnels will not be included.

Railway tunnels will be shown as points when they are shorter than 250 metres.

General - All Scales

Tunnels which carry both road and railway traffic will be held as a coincident road tunnel and railway tunnel feature in their respective layers.

Railway tunnels will be named where name is known.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Tunnel Line will be coincident with the equivalent section of the Railway. There must be a vertex in the Railway feature at the exact location of the start and end points of the Railway Tunnel Line. The Railway must continue outwards from both endpoints of the Railway Tunnel Line.

Railway Tunnel Lines may be shown off the rail network if they are on a dismantled railway.

A Railway Tunnel Line and a Railway Tunnel Point can not represent the same tunnel.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

The points of disappearance and emergence of Railway tunnel features will be shown by the feature Transition Point.

Map Rules

General - All Scales

Railway tunnels will be named, where name is known.

The equivalent section of railway associated with Railway Tunnel Line must not be symbolised on the map.

Only Railway tunnels which are not dismantled will be shown on the map face.

Related Features

Railway, Road Tunnel Point , Transition point, Railway Station

Related Chapters

Section 3 chapter 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Updated: 1/12/2007

Scales 1:25 000
1:100 000 &
1:250 000

Railway Tunnel Point

RailwayTunnelPoints

RailTransport

Point

An artificial underground or underwater passage carrying a railway.

Minimum Size Criterion:


Minimum Size for: Criterion 1:25 000 1:100 000 1:250 000
Inclusion Area (sq m)      
Inclusion Length (m)      
Data Capture and
Map Representation
Area (sq m)      
Data Capture and
Map Representation
Length (m)      

Data Attributes

FEATURE TYPE (FEATURETYPE) [String;Yes(No);32;0;0;Pop_Req] The code which identifies the type of topographic feature represented.

Railway Tunnel Point

NAME (NAME) [String;Yes;60;0;0;Pop_Dep]

The name of the Railway Tunnel.This item should be populated where name is known.

STATUS (STATUS) [String;Yes(No);18;0;0;Pop_Req] Code for operational status;

Acceptable Domain Entries from dm_RailwayStatus;
Abandoned
Dismantled
Operational
Under Construction

FEATURE RELIABILITY DATE (FEATURERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the spatial object; Date to be adjusted only during spatial change or verification of an existing feature location or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

FEATURE SOURCE (FEATURESOURCE) [String;Yes;50;0;0;Pop_Req] This primary source used to determine the spatial location of a feature.

ATTRIBUTE RELIABILITY DATE (ATTRIBUTERELIABILITY) [Date;Yes;36;0;0;Pop_Req] The reliability date of the attribute object; Date to be adjusted only during attribute change or verification of an existing feature's item values or the capture of a new feature (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Attribute Verification.

ATTRIBUTE SOURCE (ATTRIBUTESOURCE) [String;Yes;50;0;0;Pop_Req] The primary source used to populate the attribute fields of a feature.

PLANIMETRIC ACCURACY (PLANIMETRICACCURACY) [SmallInteger;Yes(No);0;4;0;Pop_Req] The standard deviation of the horizontal positional accuracy. See Section 1 Chapter 3.7 Positional Accuracy for more information;

REVISED DATE (REVISED) [Date;Yes;36;0;0;Pop_Aut] Date of creation or subsequent revision of the feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

DATA SOURCE (SOURCE) [String;Yes(No);50;0;0;Pop_Req] This is the official name of the agency that originally captured the spatial object for the TOPO250K NTDB; The default value when unknown or not specified in project instructions will be GEOSCIENCE AUSTRALIA.

UNIQUE FEATURE IDENTIFIER (UFI) [String;Yes;10;0;0;Pop_Aut] The unique feature identifier used for the release of Geodata TOPO250K Series 2 product;

FEATURE CREATION DATE (CREATIONDATE) [Date;Yes;36;0;0;Pop_Aut] Date of creation of feature in the database. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

FEATURE RETIREMENT DATE (RETIREMENTDATE) [Date;Yes;36;0;0;Pop_Aut] Date of retirement of feature in the database.This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

PERSISTENT IDENTIFIER (PID) [Integer;Yes;0;8;0;Pop_Aut] This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

UPPER SCALE OF DATA UTILISATION (UPPERSCALE) [Integer;Yes;0;8;0;Pop_Dep] Upper Scale for which the entity should be considered suitable either in its current representation or in a different geometry representation;

Acceptable Domain Entries from dm_UpperScale;
0
25000
50000
100000
250000
1000000
2500000
5000000
10000000

UPPER SCALE CERTAINTY (USCERTAINTY) [String;Yes;10;0;0;Pop_Dep] Classification of upper scale certainity;

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

SYMBOL (SYMBOL) [SmallInteger;Yes(No);0;4;0;Pop_Req] (Link to Symbol Dictionary) Symbol number/s applicable;

0

FEATURE WIDTH (FEATUREWIDTH) [Double;Yes;0;8;4;Pop_Dep]

Currently not used by symbology; 0

ORIENTATION (ORIENTATION) [SmallInteger;Yes;0;3;0;Pop_Dep] Orientation in whole degrees from East going anti-clockwise;

Currently not used by symbology; 0

TEXT NOTE (TEXTNOTE) [String;Yes;50;0;0;Pop_Dep] Descriptive note to appear on map. Text Note field should be added when directed in the Geodatabase Rules or if descriptive information is known about a feature that is not covered by any other item in the feature class and expands on the definition of the feature.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;2;0;Pop_Dep] A number allowed for ease of symbology of errors or production notes. This code is for production purposes and therefore for producers internal use only and will not be validated.

Geodatabase Rules

1:25 000

Size and any other selection criteria apply to all feature occurrences.

Railway tunnels will be shown as lines when they are longer than 25m.

1:100 000

Size and any other selection criteria apply to all feature occurrences.

All Railway tunnels will be represented in the TOPO100K NTDB either as a Railway Tunnel Line or as a Railway Tunnel Point. All railway tunnel less than 25m will be shown as Railway Tunnel Points. New Railway Tunnel Lines less than 100m will be shown as a Railway Tunnel Point. For existing tunnels between 25m and 100m the tunnel information will be retained in the same geometry as captured in the base material/digital data.

1:250 000

Size and any other selection criteria apply to new feature occurrences. All feature occurrences existing in the TOPO250K NTDB will be retained unless there is clear evidence they no longer exist.

Dismantled railway tunnels will not be included.

Railway tunnels will be shown as lines when they are greater than 250 metres.

General - All Scales

Tunnels which carry both road and railway traffic will be held as a coincident road tunnel and railway tunnel feature in their respective layers.

Railway tunnels will be named, where name is known.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Tunnel Points will be coincident with a Vertex on the associated Railway.

Railway Tunnel Points may be shown off the rail network if they are on a dismantled railway.

A Railway Tunnel Line and a Railway Tunnel Point can not represent the same tunnel.

Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules

General - All Scales

Railway tunnels will be named, where name is known.

Only Railway tunnels which are not dismantled will be shown on the map face.

Related Features

Railway, Road Tunnel Line, Transition point, Railway Station

Related Chapters

Section 3 chapter 5.3, 5.11.2

Related Products

GEODATA LITE TOPO100K, GEODATA TOPO250K, NTMS 100K, NTMS 250K

Note: See disclaimer in Appendix A Chapter 1.2 Use of Feature Type Dictionary - Structure of an Entry regarding Related features, chapters & products. The information in this entry is uncontrolled when printed.


[back to top]



Unless otherwise noted, all Geoscience Australia material on this website is licensed under the Creative Commons Attribution 3.0 Australia Licence.