Updated: 31/01/2012

Scales 1:25 000 &
1:100 000

Boat Ramp Line

MarineInfrastructureLines

Marine

Polyline

A sloping construction to facilitate launching or retrieving vessels from water.

Minimum Size Criterion:


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

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

Data Attributes

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

Boat Ramp 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.

BoatRampLine

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

The Name of the Boat Ramp. This item should be populated where name is known.

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

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


Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules

General - All Scales

All Boat Ramp Lines will be labelled with a descriptive note or named eg 'boat ramp'.

Related Features

Related Chapters

Section 3 Chapter 5.3
Appendix U Chapter 2.6

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

Breakwater

MarineInfrastructureLines

Marine

Polyline

A solid structure to break the force of the waves, sometimes detached from the coast, protecting a harbour or anchorage.

Minimum Size Criterion:


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

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

Data Attributes

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

Breakwater

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.

Breakwater

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

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

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.

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

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset


Map Rules

General - All Scales

Features will be named if named is known.

All breakwaters are to have an accompanying descriptive note eg 'breakwater'

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

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

Dry Dock Point

MarineInfrastructurePoints

Marine

Point

A structure or basin providing support for a vessel and from which water can be removed so that the bottom of the vessel is exposed.

Minimum Size Criterion:


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

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 1406  
1:100 000 22500  

Data Attributes

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

Dry Dock 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.

DryDockPoint

COLOUR (COLOUR) [String;Yes;12;0;0;Pop_Wk] The colour of the Light projected from the feature.

This field is not applicable to this subtype and therefore is currently not to be populated;

DURATION (DURATION) [String;Yes;12;0;0;Pop_Wk] Duration of the cycle in seconds.

This field is not applicable to this subtype and therefore is currently not to be populated;

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

This field is not applicable to this subtype and therefore is currently not to be populated;

FLASHES (FLASHES) [String;Yes;12;0;0;Pop_Wk] Number of Light Flashes;

This field is not applicable to this subtype and therefore is currently not to be populated;

LIGHT TYPE (LIGHTTYPE) [String;Yes;15;0;0;Pop_Wk] The nature of the light action.

This field is not applicable to this subtype and therefore is currently not to be populated;

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

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

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.

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


Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Dry Dock Points must appear over the Sea or polygons in the Waterbodies Dataset ie. they cannot appear over land.

Map Rules

General - All Scales

All dry docks are to have an accompanying descriptive note 'dry dock' unless the word 'dry dock' is included in the name.

Dry Docks will mask all other detail except route markers, kilometric distance indicators and annotation.

Related Features


Related Chapters


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

Foreshore Flat

ForeshoreFlats

Marine

Polygon

That part of the seabed or estuarine areas, between mean high water and the line of lowest astronomical tide.

Minimum Size Criterion:


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

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 3906  
1:100 000 62500  
1:250 000 390625  
1:1 000 000 5000000  

Data Attributes

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

Foreshore Flat

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

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

New Foreshore Flat polygons that are under the minimum size for data capture but form clusters with other new or existing Foreshore Flat polygons (which either meet, or are below, the minimum size for data capture) will be considered applicable for that capture scale if the resultant cluster/s are equal to, or exceed, the minimum size for data capture. The only exception is when the resultant cluster misrepresents the true extent/significance of the feature. A cluster will only be considered legitimate in this context where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.2)) metres and each component part is above the minimum size for inclusion. In this situation, the Foreshore Flat polygons should be captured as their individual components not as the cluster upon which its applicability is based.

The UPPERSCALE value will be applied based on a Foreshore Flat polygon meeting the applicable minimum size for map representation. Where Foreshore Flat polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Foreshore Flats cannot overlap;
each other or any other polygon in the Marine Dataset.

A Foreshore Flat edge must be coincident with the edge of other polygon features in the Marine feature dataset where it abuts (Foreshore Flat transitions into Reef or Shoal) them in reality.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Foreshore Flats must be contained within;
Sea, WatercourseAreas (feature class) or Lake.

A Foreshore Flat edge must be coincident with the edge of a sea, estuarine lake or estuarine watercourse area polygon where it abuts (transitions from foreshore flat to land) them in reality.

Map Rules


Related Features

Related Chapters

Section3 Chapter 6.9, 5.11.2, 5.19, 5.18

Related Products

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

Jetty

MarineInfrastructureLines

Marine

Polyline

A structure projecting into a body of water for use as a promenade or as a platform alongside which vessels may be secured for loading and unloading passengers and cargo.

Minimum Size Criterion:


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

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

Data Attributes

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

Jetty

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.

Jetty

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

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

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.

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

Jetties are to have an accompanying textnote eg 'jetty', 'marina', 'pier' unless the words 'jetty', 'marina' 'pier' etc are included in the name.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Jetties cannot overlap;
BuildingAreas (feature class).

Map Rules

General - All Scales

Jetties are to have an accompanying descriptive note eg 'jetty', 'marina', 'pier' unless the words 'jetty', 'marina,' 'pier' etc are included in the name.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

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

Lighthouse

MarineInfrastructurePoints

Marine

Point

A building or structure housing a light used as a navigation aid to shipping.

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.

Lighthouse

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

8

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

Lighthouse

COLOUR (COLOUR) [String;Yes;12;0;0;Pop_Wk] The colour of the Light projected from the feature.

DURATION (DURATION) [String;Yes;12;0;0;Pop_Wk] Duration of the cycle in seconds.

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

FLASHES (FLASHES) [String;Yes;12;0;0;Pop_Wk] Number of Light Flashes;

LIGHT TYPE (LIGHTTYPE) [String;Yes;15;0;0;Pop_Wk] The nature of the light action.

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

The Lighthouse's name (see Geodatabase Rules for population requirements.)

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.

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

Lighthouse will be named in the data, but will only be named on the map (in accordance with approved reference sources) where the lighthouse does not have the same root name as the Island or Cape feature. For example, the name Bedout Lighthouse would not be shown when it is situated on Bedout Island.

The lighthouse need not be operational to be included.

Navigation beacons will not be classified as lighthouses.

Reference material for Lighthouses will be supplied. This reference material will include the Australian Pilot and the Admiralty List of Lights and Fog Signals. In general, if a lighthouse is shown on the associated previous edition 250K map it should be retained or captured as a lighthouse. New lighthouses should only be added if they have a substantial structure and have two or more of the following characteristics to distinguish them from marine lights:

  • The structure is over 7 metres tall.
  • The light is visible for at least 12 kilometres.
  • Is of solid construction eg Concrete or Stone.
  • The structure is painted a distinctive colour, especially white.
Where a Lighthouse and an Offshore rock are shown on the base material/digital data or reference material to be coincident, they should be coincident. If one of the two features had been previously displaced by a maximum of 10 metres in any direction they should be adjusted back to their true coincident position.

Where a lighthouse and an offshore rock are in close proximity, the lighthouse symbol will be given precedence (the offshore rock will have a symbol number of 2 PointNoDraw) but the name of the offshore rock will take precedence over the lighthouse name.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Lighthouses cannot overlap the sea except when coincident with an offshore rock. Any within 10m of an offshore rock should be made coincident when applicable.

Map Rules

General - All Scales

Where a lighthouse and an offshore rock are in close proximity the lighthouse symbol will be given precedence but the name of the offshore rock will take precedence over the lighthouse name.

Related Features

Related Chapters


Related Products

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:1 000 000

Lightship

MarineInfrastructurePoints

Marine

Point

A moored ship (generally permanently) in dangerous waters that has a powerful light or warning signals to alert other vessels. They are used in waters too deep or otherwise unsuitable for lighthouse construction.

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.

Lightship

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

9

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

Lightship

COLOUR (COLOUR) [String;Yes;12;0;0;Pop_Wk] The colour of the Light projected from the feature.

DURATION (DURATION) [String;Yes;12;0;0;Pop_Wk] Duration of the cycle in seconds.

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

FLASHES (FLASHES) [String;Yes;12;0;0;Pop_Wk] Number of Light Flashes;

LIGHT TYPE (LIGHTTYPE) [String;Yes;15;0;0;Pop_Wk] The nature of the light action.

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

The Lightship's name (see Geodatabase Rules for population requirements.)

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.

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

The lightship need not be operational to be included.

Reference material for Lightships will be supplied. This reference material will include the Australian Pilot and the Admiralty List of Lights and Fog Signals and the previous edition WAC.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Light Ships must exist within either;
Sea, Lake (perennial) or WatercourseAreas feature class (Perennial)

Map Rules

General - All Scales

To be shown with a description if visibility range is equal to, or greater than, 15 nautical miles.

Related Features

Related Chapters


Related Products

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:100 000

Marine Anno 100K

MarineAnno100K

Marine

Annotation

Type associated with the Marine 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 MarineAnno;
ArialNarrow10ptCenter
ArialNarrow12ptCenter
ArialNarrow14ptCenter
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow6ptCenter
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow7ptCenter
ArialNarrow7ptLeft
ArialNarrow7ptRight
ArialNarrow8ptCenter

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_MarineFCs;
ForeshoreFlats
MarineHazardAreas
MarineHazardPoints
MarineInfrastructureLines
MarineInfrastructurePoints

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 Marine feature dataset should exist within the MarineAnno 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

Marine Anno 250K

MarineAnno250K

Marine

Annotation

Type associated with the Marine 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 MarineAnno;
ArialNarrow10ptCenter
ArialNarrow12ptCenter
ArialNarrow14ptCenter
ArialNarrow6ptItalicCenter
ArialNarrow6ptItalicLeft
ArialNarrow6ptItalicRight
ArialNarrow5ptCenter
ArialNarrow5ptLeft
ArialNarrow6ptLeft
ArialNarrow6ptRight
ArialNarrow8ptCenter

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_MarineFCs;
ForeshoreFlats
MarineHazardAreas
MarineHazardPoints
MarineInfrastructureLines
MarineInfrastructurePoints

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 Marine feature dataset should exist within the MarineAnno 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

Marine Anno WAC

MarineAnnoWAC

Marine

Annotation

Type associated with the Marine 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 MarineAnno;
Arial6ptCenter
Arial6ptLeft
Arial6ptRight
Arial8ptCenter
Arial8ptLeft
Arial8ptRight

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_MarineFCs;
ForeshoreFlats
MarineHazardAreas
MarineHazardPoints
MarineInfrastructureLines
MarineInfrastructurePoints
ReefLines

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 Marine feature dataset should exist within the MarineAnno 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

Marine Anno 2_5MIL

MarineAnno2_5MIL

Marine

Annotation

Type associated with the Marine 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 MarineAnno;
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight
Arial10ptItalicCenter
Arial10ptItalicLeft
Arial10ptItalicRight

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_MarineFCs;
MarineHazardAreas

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 Marine feature dataset should exist within the MarineAnno 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:5 000 000

Marine Anno 5MIL

MarineAnno5MIL

Marine

Annotation

Type associated with the Marine Feature Dataset for 1:5 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 MarineAnno;
Arial6pt5ItalicCenter
Arial6pt5ItalicLeft
Arial6pt5ItalicRight
Arial10ptItalicCenter
Arial10ptItalicLeft
Arial10ptItalicRight

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_MarineFCs;
MarineHazardAreas

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 Marine feature dataset should exist within the MarineAnno 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:5 000 000 scale or a smaller scale/larger extent (eg 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, 13

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:10 000 000

Marine Anno 10MIL

MarineAnno10MIL

Marine

Annotation

Type associated with the Marine Feature Dataset for 1:10 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 MarineAnno;
Arial6ptItalicCenter
Arial6ptItalicLeft
Arial6ptItalicRight

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_MarineFCs;
MarineHazardAreas

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 Marine feature dataset should exist within the MarineAnno 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:10 000 000 scale.

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

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

Marine Light

MarineInfrastructurePoints

Marine

Point

A signal light for sea navigation by night or in conditions of poor visibility.

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.

Marine Light

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

10

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

MarineLight

COLOUR (COLOUR) [String;Yes;12;0;0;Pop_Wk] The colour of the Light projected from the feature.

DURATION (DURATION) [String;Yes;12;0;0;Pop_Wk] Duration of the cycle in seconds.

ELEVATION (ELEVATION) [Double;Yes(No);0;7;2;Pop_Req] Elevation in metres from the Australian Height Datum.

FLASHES (FLASHES) [String;Yes;12;0;0;Pop_Wk] Number of Light Flashes;

LIGHT TYPE (LIGHTTYPE) [String;Yes;15;0;0;Pop_Wk] The nature of the light action.

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

This field is not applicable to this subtype and therefore is currently not to be populated;

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.

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

When a light meets the definition of a lighthouse it should be captured as a Lighthouse feature type and not as a Marine Light.

Reference material for Lighthouses and marine lights will be supplied. This reference material will include the Australian Pilot and the Admiralty List of Lights and Fog Signals. In general, if a lighthouse is shown on the associated previous edition 250K map it should be retained or captured as a lighthouse. New lighthouses should only be added if they have a substantial structure and have two or more of the following characteristics to distinguish them from marine lights:

  • The structure is over 7 metres tall.
  • The light is visible for at least 12 kilometres.
  • Is of solid construction eg Concrete or Stone.
  • The structure is painted a distinctive colour, especially white.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Marine Lights must overlap;
Sea, Lake (Perennial) or WatercourseAreas feature class (Perennial)

Map Rules

General - All Scales

Marine Lights are to be shown with a description if visibility range is equal to, or greater than, 15 nautical miles or greater.

Related Features

Related Chapters


Related Products

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

Offshore Rock

MarineHazardPoints

Marine

Point

A rock located offshore that represents a hazard to shipping.

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.

Offshore Rock

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.

OffshoreRock

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

The name of the Offshore Rock. 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_MarineRelationship at 25K and 100K as well as acceptable entries for the 250K field;
Bare
Tidal
Submerged

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.

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

When applicable for inclusion/data capture an Offshore Rock will be depicted as either an Offshore Rock, Reef, Shoal or Island dependant on size criteria and its relationship to sea level.

Existing Offshore Rock features below the minimum data capture size for a Reef/Shoal or Island as appropriate will be retained in the same geometry as captured in the base material/digital data (eg Offshore Rock, Reef, Shoal or Island). The only exception is all features below 625 sq m which will be shown as Offshore Rock

New features with a RELATIONSHIP Code of Bare below the minimum data capture size for an Island will be captured as an Offshore Rock. New features with a RELATIONSHIP Code of Bare which are equal to or above the minimum data capture size for an Island at the specified scale will be captured as an Island.

New features with a RELATIONSHIP Code of Tidal or Submerged below the minimum data capture size for a Reef/Shoal will be captured as an Offshore Rock. New features with a RELATIONSHIP Code of Tidal or Submerged which are equal to or above the minimum data capture size for a Reef/Shoal at the specified scale will be captured as either a reef or shoal as appropriate. The reef feature will be considered the default.

Where a Lighthouse and an Offshore rock are shown on the base material/digital data or reference material to be coincident, they should be coincident. If one of the two features had been previously displaced by a maximum of 10 metres in any direction they should be adjusted back to their true coincident position.

Where a lighthouse and an offshore rock are in close proximity, the lighthouse symbol will be given precedence (the offshore rock will have a symbol number of 2 PointNoDraw) but the name of the offshore rock will take precedence over the lighthouse name.

Offshore rocks may be symbolised as non printing (Symbol Number 2 PointNoDraw) where they unavoidably clash with text.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Offshore rocks must appear in the Sea or WatercourseAreas (feature class) and Lakes under tidal influence.

Map Rules

General - All Scales

Offshore rocks may be symbolised as 2 PointNoDraw where they unavoidably clash with text.

Where a lighthouse and an offshore rock are in close proximity, the lighthouse symbol will be given precedence (the offshore rock will have a symbol number of 2 PointNoDraw) but the name of the offshore rock will take precedence over the lighthouse name.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

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

Reef

MarineHazardAreas

Marine

Polygon

An area of rock or coral that is exposed between mean high water and lowest tide, or just below approximate lowest tide, which is visually prominent or a hazard to shipping.

Minimum Size Criterion:


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

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 3906  
1:100 000 62500  
1:250 000 390625  
1:1 000 000 390625  
1:2 500 000 4000000  
1:5 000 000 5000000  
1:10 000 000 6000000  

Data Attributes

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

Reef

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.

Reef

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

The name of the Reef. 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_MarineRelationship;
Bare
Tidal
Submerged

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

When applicable for inclusion/data capture a Reef will be depicted as either an Offshore Rock or Reef dependant on size criteria.

Existing Reef features below the minimum data capture size for a Reef will be retained in the same geometry as captured in the base material/digital data (eg Offshore Rock or Reef). The only exception is all features below 3906 sq m which will be shown as Offshore Rocks.

New Reef features below the minimum data capture size for an Reef will be captured as an Offshore Rock. New Reef features which are equal to or above the minimum data capture size for a Reef at the specified scale will be captured as a Reef. At Capture Scales of 2 500 000 and smaller scales, new Reef polygons that are under the minimum size for data capture but form clusters with other new or existing Reef polygons (which either meet, or are below, the minimum size for data capture) will be considered applicable for that capture scale if the resultant cluster/s are equal to, or exceed, the minimum size for data capture. The only exception is when the resultant cluster misrepresents the true extent/significance of the feature. A cluster will only be considered legitimate in this context where the separation between polygons is equal to or less than ((Capture Scale/1000) * 0.15)) metres and each component part is above the minimum size for inclusion. In this situation, the Reef polygons should be captured as their individual components not as the cluster upon which its applicability is based.

An offshore rock and reef can not exist in the geodatabase representing the same topographic entity. An offshore rock may exist within a reef structure if it is representing a different topographic entity.

Descriptive notes may be included in the textnote field.

The UPPERSCALE value will be applied based on a Reef polygon meeting the applicable minimum size for map representation. For Upperscale Values of 2 500 000 and smaller scales, where Reef polygons are under the minimum size for map representation but form clusters as discussed above, the 'UPPERSCALE' value will be based on the total area of the sum of the component parts provided the resultant cluster does not misrepresent the true extent/significance of the feature.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Reef cannot overlap;
each other or any other polygon in the Marine Dataset.

A Reef edge must be coincident with the edge of other polygon features in the Marine feature dataset where it abuts (Reef transitions into Shoal or Foreshore Flat) them in reality.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Reefs cannot overlap;
Mainland or Island unless contained within a Lake (Perennial) or WatercourseAreas feature class (Perennial).

A MarineHazardAreas edge (feature class polygon) must be coincident with the edge of a sea, estuarine lake or estuarine watercourse area polygon where it abuts (transitions from MarineHazardArea to land) them in reality.

Map Rules

General - All Scales

Reefs should be named, where name is known.

Descriptive notes may be included.

For Upperscale Values of 2 500 000 and smaller scales, reef emphasis symbols may be required to represent small narrow reef chains which are of national significance but too thin to be shown on the map as their true shape.

Related Features

Related Chapters

Section 3 Chapter 5.3, 5.11.2, 5.18, 5.19

Related Products

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:1 000 000

Reef Line

ReefLines

Marine

Polyline

A line depicting the boundary of a reef system.

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.

Reef Line

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.

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 1 000 000 PRODUCTS (SYMBOLWAC1Mil) [Integer; Yes; 4; 0; 0; Pop_Dep] For Applicable Symbol numbers including core values see attached link; (See RepresentationFieldsTables_Marine.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

All feature occurrences existing in the base material/digital data or on the previous edition World Aeronautical Chart will be retained/captured unless there is clear evidence they no longer exist.

All features will be provided a SYMBOLWAC of 4203 Reef Line WAC. The only exceptions to this rule is where symbolisation causes clutter and when this occurs a selection of lines may assigned a SYMBOLWAC of 1 LineNoDraw until an acceptable cartographic result is obtained.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Reef Lines must overlap either;
Sea 10MIL, WatercourseAreas feature class (Perennial), Lake (Perennial)

Map Rules


Related Features

Related Chapters

Section 2 Chapter 2.2.3
Section 3 Chapters 5.11.1, 5.11.2, 5.17, 6.2, 6.9

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

Sea Wall

MarineInfrastructureLines

Marine

Polyline

A solid structure usually of concrete masonry or earth, built to prevent erosion or encroachment by the sea.

Minimum Size Criterion:


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

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

Data Attributes

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

Sea Wall

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.

SeaWall

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

This field is not applicable to this subtype and therefore is currently not to be populated;

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.

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

Only walls that form part of the coastline and are usually wet under daily tidal influence will be shown. Retaining walls adjacent to beaches or in riverbanks do not fall in this feature type.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Wharves coincident with the coastline will be cloned as sea walls. This will create two coincident arcs in the one feature class, which will be considered an exception to the standard topology structure rules.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Sea walls which form part of the coastline will be coincident with the equivalent section of the Shoreline. There must be a vertex in the Shoreline feature at the exact location of the start and end points of the Sea walls. The Shoreline must continue outwards from both endpoints of the Sea walls.

Wharves coincident with the coastline will be cloned as sea walls. This will create two coincident arcs in the one feature class, which will be considered an exception to the standard topology structure rules.

Map Rules

General - All Scales

Sea walls will be labelled 'sea wall'.

Related Features

Related Chapters

Section 3 Chapters 5.3, 5.11.1, 5.11.2

Related Products

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

Shoal

MarineHazardAreas

Marine

Polygon

A detached area of any material the depth over which constitutes a danger to surface navigation of marine craft. The term shoal is not generally used for dangers which are composed entirely of rock or coral.

Minimum Size Criterion:


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

Minimum Size for Data Captured and
Map Representation (per scale):
Area (sq m) Criterion Length (m) Criterion
1:25 000 3906  
1:100 000 62500  
1:250 000 390625  
1:1 000 000 390625  

Data Attributes

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

Shoal

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.

Shoal

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

The name of the Shoal. 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_MarineRelationship;
Bare
Tidal
Submerged

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.

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

When applicable for inclusion/data capture a Shoal will be depicted as either an Offshore Rock or Shoal dependant on size criteria.

Existing Shoal features below the minimum data capture size for a Shoal will be retained in the same geometry as captured in the base material/digital data (eg Offshore Rock or Shoal). The only exception is all features below 3906 sq m which will be shown as Offshore Rocks.

New Shoal features below the minimum data capture size for a Shoal will be captured as an Offshore Rock. New Shoal features which are equal to or above the minimum data capture size for a Shoal at the specified scale will be captured as a Shoal.

An offshore rock and Shoal can not exist in the geodatabase representing the same topographic entity. An offshore rock may exist within a Shoal structure if it is representing a different topographic entity.

Descriptive notes may be included in the textnote field.

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Shoal cannot overlap;
each other or any other polygon in the Marine Dataset.

A Shoal edge must be coincident with the edge of other polygon features in the Marine feature dataset where it abuts (Shoal transitions into Reef or Foreshore Flat) them in reality.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Reefs cannot overlap;
Mainland or Island unless contained within a Lake (Perennial) or WatercourseAreas feature class (Perennial).

A MarineHazardAreas edge (feature class polygon) must be coincident with the edge of a sea, estuarine lake or estuarine watercourse area polygon where it abuts (transitions from MarineHazardArea to land) them in reality.

Map Rules

General - All Scales

Shoals should be named, where name is known.

Descriptive notes may be included.

Related Features

Related Chapters

Section 3 Chapter 5.3, 5.11.2, 5.18, 5.19

Related Products

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

Wharf Line

MarineInfrastructureLines

Marine

Polyline

A structure built along the shoreline to provide for the berthing (or mooring) of vessels. In large commercial ports it may be associated with warehouses and storage facilities for shipping containers.

Minimum Size Criterion:


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

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

Data Attributes

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

Wharf Line

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

5

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

WharfLine

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

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

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.

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

Inter-Feature Relationship Rules - Internal to Associated Dataset

General - All Scales

Wharves coincident with the coastline will be cloned as sea walls. This will create two coincident arcs in the one feature class, which will be considered an exception to the standard topology structure rules.

Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Wharves coincident with the coastline will be cloned as sea walls. This will create two coincident arcs in the one feature class, which will be considered an exception to the standard topology structure rules.

Map Rules

General - All Scales

Wharfs will be labelled with their name, where name is known.

Related Features

Related Chapters

Section 3 Chapters 5.3, 5.11.1, 5.11.2

Related Products

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

Wreck

MarineHazardPoints

Marine

Point

A disabled vessel, either submerged or visible, which is attached to, or foul of, the bottom or cast up on the shore.

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.

Wreck

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.

Wreck

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

The name of the Wreck (see Geodatabase Rules for population requirements).

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_MarineRelationship at 25K and 100K as well as acceptable entries for the 250K field;
Bare
Tidal
Submerged

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.

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_Marine.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_Marine.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_Marine.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 wrecks visible above water level and all those submerged wrecks which constitute a danger to shipping will be included.

Wrecks will be named and the date the vessel went aground may be included when it is of historical or general interest. The date will be held in the textnote field.

All wrecks will be given a minimum Upperscale Value of 250,000. Wrecks with a relationship of 'Bare' or 'Tidal' will be given an Upperscale Value of 1,000,000. The only exceptions will be if this results in clutter on the hardcopy/digital map products, in which case, priority should be given to the entities with higher historical/landmark significance.

Inter-Feature Relationship Rules - Internal to Associated Dataset


Inter-Feature Relationship Rules - External to Associated Dataset

General - All Scales

Wrecks cannot overlap;
BuildingAreas (feature class) or BuildingPoints (feature class)

Map Rules

General - All Scales

Wrecks will be named and the date the vessel went aground may be included when it is of historical or general interest.

Related Features

Related Chapters

Section 3 Chapter 5.3

Related Products

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