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

Gas Pipeline

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.

GasPipeline

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

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

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Acceptable Domain Entries from dm_PipelineRelationship;
Above Ground
Elevated
Submerged
Underground

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

Acceptable Domain Entries from dm_PipelineStatus;
Disused
Operational
Proposed
Under Construction

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

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

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

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

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

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

281 - Above ground/Elevated Pipelines
282 - Underground Pipelines
0 - Submerged Pipeline or Pipeline running too close to another pipeline to be shown

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

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

General - All Scales

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

Pipelines included in the authorised reference material for pipelines will be added.

Small pipelines serving individual homesteads or farmhouses will not be shown.

If base material/digital data and reference material does not provide information on oil or gas pipeline relationships to ground level, then they should be attributed as Underground.

Two or more pipelines (neither of them water) running closer that 1mm to scale and parallel to each other will be shown in their true position but given a symbol of '0'. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the two pipelines and symbolised with the appropriate symbol. If one pipeline is above ground or elevated and the other is below ground the representation will be given the above ground/elevated symbol of 281. It is this representation which will be shown on the map face and labelled with the names and/or substance/s as appropriate.

Two or more pipelines (where one is a water pipeline) running closer than 1mm to scale and parallel to each other, will be cartographically generalised as follows:
-If more than one pipeline is not water then these pipelines will be generalised into a single pipeline as stated in the above paragraphs, and the resultant 'CartoGeneralisationLine' representation will be offset from the water pipeline.
-If only one pipeline is not water, that pipeline will be given a symbol of '0' and a 'CartoGeneralisationLine' representation should be created for that pipeline which will then be offset from the water pipeline.

In both cases the two final pipeline representations should be labelled on the map face with their name and/or substance/s as appropriate.

Pipelines are to have an accompanying textnote eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'. Where applicable textnotes should be ordered so that detailed descriptive information such as 'underground' or 'disused' follows the more generic product pipeline information e.g. 'gas pipeline underground'

General - All Scales

Where one pipeline crosses another a node will be shown at the intersection point. ie. the arcs will be split.

General - All Scales

Pipelines are to have an accompanying descriptive note eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'.

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

Pipelines will be masked for Roads, Built Up Area and Recreation Areas(Feature Class) . The break will be the same as the width of the road it crosses.

Two or more pipelines running closer that 1mm to scale and parallel to each other will be represented as per the Geodatabase Rules.

Oil Pipeline, Water Pipeline, Pipeline Other, Petroleum Well

Section 3 Chapter 5.3, 5.20

NTMS 100K

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

Oil Pipeline

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.

OilPipeline

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

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

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Acceptable Domain Entries from dm_PipelineRelationship;
Above Ground
Elevated
Submerged
Underground

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

Acceptable Domain Entries from dm_PipelineStatus;
Disused
Operational
Proposed
Under Construction

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

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

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

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

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

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

281 - Above ground/Elevated Pipelines
282 - Underground Pipelines
0 - Submerged Pipeline or Pipeline running too close to another pipeline to be shown

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

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

General - All Scales

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

Pipelines included in the authorised reference material for pipelines will be added.

Small pipelines serving individual homesteads or farmhouses will not be shown.

If base material/digital data and reference material does not provide information on oil or gas pipeline relationships to ground level, then they should be attributed as Underground.

Two or more pipelines (neither of them water) running closer that 1mm to scale and parallel to each other will be shown in their true position but given a symbol of '0'. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the two pipelines and symbolised with the appropriate symbol. If one pipeline is above ground or elevated and the other is below ground the representation will be given the above ground/elevated symbol of 281. It is this representation which will be shown on the map face and labelled with the names and/or substance/s as appropriate.

Two or more pipelines (where one is a water pipeline) running closer than 1mm to scale and parallel to each other, will be cartographically generalised as follows:
-If more than one pipeline is not water then these pipelines will be generalised into a single pipeline as stated in the above paragraphs, and the resultant 'CartoGeneralisationLine' representation will be offset from the water pipeline.
-If only one pipeline is not water, that pipeline will be given a symbol of '0' and a 'CartoGeneralisationLine' representation should be created for that pipeline which will then be offset from the water pipeline.

In both cases the two final pipeline representations should be labelled on the map face with their name and/or substance/s as appropriate.

Pipelines are to have an accompanying textnote eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'. Where applicable textnotes should be ordered so that detailed descriptive information such as 'underground' or 'disused' follows the more generic product pipeline information e.g. 'gas pipeline underground'

General - All Scales

Where one pipeline crosses another a node will be shown at the intersection point. ie. the arcs will be split.

General - All Scales

Pipelines are to have an accompanying descriptive note eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'.

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

Pipelines will be masked for Roads, Built Up Area and Recreation Areas(Feature Class) . The break will be the same as the width of the road it crosses.

Two or more pipelines running closer that 1mm to scale and parallel to each other will be represented as per the Geodatabase Rules.

Gas Pipeline, Water Pipeline, Pipeline Other, Petroleum Well

Section 3 Chapter 5.3, 5.20

NTMS 100K

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

Pipeline

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

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

PRODUCT CODE (PRODUCT) [String;Yes;35;0;0;Pop_Dep] Type of product produced or transported;

This item must be populated. Applicable field entries;
Water
Gas
Oil
Gas and Oil
Other
Unknown

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Applicable field entries:
Elevated
Above Ground
Underground

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

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

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;

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

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

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

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

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

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

281 - Above ground/Elevated Pipelines whose product is not water
282 - Underground Pipelines whose product is not water
947 - Water Pipelines
0 - Pipeline running too close to another pipeline to be shown

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

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

General - All Scales

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

When a new undersized length of water pipeline exists between two canals which meet their selection criterion, then the section of water pipeline should be represented as a canal feature, accepting the attributes of its adjoining canals.

Only Pipelines included in the reference material for pipelines will be added.
Two or more pipelines running closer that 1mm to scale, parallel to each other and carrying the same substance will be shown/captured as a single feature (ie. Physically combined to form one section of Pipeline) .Two or more pipelines running closer than 1mm to scale, parallel to each other and carrying the different substances will be symbolised as a single line. In this case one or more of the pipelines will have a symbol number 0 and the TextNote will describe both substances, for example 'gas and oil pipelines'.In this situation, priority will be given to symbolising Gas/Oil pipelines over Water pipelines, which should then be symbolised to 0 (non-printing). Precedence should also be given to those pipelines having a RELATIONSHIP code of 1(Elevated) or 2 (Above Ground) over those with a RELATIONSHIP code of 3 (Underground).

Small pipelines serving individual homesteads or farmhouses will not be shown.

If base material/digital data and reference material does not provide information on oil or gas pipeline relationships to ground level, then they should be attributed as Underground. However, if base material/digital data and reference material does not provide information on water pipeline relationships to ground level, then this information be sought via an Action Request to Geoscience Australia.

Pipelines are to have an accompanying textnote eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'. Where applicable textnotes should be ordered so that detailed descriptive information such as 'underground' or 'disused' follows the more generic product pipeline information e.g. 'gas pipeline underground'

General - All Scales

Where one pipeline crosses another a node will be shown at the intersection point. ie. the arcs will be split.

General - All Scales

Pipelines are to have an accompanying descriptive note eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'.

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

Pipelines will be masked for Roads, Built Up Area and Recreation Areas(Feature Class) . The break will be the same as the width of the road it crosses.

GEODATA TOPO250K, NTMS 250K

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

Pipeline Other

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

4

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

PipelineOther

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

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

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Acceptable Domain Entries from dm_PipelineRelationship;
Above Ground
Elevated
Submerged
Underground

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

Acceptable Domain Entries from dm_PipelineStatus;
Disused
Operational
Proposed
Under Construction

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

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

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

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

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

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

281 - Above ground/Elevated Pipelines
282 - Underground Pipelines
0 - Submerged Pipeline or Pipeline running too close to another pipeline to be shown

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

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

General - All Scales

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

Pipelines included in the authorised reference material for pipelines will be added.

Small pipelines serving individual homesteads or farmhouses will not be shown.

If base material/digital data and reference material does not provide information on oil or gas pipeline relationships to ground level, then they should be attributed as Underground.

Two or more pipelines (neither of them water) running closer that 1mm to scale and parallel to each other will be shown in their true position but given a symbol of '0'. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the two pipelines and symbolised with the appropriate symbol. If one pipeline is above ground or elevated and the other is below ground the representation will be given the above ground/elevated symbol of 281. It is this representation which will be shown on the map face and labelled with the names and/or substance/s as appropriate.

Two or more pipelines (where one is a water pipeline) running closer than 1mm to scale and parallel to each other, will be cartographically generalised as follows:
-If more than one pipeline is not water then these pipelines will be generalised into a single pipeline as stated in the above paragraphs, and the resultant 'CartoGeneralisationLine' representation will be offset from the water pipeline.
-If only one pipeline is not water, that pipeline will be given a symbol of '0' and a 'CartoGeneralisationLine' representation should be created for that pipeline which will then be offset from the water pipeline.

In both cases the two final pipeline representations should be labelled on the map face with their name and/or substance/s as appropriate.

Pipelines are to have an accompanying textnote eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'. Where applicable textnotes should be ordered so that detailed descriptive information such as 'underground' or 'disused' follows the more generic product pipeline information e.g. 'gas pipeline underground'

General - All Scales

Where one pipeline crosses another a node will be shown at the intersection point. ie. the arcs will be split.

General - All Scales

Pipelines are to have an accompanying descriptive note eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'.

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

Pipelines will be masked for Roads, Built Up Area and Recreation Areas(Feature Class) . The break will be the same as the width of the road it crosses.

Two or more pipelines running closer that 1mm to scale and parallel to each other will be represented as per the Geodatabase Rules.

Oil Pipeline, Water Pipeline, Gas Pipeline, Petroleum Well

Section 3 Chapter 5.3, 5.20

NTMS 100K

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

Powerline

CAPACITY IN KILOVOLTS (CAPACITYKV) [Single;Yes;0;6;2;Pop_Req] The capacity in Kilovolts that can be transmitted or dealt with by the feature.

OPERATOR (OPERATOR) [String;Yes;60;0;0;Pop_Wk] The Company Operating the Facility;

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Acceptable Domain Entries from dm_PowerlineRelationship;
Overhead
Underground
Unknown

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

Acceptable Domain Entries from dm_PowerlineStatus;
Non Operational
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 Section 1 Chapter 3.6); Most Recent Reliability Date of Revision Source Material (or Base Material/digitial data for inital capture) used for Spatial Verification

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

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

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

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

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

METADATA LINK (METADATALINK) [String;Yes;50;0;0;Pop_Dep] A hyperlink which can be activited in an ArcMap Session to a separate metadata document, see geodatabase rules for more information;

REALIGNMENT STATUS (REALIGNMENTSTATUS) [String;Yes;25;0;0;Pop_Req] Status of Realignment of Powerline from its original source;

Acceptable Domain Entries from dm_RealignmentStatus;
Original Source Position
Realigned Position

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

REVISION SOURCE (REVSOURCE) [String;Yes;50;0;0;Pop_Req] The source/reference material used to revise features;

REVISION SOURCE DATE (REVSOURCEDATE) [Date;Yes;36;0;0;Pop_Req] The date of source/reference material used to revise features;

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

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

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

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

542
0 - non printing line see geodatabase rules

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

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

1:25 000

Powerlines will be sourced from the base material/digital data supplied by authoritative Electricity companies.

Powerlines less than 33kv will be given an UpperScale value of 25 000 and a Uscertainity of 'definite'.

Powerlines equal to or greater than 33kv and less than 66kv will be given an UpperScale value of 50 000 and a Uscertainity of 'definite'.

Powerlines equal to or greater than 66kv and less than 110kv will be given an UpperScale value of 100 000 and a Uscertainity of 'definite'.

Powerlines equal to or greater than 110kv will be given an UpperScale value of 250 000 and a Uscertainity of 'indefinite' unless otherwise known.

All powerlines having a 'Realignment Status' of 'Original Source Position' and a voltage of 66kv and above are required to be revised spatially for licence agreement purposes. Therefore these powerlines should be reviewed against imagery during revision processes and the 'Realignment Status' attribute updated accordingly. Dependant on the licence agreement this may also affect the 'Restrictions' field, Geoscience Australia will provide directions to producers if this is the case.

Two or more powerlines running closer that 1mm to scale and parallel to each other will be shown in their true position but given a symbol of '0'. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the two powerlines and symbolised with the appropriate symbol. It is this representation which will be shown on the map face.

Powerlines sourced from the base material/digital data with the words 'position approximate' indicated in the 'data supplier assessment column' will be textnoted with a descriptive note 'position approximate'.

1:100 000

Powerlines will be sourced from the base material/digital data supplied by authoritative Electricity companies.

Powerlines less than 33kv will be given an UpperScale value of 25 000 and a Uscertainity of 'definite'.

Powerlines equal to or greater than 33kv and less than 66kv will be given an UpperScale value of 50 000 and a Uscertainity of 'definite'.

Powerlines equal to or greater than 66kv and less than 110kv will be given an UpperScale value of 100 000 and a Uscertainity of 'definite'.

Powerlines equal to or greater than 110kv will be given an UpperScale value of 250 000 and a Uscertainity of 'indefinite' unless otherwise known.

All powerlines having a 'Realignment Status' of 'Original Source Position' and a voltage of 66kv and above are required to be revised spatially for licence agreement purposes. Therefore these powerlines should be reviewed against imagery during revision processes and the 'Realignment Status' attribute updated accordingly. Dependant on the licence agreement this may also affect the 'Restrictions' field, Geoscience Australia will provide directions to producers if this is the case.

Two or more powerlines running closer that 1mm to scale and parallel to each other will be shown in their true position but given a symbol of '0'. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the two powerlines and symbolised with the appropriate symbol. It is this representation which will be shown on the map face.


Powerlines sourced from the base material/digital data with the words 'position approximate' indicated in the 'data supplier assessment column' will be textnoted with a descriptive note 'position approximate'.

1:250 000

Only powerlines included in the supplied revision source materials for powerlines with a rated capacity of 110kv or greater will be shown.

Several powerlines running closer than 1 mm to scale and parallel to each other will be represented/captured as one line (ie. Physically combined to form one section of Powerline).

Powerlines sourced from the reference material with the words 'position approximate' indicated in the 'data supplier assessment column' will be textnoted with a descriptive note 'position approximate'.

General - All Scales

Cartographic generalisation should take into account the width of the powerline symbol.

Underground powerlines will be symbolised with '0'.

1:25 000

Powerlines that terminate at substations or power stations should maintain their network connectivity with these features by having the appropriate end node of the powerline being coincident with the point feature.

1:100 000

Where one powerline crosses another a node will be shown at their intersection point. ie. the arcs will be split.

Powerlines that terminate at substations or power stations should maintain their network connectivity with these features by having the appropriate end node of the powerline being coincident with the point feature.

1:250 000

Where one powerline crosses another a node will be shown at their intersection point. ie. the arcs will be split.

General - All Scales

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

Powerlines sourced from the reference material with the words 'position approximate' indicated in the 'data supplier assessment column' will be labelled with a descriptive note position approximate where practical.

Powerlines will be masked for Built Up Area and Recreation Areas(Feature Class)


Two or more powerlines running closer that 1mm to scale and parallel to each other will be represented as per the Geodatabase Rules.

Underground powerlines will not be shown on the map face.

Power Station, Substation, Power Generation Facility

Section 3 Chapter 5.3, 5.20

GEODATA TOPO250K, NTMS 100K, NTMS 250K

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

Power Station

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

The name of the Power Station.

CAPACITY IN MEGAWATTS (CAPACITYMW) [Single;Yes;0;6;2;Pop_Req] The capacity in Megawatts that can be dealt with by the feature.

FUEL TYPE (FUELTYPE) [String;Yes;35;0;0;Pop_Req] The type of fuel used to generate power;

Acceptable Domain Entries from dm_PowerStationFuel;
Biomass
Biomass (Animal Waste)
Biomass (Bagasse)
Biomass (Biogas)
Biomass (Digester Gas)
Biomass (Landfill Methane)
Biomass (Municipal Waste)
Biomass (Sewage Methane)
Biomass (Wood Waste/Black Liqour)
Biomass (Wood)
Black Coal
Black Coal/Gas
Brown Coal
Coal
Coal Bed Methane
Distillate
Gas
Gas/Other
Geothermal
Hydro
Ocean (Tidal)
Ocean (Wave)
Other
Solar
Solar/Fossil
Wind

POWER GENERATION TYPE (GENERATIONTYPE) [String;Yes;40;0;0;Pop_Req] Type of Generator used in Power Station

Acceptable Domain Entries from dm_PowerGeneratorType;
CoGeneration
Combined Cycle Gas Turbinet
Gas Turbine
Hydro
Internal Combustion
Other
Steam Turbine
Wind Turbine

OPERATOR (OPERATOR) [String;Yes;60;0;0;Pop_Wk] The Company Operating the Facility;

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

Acceptable Domain Entries from dm_PowerStationStatus;
Non Operational
Operational
Under Construction
Unknown

METADATA LINK (METADATALINK) [String;Yes;50;0;0;Pop_Dep] A hyperlink which can be activited in an ArcMap Session to a separate metadata document, see geodatabase rules for more information;

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

REVISION SOURCE (REVSOURCE) [String;Yes;50;0;0;Pop_Req] The source/reference material used to revise features;

REVISION SOURCE DATE (REVSOURCEDATE) [Date;Yes;36;0;0;Pop_Req] The date of source/reference material used to revise features;

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

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

0

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

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

General - All Scales

Information relating to the attributes and existance of Power Stations should be derived from the authoritative reference material 'Electricity Australia Annual Report'

The Power Station should be positioned central to the main power generation facility.

General - All Scales

Powerlines that terminate at substations or power stations should maintain their network connectivity with these features by having the appropriate end node of the powerline being coincident with the point feature.

General - All Scales

A Power Generation Facility polygon should enclose the power station, if the facility's size meets the minimum data capture criteria.

Buildings with a function of 'Substation' or 'Power Station' will be cloned as 'Sub Station' or 'Power Station' respectively in the Utility Feature Dataset.

Powerlines, Building Point, Building Area, Sub Station

Section 3 Chapter 5.20

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

Sub Station

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

The name of the Sub Station, where known.

CAPACITY IN KILOVOLTS (CAPACITYKV) [Single;Yes;0;6;2;Pop_Req] The capacity in Kilovolts that can be transmitted or dealt with by the feature.

CLASSIFICATION (CLASS) [String;Yes(No);40;0;0;Pop_Req] The entities classification or status;

Classification of Substation Terminals. Acceptable Domain Entries from dm_SubstationClassification;
Other Or Unknown
Sole Use Zone Substation
Switching Station
Terminal Substation
Zone Substation

OPERATOR (OPERATOR) [String;Yes;60;0;0;Pop_Wk] The Company Operating the Facility;

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

Acceptable Domain Entries from dm_SubStationStatus;
Non Operational
Operational
Under Construction
Unknown

METADATA LINK (METADATALINK) [String;Yes;50;0;0;Pop_Dep] A hyperlink which can be activited in an ArcMap Session to a separate metadata document, see geodatabase rules for more information;

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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.

REVISION SOURCE (REVSOURCE) [String;Yes;50;0;0;Pop_Req] The source/reference material used to revise features;

REVISION SOURCE DATE (REVSOURCEDATE) [Date;Yes;36;0;0;Pop_Req] The date of source/reference material used to revise features;

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

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

0

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

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

General - All Scales

Sub Station will be sourced from the base material/digital data supplied by authoritative Electricity companies.

General - All Scales

Powerlines that terminate at substations or power stations should maintain their network connectivity with these features by having the appropriate end node of the powerline being coincident with the point feature.

General - All Scales

Buildings with a function of 'Substation' or 'Power Station' will be cloned as 'Sub Station' or 'Power Station' respectively in the Utility Feature Dataset.

Section 3 Chapter 5.20

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 UtilityAnno;
Arial6ptItalicLeft
Arial6ptItalicRight
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow8ptLeft
ArialNarrow8ptRight

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_UtilityFCs;
Pipelines
Powerlines
PowerStations
SubStations

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

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

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

General - All Scales

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

Only Annotation associated with, or derived from, entities in feature classes grouped within the Utility feature dataset should exist within the UtilityAnno 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.

Section 2 Chapter 5, 9, 10

NTMS 100K

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

Water Pipeline

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.

WaterPipeline

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

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

RELATIONSHIP (RELATIONSHIP) [String;Yes;12;0;0;Pop_Req] Relationship to sea level for marine features or to ground level for land based features;

Acceptable Domain Entries from dm_PipelineRelationship;
Above Ground
Elevated
Submerged
Underground

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

Acceptable Domain Entries from dm_PipelineStatus;
Disused
Operational
Proposed
Under Construction

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

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

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

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

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

RESTRICTIONS ON USE (RESTRICTIONS) [String;Yes;50;0;0;Pop_Req] Specific restrictions for data usagage as defined by licence agreements, land owners, agreements with other agencies supplying the data.

Acceptable Domain Entries from dm_Restrictions;
Australian Federal Govt Only
Australian Federal Govt plus NMI Map Products
Geoscience Australia Only
Geoscience Australia plus NMI Map Products
NMI Only
NMI Only plus NMI Map Products
NMI Use for 3rd Party
NMI Use for 3rd Party plus NMI Map Products
Public Access
Whole of Govt Only
Whole of Govt plus NMI Map Products

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

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

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

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

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

Acceptable Domain Entries from dm_USCertainty;
Definite
Indefinite
Undefined

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

947 - Water Pipelines
0 - Submerged Pipeline or Pipeline running too close to another pipeline to be shown

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

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

General - All Scales

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

Pipelines included in the authorised reference material for pipelines will be added.

Small pipelines serving individual homesteads or farmhouses will not be shown.

If base material/digital data and reference material does not provide information on water pipeline relationships to ground level, then this information be sought via an Action Request to Geoscience Australia.

When a new undersized length of water pipeline exists between two canals which meet their selection criterion, then the section of water pipeline should be represented as a canal feature, accepting the attributes of its adjoining canals.

Two or more water pipelines running closer that 1mm to scale and parallel to each other will be shown in their true position but given a symbol of '0'. A new representation of this feature will be created in the 'CartoGeneralisationLine' feature class down the centre of the pipelines and symbolised with the 947 symbol. It is this representation which will be shown on the map face and labelled with the names and/or substance as appropriate.

Two or more pipelines (where at least one is not a water pipeline) running closer than 1mm to scale and parallel to each other, will be cartographically generalised as follows:
-If more than one pipeline is not water then these pipelines will be generalised into a single pipeline as stated in the the geodatabase rules appropriate for that feature type, and the resultant 'CartoGeneralisationLine' representation will be offset from the water pipeline.
-If only one pipeline is not water, that pipeline will be given a symbol of '0' and a 'CartoGeneralisationLine' representation should be created for that pipeline which will then be offset from the water pipeline.

In both cases the two final pipeline representations should be labelled on the map face with their names and/or substance/s as appropriate.

Pipelines are to have an accompanying textnote eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'. Where applicable textnotes should be ordered so that detailed descriptive information such as 'underground' or 'disused' follows the more generic product pipeline information e.g. 'gas pipeline underground'

General - All Scales

Where one pipeline crosses another a node will be shown at the intersection point. ie. the arcs will be split.

General - All Scales

Pipelines are to have an accompanying descriptive note eg 'pipeline', 'gas pipeline', unless the word 'pipeline' is included in the name. Underground pipelines will be labelled with a descriptive note, 'underground'.

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

Pipelines will be masked for Roads, Built Up Area and Recreation Areas(Feature Class) . The break will be the same as the width of the road it crosses.

Two or more pipelines running closer that 1mm to scale and parallel to each other will be represented as per the Geodatabase Rules.

Gas Pipeline, Oil Pipeline, Pipeline Other

Section 3 Chapter 5.3, 5.20

NTMS 100K