Updated: 31/01/2012

Scales 1:100 000

RailTransport Anno 100K

RailTransportAnno100K

RailTransport

Annotation

Type associated with the Rail Transport Feature Dataset for 1:100 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
Arial6ptItalicCenter
Arial6ptItalicLeft
ArialNarrow6ptItalicCenter
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;
RailwayCrossingPoints
RailwayCrossingLines
Railways
RailwayStopPoints

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:100 000 scale or a smaller scale/larger extent (eg 1:250 000, 1:1 000 000)

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

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: 31/01/2012

Scales 1:250 000

RailTransport Anno 250K

RailTransportAnno250K

RailTransport

Annotation

Type associated with the Rail Transport Feature Dataset for 1:250 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptItalicCenter
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;
RailwayCrossingPoints
RailwayCrossingLines
Railways
RailwayStopPoints

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:250 000 scale or a smaller scale/larger extent (eg 1:1 000 000, 1:5 000 000)

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, 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: 31/01/2012

Scales 1:1 000 000

RailTransport Anno WAC

RailTransportAnnoWAC

RailTransport

Annotation

Type associated with the Rail Transport Feature Dataset for 1:1 000 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
ArialNarrow7ptCenter
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;
RailwayCrossingPoints
RailwayCrossingLines
Railways
RailwayStopPoints

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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 Lambert Conic Conformal Projection (with two standard parallels and a central meridian per each chart's requirements) to ensure the spatial position of type on the map face can be correctly represented.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:1 000 000 scale or a smaller scale/larger extent (eg 1:2 500 000, 1:10 000 000)

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, 11

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: 31/01/2012

Scales 1:2 500 000

RailTransport Anno 2_5MIL

RailTransportAnno2_5MIL

RailTransport

Annotation

Type associated with the Rail Transport Feature Dataset for 1:2 500 000 scale

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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;
Arial6ptCenter
Arial6ptLeft
Arial6ptRight

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;
Railways
RailwayStopPoints

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.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

No feature type field exists for this annotation feature class. The feature type has only been included throughout the specification 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 Simple Conic Projection with two standard parallels of 18 degrees south and 36 degrees south to ensure the spatial position of type on the map face can be correctly represented.

Annotation should only occur where the associated feature either has a sufficient dimension size or Upperscale value to be shown at 1:2 500 000 scale or a smaller scale/larger extent (eg 1:5 000 000, 1:10 000 000)

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, 12

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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000
1:5 000 000 &
1:10 000 000

Railway

Railways

RailTransport

Polyline

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

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000   125
1:100 000   500
1:250 000   1250
1:1 000 000   5000
1:2 500 000   5000
1:5 000 000   5000
1:10 000 000   10000

Data Attributes

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

Railway

ROUTE NAME (ROUTENAME) [String;Yes;100;0;0;Pop_Dep] The name of the entire railway line or powerline route. This item 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;
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;
Operational
Abandoned
Under Construction
Dismantled

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

Acceptable Domain Entries from dm_RailwayTracks;
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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);

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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;25;0;0;Pop_Dep] Classification of upper scale certainty;

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 10 000 000 PRODUCTS (SYMBOL10Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained. Dismantled railways, including those on the latest previous edition map or base data/material will be retained/captured.

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.

The following railways will only be eligible for Upperscale Values for 1:250 000 and larger scales (smaller areas):

  • short lengths of non-permanent light railways in position only for the purpose of seasonal harvesting of crops.
  • railways privately run for tourism purposes.

Only railways with status of 'Operational', 'Abandoned' or 'Under Construction' will be eligible for Upperscale Values of 1:100 000 or smaller scales (larger areas). Only railways with status of 'Operational' (or 'Under Construction' which are of national significance) will be eligible for Upperscale Values of 1:2 500 000 or smaller scales (larger areas). The only exceptions will be Dismantled Railways identified by Geoscience Australia required for 1:1 000 000 Airservices products, these railways may be provided with an Upperscale of 1:1 000 000 but will not be utilised by any 1:100 000 or 1:250 000 database products.

In general when assigning Upperscale Values, if the depiction of all tracks in full map symbology for an applicable scale is ambiguous/cluttered, recalculate the Upperscale value for the applicable scale to only depict a general representative pattern.

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 Crossing Points (feature class) must fall exactly over a vertex on the Railway feature.

Railway Stations will be coincident with a vertex on a 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 WatercourseAreas (feature class), Flood Irrigation Storage, Town Water Storage, Rural Water Storage.

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

Railways cannot intersect;
Discontinuities (feature class).

Map Rules

General - All Scales

Railways will be labelled with their 'Route Name'.

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.)

For all products other than WAC Dismantled Railways will not be included on the map face.

Related Features

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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000 &
1:10 000 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 Inclusion: Area (sq m) Criterion Length (m) Criterion
All features   0

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000   0
1:100 000   40
1:250 000   100
1:1 000 000   500
1:10 000 000    

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

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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);

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

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

All new railway bridges should be captured as Railway Crossing Lines (Railway Bridge Line or Railway Overpass), where the structure has been constructed only to prevent an intersection with other road or rail traffic the Railway Overpass feature type should be utilised instead of the Railway Bridge Line feature type.

Existing Railway Bridge Points on the base material/digital data or the latest previous edition map should be recaptured as Railway Crossing Lines (Railway Bridge Line or Railway Overpass) during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Railway Bridge Point in the base material/digital data should be deleted. When the extent on a bridge is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

Existing crossing lines (e.g. bridges, causeway) on the base material/digital data or the latest previous edition map should be retained/captured unless there is evidence that they no longer exist

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').

For all of the following statements, feature width values assigned in the Railway Bridge Line symbol representations should reflect the associated railway gauges see Feature Width Meaning for more details.

For SYMBOL 100K, only Railway Bridge Lines equal to, or greater than, 40m and associated with a railway classified as equal to, or greater than, UPPERSCALE 100000 should be shown with a symbol other than 1 - line no draw. The only exception would be a bridge of historical significance or a bridge no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Bridge Lines equal to or greater than 40m and less than 50m these should be represented as point bridges (eg 4028 - Bridge Line to Point FeatWid 025). For Railway Bridge Lines equal to or greater than 50m these should be represented as linear bridges (eg 4020 - Bridge Line FeatWid 025).

For SYMBOL 250K, only Railway Bridge Lines equal to, or greater than, 40m and associated with a railway classified as equal to, or greater than, UPPERSCALE 250000 should be shown with a symbol other than 1 - line no draw. The only exception would be a bridge of historical significance or a bridge no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Bridge Lines equal to or greater than 40m and less than 100m these should be represented as point bridges (eg 4028 - Bridge Line to Point FeatWid 025). For Railway Bridge Lines equal to or greater than 100m these should be represented as linear bridges (eg 4020 - Bridge Line FeatWid 025).

For SYMBOL WAC1Mil, only Railway Bridge Lines equal to, or greater than, 500m and associated with a railway classified as equal to, or greater than, UPPERSCALE 1000000 should be shown with a symbol other than 1 - line no draw. The only exception would be a bridge of historical significance, a bridge identified by Airservices Australia for inclusion on WACs or a bridge no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Bridge Lines equal to or greater than 500m and less than 1000m these should be represented as point bridges (eg 4025 - Bridge Line to Point FeatWid 08). For Railway Bridge Lines equal to or greater than 1000m these should be represented as linear bridges (eg 4020 - Bridge Line FeatWid 025).

For all of the 3 above paragraphs the following applies:

  • All bridges with a status of dismantled will be given a symbol value of 1 - line no draw.
  • Where cartographic clutter occurs, only significant bridges will be shown. The significance of the bridge depends on the number of bridges in the vicinity, the importance of the railway etc. As guidance, the selection from the latest previous edition map will be taken and a similar approach applied to any new bridges. In this case, bridges not considered significant will be given a symbol value of 1 - line no draw.

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 not represented in the Railway Feature Class.

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'

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

Related Features

Related Chapters

Section 3 Chapters 5.8 and 5.11.2
Appendix U Chapter 2.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: 31/01/2012

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

Railway Bridge Point

RailwayCrossingPoints

RailTransport

Point

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

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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

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.

RailwayBridgePoint

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

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Existing Railway Bridge Points on the base material/digital data or the latest previous edition map should be recaptured as RailwayCrossingLines (Railway Bridge Line or Railway Overpass) during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Railway Bridge Point in the base material/digital data should be deleted. When the extent on a bridge is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

All new railway bridges should be captured as RailwayCrossingLines (Railway Bridge Line or Railway Overpass).

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').

When assigning Upperscale for Railway Bridge Points, for Upperscale of 250000 and smaller scales (larger areas), 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

For feature width values assigned in the Railway Bridge Point symbol representations should reflect the associated railway gauges see Feature Width Meaning for more details.

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 not represented in the Railway Feature Class.

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

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: 31/01/2012

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 Inclusion: Area (sq m) Criterion Length (m) Criterion
All features   50

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000   50
1:100 000   200
1:250 000   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

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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);

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained.

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.

For all of the following statements, feature width values assigned in the Railway Causeway symbol representations should reflect the associated railway gauges see Feature Width Meaning for more details.

For SYMBOL 100K, only Railway Causeways equal to, or greater than, 200m and associated with a railway classified as equal to, or greater than, UPPERSCALE 100000 should be shown with a symbol other than 1 - line no draw. The only exception would be a causeway of historical significance or a causeway no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Causeways equal to or greater than 200m these should be represented as linear causeways (eg 4008 - Railway Causeway FeatWid 025).

For SYMBOL 250K, only Railway Causeways equal to, or greater than, 500m and associated with a railway classified as equal to, or greater, than UPPERSCALE 250000 should be shown with a symbol other than 1 - line no draw. The only exception would be a causeway of historical significance or a causeway no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Causeways equal to or greater than 500m these should be represented as linear causeways (eg 4008 - Railway Causeway FeatWid 025).

For the 2 above paragraphs the following applies:

  • All causeways with a status of dismantled will be given a symbol value of 1 - line no draw.
  • Where cartographic clutter occurs, only significant causeways will be shown. The significance of the causeways depends on the number of causeways in the vicinity, the importance of the railway etc. As guidance, the selection from the latest previous edition map will be taken and a similar approach applied to any new causeways. In this case, causeways not considered significant will be given a symbol value of 1 - line no draw.

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

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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000 &
1:1 000 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 Inclusion: Area (sq m) Criterion Length (m) Criterion
All features   0

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000   0
1:100 000   40
1:250 000   100
1:1 000 000   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 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

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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);

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

All new railway bridges should be captured as Railway Crossing Lines (Railway Bridge Line or Railway Overpass), where the structure has been constructed only to prevent an intersection with other road or rail traffic the Railway Overpass feature type should be utilised instead of the Railway Bridge Line feature type.

Existing Railway Bridge Points on the base material/digital data or the latest previous edition map should be recaptured as Railway Crossing Lines (Railway Bridge Line or Railway Overpass) during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Railway Bridge Point in the base material/digital data should be deleted. When the extent on a bridge is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

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

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

For all of the following statements, feature width values assigned in the Railway Overpass symbol representations should reflect the associated railway gauges see Feature Width Meaning for more details.

For SYMBOL 100K, only Railway Overpasses equal to, or greater than, 40m and associated with a railway classified as equal to, or greater than, UPPERSCALE 100000 should be shown with a symbol other than 1 - line no draw. The only exception would be a bridge of historical significance or a bridge no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Overpasses equal to or greater than 40m and less than 50m these should be represented as point bridges (eg 4028 - Bridge Line to Point FeatWid 025). For Railway Overpasses equal to or greater than 50m these should be represented as linear bridges (eg 4031 - Railway Overpass FeatWid 025).

For SYMBOL 250K, only Railway Overpasses equal to, or greater than, 40m and associated with a railway classified as equal to, or greater than, UPPERSCALE 250000 should be shown with a symbol other than 1 - line no draw. The only exception would be a bridge of historical significance or a bridge no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Overpasses equal to or greater than 40m and less than 100m these should be represented as point bridges (eg 4028 - Bridge Line to Point FeatWid 025). For Railway Overpasses equal to or greater than 100m these should be represented as linear bridges (eg 4020 - Bridge Line FeatWid 025).

For SYMBOL WAC1Mil, only Railway Overpasses equal to, or greater than, 500m and associated with a railway classified as equal to, or greater than, UPPERSCALE 1000000 should be shown with a symbol other than 1 - line no draw. The only exception would be a bridge of historical significance, a bridge identified by Airservices Australia for inclusion on WACs or a bridge no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Overpasses equal to or greater than 500m and less than 1000m these should be represented as point bridges (eg 4025 - Bridge Line to Point FeatWid 08). For Railway Overpasses equal to or greater than 1000m these should be represented as linear bridges (eg 4020 - Bridge Line FeatWid 025).

For all of the 3 above paragraphs the following applies:

  • All bridges with a status of dismantled will be given a symbol value of 1 - line no draw.
  • Where cartographic clutter occurs, only significant bridges will be shown. The significance of the bridge depends on the number of bridges in the vicinity, the importance of the railway etc. As guidance, the selection from the latest previous edition map will be taken and a similar approach applied to any new bridges. In this case, bridges not considered significant will be given a symbol value of 1 - line no draw.

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

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: 31/01/2012

Scales 1:1 000 000

Railway Siding Point

RailwayStopPoints

RailTransport

Point

A short section or sections of track by the side of a railway used for shunting as well as for loading and unloading of freight. A siding will consist of not more than four parallel sections of track.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

Data Attributes

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

Railway Siding Point

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.

RailwaySidingPoint

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_RailSidingStatus;
Abandoned
Decommissioned On Dismantled Railway
Operational
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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
1000000

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained.

When the siding point also meets the definition of a Railway Station then a Railway Station feature type will be used to represent the entity instead of a Railway Siding Point.

Only those Railway Siding Points requested by Airservices Australia for inclusion in the World Aeronautical Charts will be assigned an Upperscale Value of 1 000 000.

For SYMBOLWAC1MIL, all Railway Siding Points with the equivalent Upperscale value or smaller scale (greater area) will have a symbol of 222 except in the following cases when symbol 2 - point no draw should be utilised;

  • when the resultant symbolisation causes clutter with surrounding detail of higher significance to the user , or
  • where the location of the railway siding is already represented by either a Built Up Area or Populated Place of the same name, or
  • where the railway siding is fully contained within a Built Up Area polygon

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Railway Siding Points will be coincident with a vertex on a Railway.

Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules


Related Features

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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000 &
1:5 000 000

Railway Station

RailwayStopPoints

RailTransport

Point

A recognised stopping place for trains where passengers may board or alight or freight is 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 Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 2 500 000 PRODUCTS (SYMBOL2_5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 5 000 000 PRODUCTS (SYMBOL5Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Railway Stations on Dismantled lines will be given an Upperscale value of 25 000.

All railway stations on operational and abandoned lines (including disused/abandoned railway stations) will be assigned a minimum Upperscale value of 250 000. The only exception will be non-operational railway stations where there is clear evidence that the buildings and associated structures no longer exist (i.e. have been dismantled) which will be given an Upperscale value of 25 000.

All operational or under construction Railway Stations, situated upon railway lines assigned with an Upperscale values of 1 000 000 or smaller scale (greater area), will be given the equivalent Upperscale value of its associated railway. Abandoned and Dismantled Railway stations will not be eligible for Upperscales values of 1 000 000 or smaller scales (greater area).

The following applies to symbol assignments for all scales eg SYMBOL100K, SYMBOL250K:

  • Railway stations must be assigned the equivalent Upperscale value or smaller scale (greater area) to have a symbol value other than NULL.
  • Railway stations with the equivalent Upperscale value or smaller scale (greater area) must have one of the legitimate symbol values as per the applicable symbol number listing.
  • Railway stations on underground lines will not be symbolised (e.g symbol = 2 - point no draw).

For SYMBOL100K and SYMBOL250K, all Railway Stations with the equivalent Upperscale value or smaller scale (greater area) will have a symbol of 222 unless denoted to be given a symbol 2 - point no draw from either the paragraphs above or when the resultant symbolisation causes clutter with surrounding detail of higher significance to the user .

For SYMBOLWAC1MIL, all Railway Stations with the equivalent Upperscale value or smaller scale (greater area) will have a symbol of 222 unless
  • denoted to be given a symbol 2 - point no draw from either the paragraphs above, or
  • when the resultant symbolisation causes clutter with surrounding detail of higher significance to the user, or
  • where the location of the railway station is already represented by either a Built Up Area or Populated Place of the same name, or
  • where the railway station is fully contained within a Built Up Area polygon

For SYMBOL2_5MIL and SYMBOL5MIL, all Railway Stations with the equivalent Upperscale value or smaller scale (greater area) will have a symbol of 2 - point no draw.

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

General - All Scales

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 BuildingPoint or BuildingArea feature class entities as appropriate.

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

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: 31/01/2012

Scales 1:25 000
1:100 000
1:250 000
1:1 000 000
1:2 500 000
1:5 000 000 &
1:10 000 000

Railway Tunnel Line

RailwayCrossingLines

RailTransport

Polyline

An artificial underground or underwater passage carrying a railway.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features   0

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000   25
1:100 000   50
1:250 000   50
1:1 000 000   1000
1:2 500 000   2500
1:5 000 000   5000
1:10 000 000   10000

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

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

6

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

RailwayTunnelLine

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

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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);

METADATA COMMENTS (METADATACOMMENT) [String;Yes;1000;0;0;Pop_Dep] Comments expanding on the issues related to data capture, representation or sources.

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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Size and any other selection criteria apply to all feature occurrences. All feature occurrences existing in the base material/digital data or NTDB meeting the minimum size for inclusion will be retained unless there is clear evidence they no longer exist.

All new railway tunnels should be captured as Railway Tunnel Lines.

Existing Railway Tunnel Points on the base material/digital data or the latest previous edition map should be recaptured as Railway Tunnel Lines during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Railway Tunnel Point in the base material/digital data should be deleted. When the extent on a tunnel is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

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.

Dismantled Railway Tunnels will not be eligible for a symbol other than 1 - line no draw for all scales.

For SYMBOL 100K, only Railway Tunnel Lines above 100m and associated with a railway classified as UPPERSCALE 100000 should be shown with a symbol other than 1 - line no draw. The only exception would be a tunnel of historical significance or a tunnel no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Tunnel Lines greater than 100m these can be represented as linear Tunnels (205 - Tunnel Line).

For SYMBOL 250K, only Railway Tunnel Lines above 250m and associated with a railway classified as UPPERSCALE 250000 should be shown with a symbol other than line 1 - line no draw. The only exception would be a tunnel of historical significance or a tunnel no longer associated with a defined railway which still meets the minimum size for map representation. For Railway Tunnel Lines greater than 250m these can be represented as linear Tunnels (205 - Tunnel Line).

For SYMBOL WAC1Mil, only Railway Tunnel Lines above 1000m and associated with a railway classified as UPPERSCALE 1000000 should be represented as linear Tunnels (205 - Tunnel Line), all other tunnels will be shown with a symbol 1 - line no draw.

For all of the 3 above paragraphs the following applies: Where clutter occurs only significant tunnels will be shown. The significance of the tunnel depends on the number of tunnels in the vicinity, the importance of the railway etc.

For SYMBOL2_5MIL, SYMBOL5MIL and SYMBOL10MIL all Railway Tunnel Lines will be given 1 - line no draw.

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

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: 31/01/2012

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

Railway Tunnel Point

RailwayCrossingPoints

RailTransport

Point

An artificial underground or underwater passage carrying a railway.

Minimum Size Criterion:


Minimum Size for Inclusion: Area (sq m) Criterion Length (m) Criterion
All features    

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
All features Regardless of Scale    

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

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

6

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

RailwayTunnelPoint

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

PURPOSE OF STRUCTURE CONSTRUCTION (PURPOSE) [String;Yes;20;0;0;Pop_Req] The type of obstacle the structure was constructed to avoid.

Acceptable Domain Entries from dm_PurposeOfConstruction;
HYDROLOGY
INFRASTRUCTURE
OTHER
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 (see Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digital data for initial 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/digital data for initial 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.

STAKEHOLDERID (STKEHDRID) [String;Yes;250;0;0;Pop_Wk] This is the id used by GA stakeholders or collaborators to identify the link between data maintained, captured or held by GA and their own datasets.

STAKEHOLDER NAME RELATED TO ID ENTRY (STKEHDRNAME) [String;Yes;250;0;0;Pop_Wk] This is the name of stakeholders or collaborators from whom the stakeholderid has been derived and data link is maintained.

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

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

Acceptable Domain Entries from dm_USCertainty;
Automatically Assigned
Definite
Indefinite
Undefined

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.

AUSHYDRO IDENTIFER (AUSHYDRO_ID) [Integer;Yes;0;10;0;Pop_Aut] This is a unique AusHydro Identifier maintained for the national digital surface hydrography dataset.

EDIT CODE (EDITCODE) [SmallInteger;Yes;0;5;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.

SYMBOL FOR 100 000 PRODUCTS (SYMBOL100K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 250 000 PRODUCTS (SYMBOL250K) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

SYMBOL FOR 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_RailTransport.html)

GLOBAL IDENTIFIER (GlobalID) [Global ID;Yes;Pop_Aut] A unique system generated Global Identifier. This field will be entered/edited automatically by GEOSCIENCE AUSTRALIA.

Geodatabase Rules

General - All Scales

Existing Railway Tunnel Points on the base material/digital data or the latest previous edition map should be recaptured as Railway Tunnel Lines during maintenance/revision processes unless there is evidence that they no longer exist. When applicable the associated Railway Tunnel Point in the base material/digital data should be deleted. When the extent on a tunnel is unclear, an Action Request should be sent to Geoscience Australia seeking locational information (eg imagery, plans, etc).

All new railway tunnels should be captured as Railway Tunnel Lines.

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.

Dismantled Railway Tunnels will not be eligible for an Upperscale Value of 100 000 and smaller scales (larger areas).

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

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]



Topic contact: mapfeedback@ga.gov.au Last updated: January 20, 2012