HYDROGRAPHIC - Spatial Data Model - Specification

Contents

1. Overview
2. Class Diagram
3. Class Details
4. Relationships
5. Code Lists
6. Miscellaneous Information

1. Overview

The HYDROGRAPHIC data model has the following characteristics:

Name:	HYDROGRAPHIC
Description:	The List, Hydrographic theme data model. File: L:\LIST\datamodels\current\hydro.dmd
Database Type:	ODBC
Dataset:	HYDOGRAPHIC
Unit of Measure:	meters

2. Class Diagram

3. Class Details

The following classes are part of the HYDROGRAPHIC data model. The characteristics and attributes of each of the classes is described.

3.1. Class: ArtWc1D

This class is defined as follows:

Name:	ArtWc1D
Screen Text:	Artificial Watercourse 1D
Plural:	Artificial Watercourse 1Ds
Description:	An Artificial Watercourse represented as a chain.
Use 'an':	Yes
Spatial:	Yes
Feature Types:	s

It contains the following attributes:

3.1.1. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.2. Class: ArtWc2D

This class is defined as follows:

Name:	ArtWc2D
Screen Text:	Artificial Watercourse 2D
Plural:	Artificial Watercourse 2Ds
Description:	An Artificial Watercourse represented as a polygon.
Use 'an':	Yes
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.2.1. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.2.2. Attribute: flow

Name:	flow
Screen Text:	Flow
Description:	Whether the flow is permanent or intermittent.
Plural:	Flows
SQL Type:	smallint
Width:	1
Code List:	FlowTy
Field Position (Width):	1
Mandatory:	Yes

3.2.3. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.3. Class: Art_Wc

This class is defined as follows:

Name:	Art_Wc
Screen Text:	Artificial Watercourse
Plural:	Artificial Watercourse
Description:	An artificial way or course above MHWM through which water may or does flow.
Use 'an':	Yes
Spatial:	Yes
Feature Types:	la

It contains the following attributes:

3.3.1. Attribute: artwc_ty

Name:	artwc_ty
Screen Text:	Artificial Watercourse Type
Description:	The type of Artificial Watercourse.
Plural:	Artificial Watercourse Types
SQL Type:	smallint
Width:	6
Code List:	ArtWcTy
Field Position (Width):	6
Mandatory:	Yes

3.3.2. Attribute: relgrnd

Name:	relgrnd
Screen Text:	Relation to Ground
Description:	The position in relation to the ground.
Plural:
SQL Type:	smallint
Width:	6
Code List:	RelGrnd
Field Position (Width):	6
Mandatory:	Yes

3.3.3. Attribute: inuse

Name:	inuse
Screen Text:	In Use
Description:	Whether the instance is in use or not in use.
Plural:	In Uses
SQL Type:	smallint
Width:	6
Code List:	InUse
Field Position (Width):	6

3.4. Class: Dam

This class is defined as follows:

Name:	Dam
Screen Text:	Dam
Plural:	Dams
Description:	A barrier constructed across a watercourse to control the flow or raise the level of water. (ICSM)
Spatial:	Yes
Feature Types:	lP

It contains the following attributes:

3.4.1. Attribute: dam_id

Name:	dam_id
Screen Text:	Dam ID
Description:	The identifier for a Dam.
Plural:
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.4.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.4.3. Attribute: dam_type

Name:	dam_type
Screen Text:	Dam Type
Description:	The form of a Dam.
Plural:
SQL Type:	smallint
Width:	6
Code List:	DamType
Field Position (Width):	6
Mandatory:	Yes

3.4.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.4.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.4.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.4.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.5. Class: Dam_0D

This class is defined as follows:

Name:	Dam_0D
Screen Text:	Dam 0D
Plural:	Dam 0Ds
Description:	A Dam represented as a point.
Spatial:	Yes
Feature Types:	a

It does not contain any attributes.

3.6. Class: Dam_1D

This class is defined as follows:

Name:	Dam_1D
Screen Text:	Dam 1D
Plural:	Dam 1Ds
Description:	A Dam represented as a chain.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.6.1. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.7. Class: Dam_2D

This class is defined as follows:

Name:	Dam_2D
Screen Text:	Dam 2D
Plural:	Dam 2Ds
Description:	A Dam represented as a polygon.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.7.1. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.8. Class: Estuary

This class is defined as follows:

Name:	Estuary
Screen Text:	Estuary
Plural:	Estuaries
Description:	[See Specifications Volume 3]
Use 'an':	Yes
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.8.1. Attribute: estuary_id

Name:	estuary_id
Screen Text:	Estuary ID
Description:	The identifier for an Estuary.
Plural:	Estuary IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.8.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.8.3. Attribute: est_feat

Name:	est_feat
Screen Text:	Estuary Feature
Description:	The type of feature that forms an Estuary.
Plural:	Estuary Features
SQL Type:	smallint
Width:	6
Code List:	EstFeat
Field Position (Width):	6
Mandatory:	Yes

3.8.4. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.8.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.8.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.8.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.8.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.8.9. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.9. Class: Flat

This class is defined as follows:

Name:	Flat
Screen Text:	Flat
Plural:	Flats
Description:	A level area of ground where periodic flooding is causing salinity.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.9.1. Attribute: flat_id

Name:	flat_id
Screen Text:	Flat ID
Description:	The identifier for a Flat.
Plural:
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.9.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.9.3. Attribute: flat_type

Name:	flat_type
Screen Text:	Flat Type
Description:	The type of Flat.
Plural:
SQL Type:	smallint
Width:	6
Code List:	FlatType
Field Position (Width):	6
Mandatory:	Yes

3.9.4. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.9.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.9.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.9.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.9.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.9.9. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.10. Class: Floodpl

This class is defined as follows:

Name:	Floodpl
Screen Text:	Floodplain
Plural:	Floodplains
Description:	A nearly-flat plain that is adjacent to a Watercourse, is naturally subject to flooding and whose boundaries are (a) very indefinite and (b) might be based on field verification or local knowledge.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.10.1. Attribute: floodpl_id

Name:	floodpl_id
Screen Text:	Floodplain ID
Description:	The identifier for a Floodplain.
Plural:	Floodplain IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.10.2. Attribute: flood_deg

Name:	flood_deg
Screen Text:	Flooding Degree
Description:	The degree of flooding.
Plural:	Flood Degrees
SQL Type:	smallint
Width:	6
Code List:	FloodDeg
Field Position (Width):	6
Mandatory:	Yes

3.10.3. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.10.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.10.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.10.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.10.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.10.8. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.11. Class: HydCntr

This class is defined as follows:

Name:	HydCntr
Screen Text:	Hydrographic Connector
Plural:	Hydrographic Connectors
Description:	A pseudo-feature that creates an artificially continuous linear hydrographic feature by (a) joining two otherwise discrete parts of a linear feature, or (b) extending a linear feature to an imaginary junction with another feature.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.11.1. Attribute: hydcntr_id

Name:	hydcntr_id
Screen Text:	Hydrographic Connector ID
Description:	The identifier for a Hydrographic Connector.
Plural:	Hydrographic Connector IDs
SQL Type:	smallint
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.11.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.11.3. Attribute: hydcntr_ty

Name:	hydcntr_ty
Screen Text:	Hydrographic Connector Type
Description:	The class of feature traversed, joined or extended by an instance and, where a Watercourse 2D is traversed, the type of flow.
Plural:	Hydrographic Connector Types
SQL Type:	smallint
Width:	6
Code List:	HydConTy
Field Position (Width):	6
Mandatory:	Yes

3.11.4. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.11.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.11.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.11.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.11.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.12. Class: Hyd_Close

This class is defined as follows:

Name:	Hyd_Close
Screen Text:	Hydrographic Closure
Plural:	Hydrographic Closures
Description:	A pseudo-feature used as an arbitrary boundary where adjacent hydrographic features have no natural common boundary.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.12.1. Attribute: hydclse_id

Name:	hydclse_id
Screen Text:	Hydrographic Closure ID
Description:	The identifier for a Hydrographic Closure.
Plural:	Hydrographic Closure IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes
Unique:	Yes

3.12.2. Attribute: adj_feat_1

Name:	adj_feat_1
Screen Text:	Adjacent Feature 1
Description:	The class of the feature which is adjacent on one side.
Plural:	Adjacent Feature 1s
SQL Type:	smallint
Width:	6
Code List:	AdjFeat
Field Position (Width):	6
Mandatory:	Yes
Use 'an':	Yes

3.12.3. Attribute: adj_feat_2

Name:	adj_feat_2
Screen Text:	Adjacent Feature 2
Description:	The class of the feature which is adjacent on the other side.
Plural:	Adjacent Feature 2s
SQL Type:	smallint
Width:	6
Code List:	AdjFeat
Field Position (Width):	6
Mandatory:	Yes
Use 'an':	Yes

3.12.4. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.12.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.12.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.12.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.12.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.13. Class: Land

This class is defined as follows:

Name:	Land
Screen Text:	Land
Plural:	Lands
Description:	an island within a Water Body or Watercourse 2D or an area surrounded by and above MHWM.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.13.1. Attribute: land_id

Name:	land_id
Screen Text:	Land ID
Description:	The identifier for a Land.
Plural:	Land IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.13.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.13.3. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.13.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.13.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.13.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.13.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.13.8. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.14. Class: Rapid

This class is defined as follows:

Name:	Rapid
Screen Text:	Rapid
Plural:	Rapids
Description:	An area of broken, fast flowing water in a stream. (ICSM)
Spatial:	Yes
Feature Types:	pa

It contains the following attributes:

3.14.1. Attribute: rapid_id

Name:	rapid_id
Screen Text:	Rapid ID
Description:	The identifier for a Rapid.
Plural:	Rapid IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.14.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.14.3. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.14.4. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.14.5. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.14.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.15. Class: Rapid_0D

This class is defined as follows:

Name:	Rapid_0D
Screen Text:	Rapid 0D
Plural:	Rapid 0Ds
Description:	A Rapid represented as a point.
Spatial:	Yes
Feature Types:	p

It does not contain any attributes.

3.16. Class: Rapid_2D

This class is defined as follows:

Name:	Rapid_2D
Screen Text:	Rapid 2D
Plural:	Rapid 2Ds
Description:	A Rapid represented as a polygon.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.16.1. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.16.2. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.17. Class: Rock

This class is defined as follows:

Name:	Rock
Screen Text:	Rock
Plural:	Rocks
Description:	An isolated rock formation or monolith either on land or in the sea or a water body. (ICSM)
Spatial:	Yes
Feature Types:	p

It contains the following attributes:

3.17.1. Attribute: rock_id

Name:	rock_id
Screen Text:	Rock ID
Description:	The identifier for a Rock.
Plural:	Rock IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.17.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.17.3. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.17.4. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.17.5. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.17.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.18. Class: Sea

This class is defined as follows:

Name:	Sea
Screen Text:	Sea
Plural:	Seas
Description:	An area of water below MHWM but not including an Estuary.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.18.1. Attribute: sea_id

Name:	sea_id
Screen Text:	Sea ID
Description:	The identifier for a Sea.
Plural:	Sea IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.18.2. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.18.3. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.18.4. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.18.5. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.18.6. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.19. Class: Spring

This class is defined as follows:

Name:	Spring
Screen Text:	Spring
Plural:	Springs
Description:	A place where water issues from the ground naturally. (ICSM)
Spatial:	Yes
Feature Types:	p

It contains the following attributes:

3.19.1. Attribute: spring_id

Name:	spring_id
Screen Text:	Spring ID
Description:	The identifier for a Spring.
Plural:	Spring IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.19.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.19.3. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.19.4. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.19.5. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.19.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.20. Class: SubReef

This class is defined as follows:

Name:	SubReef
Screen Text:	Submerged Reef
Plural:	Submerged Reefs
Description:	An area of rock in a Sea or an Estuary, that is close to the surface but is usually submerged at low tide.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.20.1. Attribute: subreef_id

Name:	subreef_id
Screen Text:	Submerged Reef ID
Description:	The identifier for a Submerged Reef.
Plural:	Submerged Reef IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.20.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.20.3. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.20.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.20.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.20.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.20.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.20.8. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.21. Class: SubTree

This class is defined as follows:

Name:	SubTree
Screen Text:	Submerged Trees
Plural:	Submerged Trees
Description:	An area of drowned trees that are wholly or partly submerged.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.21.1. Attribute: subtree_id

Name:	subtree_id
Screen Text:	Submerged Trees ID
Description:	The identifier for a Submerged Trees.
Plural:	Submerged Trees IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.21.2. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.21.3. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.21.4. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.21.5. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.21.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.21.7. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.22. Class: TLine

This class is defined as follows:

Name:	TLine
Screen Text:	Tidal Line
Plural:	Tidal Lines
Description:	(a) A boundary of a Tidal Zone or (b) a line where MHWM and MLWM coincide or (c) a channel immediately below mean low water mark and less than 10 m wide.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.22.1. Attribute: tline_id

Name:	tline_id
Screen Text:	Tidal Line ID
Description:	The identifier for a Tidal Line.
Plural:	Tidal Line IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.22.2. Attribute: tline_ty

Name:	tline_ty
Screen Text:	Tidal Line Type
Description:	Type of boundary of a Tidal Zone; or a linear feature.
Plural:	Tidal Line Types
SQL Type:	smallint
Width:	6
Code List:	TLineTy
Field Position (Width):	6

3.22.3. Attribute: mhwm_type

Name:	mhwm_type
Screen Text:	MHWM Type
Description:	The structure or surface on which MHWM is found.
Plural:
SQL Type:	smallint
Width:	6
Code List:	MHWMType
Field Position (Width):	6

3.22.4. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.22.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.22.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.22.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.22.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.23. Class: TZone

This class is defined as follows:

Name:	TZone
Screen Text:	Tidal Zone
Plural:	Tidal Zones
Description:	An area between MHWM and MLWM having a uniform surface type.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.23.1. Attribute: tzone_id

Name:	tzone_id
Screen Text:	Tidal Zone ID
Description:	The identifier for a Tidal Zone.
Plural:	Tidal Zone IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.23.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.23.3. Attribute: tsurf_ty

Name:	tsurf_ty
Screen Text:	Tidal Zone Surface Type
Description:	The type of surface of a Tidal Zone.
Plural:	Tidal Zone SurfaceTypes
SQL Type:	smallint
Width:	6
Code List:	TSurfTy
Field Position (Width):	6

3.23.4. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.23.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.23.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.23.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.23.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.23.9. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.24. Class: WBody

This class is defined as follows:

Name:	WBody
Screen Text:	Water Body
Plural:	Water Bodies
Description:	Any body of inland water that has a generally level surface.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.24.1. Attribute: wbody_id

Name:	wbody_id
Screen Text:	Water Body ID
Description:	The identifier for a Water Body.
Plural:	Water Body IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.24.2. Attribute: wbody_type

Name:	wbody_type
Screen Text:	Water Body Type
Description:	The type of feature that forms a Water Body.
Plural:	Water Body Types
SQL Type:	smallint
Width:	6
Code List:	WBodyTy
Field Position (Width):	6
Mandatory:	Yes

3.24.3. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.24.4. Attribute: wbody_exst

Name:	wbody_exst
Screen Text:	Water Body Existence
Description:	The existence of the Water Body.
Plural:	Water Body Existence
SQL Type:	smallint
Width:	6
Code List:	WBodyEx
Field Position (Width):	6
Mandatory:	Yes

3.24.5. Attribute: elevation

Name:	elevation
Screen Text:	Elevation
Description:	The elevation relative to the adopted datum for the land. (For a Water Body, it applies to the surface when full.)
Plural:	Elevations
SQL Type:	smallint
Width:	6
Field Position (Width):	6
Mandatory:	Yes

3.24.6. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.24.7. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.24.8. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.24.9. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.24.10. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.24.11. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.25. Class: Wcourse

This class is defined as follows:

Name:	Wcourse
Screen Text:	Watercourse
Plural:	Watercourses
Description:	A way or course through which water may or does flow. (ICSM)
Spatial:	Yes
Feature Types:	la

It contains the following attributes:

3.25.1. Attribute: wcourse_id

Name:	wcourse_id
Screen Text:	Watercourse ID
Description:	The identifier for a Watercourse.
Plural:	Watercourse IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.25.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.25.3. Attribute: wcourse_cl

Name:	wcourse_cl
Screen Text:	Watercourse Class
Description:	Whether a Watercourse is major or minor.
Plural:	Watercourse Classes
SQL Type:	smallint
Width:	6
Code List:	WcClass
Field Position (Width):	6
Mandatory:	Yes

3.25.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.25.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.25.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.25.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.26. Class: Wcrse1D

This class is defined as follows:

Name:	Wcrse1D
Screen Text:	Watercourse 1D
Plural:	Watercourse 1Ds
Description:	A natural Watercourse represented as a chain.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.26.1. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.26.2. Attribute: impld_wc

Name:	impld_wc
Screen Text:	Implied Watercourse
Description:	Whether the watercourse is implied or well defined.
Plural:	Implied Watercourses
SQL Type:	smallint
Width:	6
Code List:	ImpldWc
Field Position (Width):	6
Mandatory:	Yes
Use 'an':	Yes

3.27. Class: Wcrse2D

This class is defined as follows:

Name:	Wcrse2D
Screen Text:	Watercourse 2D
Plural:	Watercourse 2Ds
Description:	A natural Watercourse represented as a polygon.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.27.1. Attribute: flow

Name:	flow
Screen Text:	Flow
Description:	Whether the flow is permanent or intermittent.
Plural:	Flows
SQL Type:	smallint
Width:	1
Code List:	FlowTy
Field Position (Width):	1
Mandatory:	Yes

3.27.2. Attribute: wc_bed_ty

Name:	wc_bed_ty
Screen Text:	Watercourse Bed Type
Description:	The type of material on the bed of a Watercourse.
Plural:
SQL Type:	smallint
Width:	6
Code List:	WcBedTy
Field Position (Width):	6
Mandatory:	Yes

3.27.3. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.27.4. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.28. Class: Wetland

This class is defined as follows:

Name:	Wetland
Screen Text:	Wetland
Plural:	Wetlands
Description:	A vegetated area that is flooded or saturated by surface or groundwater. (ICSM)
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.28.1. Attribute: wetland_id

Name:	wetland_id
Screen Text:	Wetland ID
Description:	The identifier for a Wetland.
Plural:	Wetland IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.28.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.28.3. Attribute: wetland_ty

Name:	wetland_ty
Screen Text:	Wetland Type
Description:	A classification for Wetlands.
Plural:
SQL Type:	smallint
Width:	6
Code List:	WetlndTy
Field Position (Width):	6
Mandatory:	Yes

3.28.4. Attribute: comp_area

Name:	comp_area
Screen Text:	Computed Area
Description:	The computed area in square metres.
Plural:	Computed Areas
SQL Type:	numeric(12,1)
Width:	14
Field Position (Width):	14
Mandatory:	Yes

3.28.5. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.28.6. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.28.7. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.28.8. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.28.9. Attribute: valid_area

Name:	valid_area
Screen Text:	Valid Area
Description:	Whether the area is a valid instance or not.
Plural:	Valid Areas
SQL Type:	smallint
Width:	6
Code List:	Valid
Field Position (Width):	6
Mandatory:	Yes

3.29. Class: Wfall_0D

This class is defined as follows:

Name:	Wfall_0D
Screen Text:	Waterfall 0D
Plural:	Waterfall 0Ds
Description:	A Waterfall represented as a point.
Spatial:	Yes
Feature Types:	p

It does not contain any attributes.

3.30. Class: Wfall_1D

This class is defined as follows:

Name:	Wfall_1D
Screen Text:	Waterfall 1D
Plural:	Waterfall 1Ds
Description:	A Waterfall represented as a chain.
Spatial:	Yes
Feature Types:	l

It does not contain any attributes.

3.31. Class: WtrLine

This class is defined as follows:

Name:	WtrLine
Screen Text:	Water Line
Plural:	Water Lines
Description:	A boundary, other than MHWM or a Watercourse 1D, of an Artificial Watercourse 2D, Flat, Floodplain, Water Body, Watercourse 2D or Wetland.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.31.1. Attribute: wtrline_id

Name:	wtrline_id
Screen Text:	Water Line ID
Description:	The identifier for a Water Line.
Plural:	Water Line IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.31.2. Attribute: assmd_ln

Name:	assmd_ln
Screen Text:	Assumed Water Line
Description:	Whether the Water Line is assumed or observed.
Plural:	Assumed Water Lines
SQL Type:	smallint
Width:	6
Code List:	AssmdWL
Field Position (Width):	6
Mandatory:	Yes
Use 'an':	Yes

3.31.3. Attribute: comp_len

Name:	comp_len
Screen Text:	Computed Length
Description:	The computed length of the feature instance, in metres.
Plural:	Computed Lengths
SQL Type:	numeric(6,1)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.31.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier
Plural:	Ufis
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.31.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.31.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.31.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

3.32. Class: Wtrfall

This class is defined as follows:

Name:	Wtrfall
Screen Text:	Waterfall
Plural:	Waterfalls
Description:	A sudden descent of water over a step or ledge in the bed of a stream. (after ICSM)
Spatial:	Yes
Feature Types:	pl

It contains the following attributes:

3.32.1. Attribute: wtrfall_id

Name:	wtrfall_id
Screen Text:	Waterfall ID
Description:	The identifier for a Waterfall.
Plural:	Waterfall IDs
SQL Type:	integer
Width:	10
Field Position (Width):	10
Mandatory:	Yes

3.32.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nomenclature Register Number
Description:	The unique identifier in the state Nomenclature Register for a named feature represented by an instance.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7

3.32.3. Attribute: height

Name:	height
Screen Text:	Height
Description:	The vertical distance from the base to the top (ICSM), in metres.
Plural:
SQL Type:	smallint
Width:	6
Field Position (Width):	6

3.32.4. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	A unique feature identifier.
Plural:	UFIs
SQL Type:	varchar(12)
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.32.5. Attribute: fmp

Name:	fmp
Screen Text:	FMP
Description:	Feature Metadata Pointer
Plural:	Fmps
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.32.6. Attribute: created_on

Name:	created_on
Screen Text:	Date Created
Description:	The date on which the record was placed in the database.
Plural:	Date Created
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.32.7. Attribute: retired_on

Name:	retired_on
Screen Text:	Date Retired
Description:	The date on which the record was retired from the database.
Plural:	Date Retired
SQL Type:	date
Width:	8
Field Position (Width):	8

4. Relationships

The relationships are listed together as a 'pair' between classes. Further details on each individual relationship 'direction' is also provided.

4.1. Relationship Pair: ArtWc1D (Art_Wc_1D_to_Art_Wc) and Art_Wc (Art_Wc_to_Art_Wc_1D)

ArtWc1D is derived from Art_Wc.

4.1.1. From ArtWc1D To Art_Wc

Name:	Art_Wc_1D_to_Art_Wc
Screen Text:	Art Wc 1D To Art Wc
Plural:	Art Wc 1D To Art Wcs
Description:	Art Wc 1D To Art Wc
Base Attribute:
Class Type Value:

4.1.2. From Art_Wc To ArtWc1D

Name:	Art_Wc_to_Art_Wc_1D
Screen Text:	Art Wc To Art Wc 1D
Plural:	Art Wc To Art Wc 1Ds
Description:	Art Wc To Art Wc 1D
Base Attribute:
Class Type Value:

4.2. Relationship Pair: ArtWc2D (Art_Wc_2D_to_Art_Wc) and Art_Wc (Art_Wc_to_Art_Wc_2D)

ArtWc2D is derived from Art_Wc.

4.2.1. From ArtWc2D To Art_Wc

Name:	Art_Wc_2D_to_Art_Wc
Screen Text:	Art Wc 2D To Art Wc
Plural:	Art Wc 2D To Art Wcs
Description:	Art Wc 2D To Art Wc
Base Attribute:
Class Type Value:

4.2.2. From Art_Wc To ArtWc2D

Name:	Art_Wc_to_Art_Wc_2D
Screen Text:	Art Wc To Art Wc 2D
Plural:	Art Wc To Art Wc 2Ds
Description:	Art Wc To Art Wc 2D
Base Attribute:
Class Type Value:

4.3. Relationship Pair: ArtWc2D (Art_Wc_2D_to_Wtr_Line) and WtrLine (Wtr_Line_to_Art_Wc_2D)

Each record in ArtWc2D is related to one or more records in WtrLine. Each record in WtrLine can be related to (optionally) one record in ArtWc2D.

4.3.1. From ArtWc2D To WtrLine

Name:	Art_Wc_2D_to_Wtr_Line
Screen Text:	Art Wc 2D To Wtr Line
Plural:	Art Wc 2D To Wtr Lines
Description:	Art Wc 2D To Wtr Line
Primary Class:	ArtWc2D
Foreign Class:	WtrLine

4.3.2. From WtrLine To ArtWc2D

Name:	Wtr_Line_to_Art_Wc_2D
Screen Text:	Wtr Line To Art Wc 2D
Plural:	Wtr Line To Art Wc 2Ds
Description:	Wtr Line To Art Wc 2D
Primary Class:	ArtWc2D
Foreign Class:	WtrLine

4.4. Relationship Pair: Art_Wc (Water_pipeline_to_Watercourse) and Wcourse (Watercourse_to_Water_pipeline)

Art_Wc is derived from Wcourse. This relationship pair is represented spatially.

4.4.1. From Art_Wc To Wcourse

Name:	Water_pipeline_to_Watercourse
Screen Text:	Water Pipeline To Watercourse
Plural:	Water Pipeline To Watercourses
Description:	Water Pipeline To Watercourse
Base Attribute:
Class Type Value:

4.4.2. From Wcourse To Art_Wc

Name:	Watercourse_to_Water_pipeline
Screen Text:	Watercourse To Water Pipeline
Plural:	Watercourses To Water Pipeline
Description:	Watercourse To Water Pipeline
Base Attribute:
Class Type Value:

4.4.3. Spatial Representation

Class Art_Wc is represented via simple line and area features. Class Wcourse is represented via simple line and area features. The features are related together via the following boundary/interior intersections:

4.5. Relationship Pair: Art_Wc (Art_Wc_to_Art_Wc_2D) and ArtWc2D (Art_Wc_2D_to_Art_Wc)

See Relationship Pair: ArtWc2D (Art_Wc_2D_to_Art_Wc) and Art_Wc (Art_Wc_to_Art_Wc_2D)}.

4.6. Relationship Pair: Art_Wc (Art_Wc_to_Art_Wc_1D) and ArtWc1D (Art_Wc_1D_to_Art_Wc)

See Relationship Pair: ArtWc1D (Art_Wc_1D_to_Art_Wc) and Art_Wc (Art_Wc_to_Art_Wc_1D)}.

4.7. Relationship Pair: Dam (Dam_to_Water_Body) and WBody (Water_body_to_Dam)

Each record in Dam can be related to (optionally) one record in WBody. Each record in WBody is related to zero or more records in Dam. This relationship pair is represented spatially.

4.7.1. From Dam To WBody

Name:	Dam_to_Water_Body
Screen Text:	Dam To Water Body
Plural:	Dams To Water Body
Description:	Dam To Water Body

4.7.2. From WBody To Dam

Name:	Water_body_to_Dam
Screen Text:	Water Body To Dam
Plural:	Water Body To Dams
Description:	Water Body To Dam

4.7.3. Spatial Representation

Class Dam is represented via simple line features. Class WBody is represented via area features. The features are related together via the following boundary/interior intersections:

Line-Polygon (1-2): The following "OR"-ed together:

Interior of Dam intersects with boundary of WBody.

4.8. Relationship Pair: Dam (Dam_to_Dam_1D) and Dam_1D (Dam_1D_to_Dam)

Dam_1D is derived from Dam.

4.8.1. From Dam To Dam_1D

Name:	Dam_to_Dam_1D
Screen Text:	Dam To Dam 1D
Plural:	Dams To Dam 1D
Description:	Dam To Dam 1D
Base Attribute:
Class Type Value:

4.8.2. From Dam_1D To Dam

Name:	Dam_1D_to_Dam
Screen Text:	Dam 1D To Dam
Plural:	Dam 1D To Dams
Description:	Dam 1D To Dam
Base Attribute:
Class Type Value:

4.9. Relationship Pair: Dam (Dam_to_Dam_2D) and Dam_2D (Dam_2D_to_Dam)

Dam_2D is derived from Dam.

4.9.1. From Dam To Dam_2D

Name:	Dam_to_Dam_2D
Screen Text:	Dam To Dam 2D
Plural:	Dams To Dam 2D
Description:	Dam To Dam 2D
Base Attribute:
Class Type Value:

4.9.2. From Dam_2D To Dam

Name:	Dam_2D_to_Dam
Screen Text:	Dam 2D To Dam
Plural:	Dam 2D To Dams
Description:	Dam 2D To Dam
Base Attribute:
Class Type Value:

4.10. Relationship Pair: Dam (Dam_to_Wcourse) and Wcourse (Wcourse_to_Dam)

Each record in Dam is always related to one (and only one) record in Wcourse. Each record in Wcourse is related to zero or more records in Dam.

4.10.1. From Dam To Wcourse

Name:	Dam_to_Wcourse
Screen Text:	Dam To Wcourse
Plural:	Dams To Wcourse
Description:	Dam To Wcourse
Primary Class:	Wcourse
Foreign Class:	Dam

4.10.2. From Wcourse To Dam

Name:	Wcourse_to_Dam
Screen Text:	Wcourse To Dam
Plural:	Wcourses To Dam
Description:	Wcourse To Dam
Primary Class:	Wcourse
Foreign Class:	Dam

4.11. Relationship Pair: Dam (Dam_to_Dam_0D) and Dam_0D (Dam_0D_to_Dam)

Dam_0D is derived from Dam.

4.11.1. From Dam To Dam_0D

Name:	Dam_to_Dam_0D
Screen Text:	Dam To Dam 0D
Plural:	Dams To Dam 0D
Description:	Dam To Dam 0D
Base Attribute:
Class Type Value:

4.11.2. From Dam_0D To Dam

Name:	Dam_0D_to_Dam
Screen Text:	Dam 0D To Dam
Plural:	Dam 0D To Dams
Description:	Dam 0D To Dam
Base Attribute:
Class Type Value:

4.12. Relationship Pair: Dam_0D (Dam_0D_to_Dam) and Dam (Dam_to_Dam_0D)

See Relationship Pair: Dam (Dam_to_Dam_0D) and Dam_0D (Dam_0D_to_Dam)}.

4.13. Relationship Pair: Dam_1D (Dam_1D_to_Dam) and Dam (Dam_to_Dam_1D)

See Relationship Pair: Dam (Dam_to_Dam_1D) and Dam_1D (Dam_1D_to_Dam)}.

4.14. Relationship Pair: Dam_2D (Dam_2D_to_Dam) and Dam (Dam_to_Dam_2D)

See Relationship Pair: Dam (Dam_to_Dam_2D) and Dam_2D (Dam_2D_to_Dam)}.

4.15. Relationship Pair: Estuary (Estuary_to_Hyd_Clos) and Hyd_Close (Hyd_Clos_to_Estuary)

Each record in Estuary is related to one or more records in Hyd_Close. Each record in Hyd_Close is related to zero or more records in Estuary. This relationship pair is represented spatially.

4.15.1. From Estuary To Hyd_Close

Name:	Estuary_to_Hyd_Clos
Screen Text:	Estuary To Closure
Plural:	Estuarys To Closure
Description:	Estuary To Closure

4.15.2. From Hyd_Close To Estuary

Name:	Hyd_Clos_to_Estuary
Screen Text:	Closure To Estuary
Plural:	Closures To Estuary
Description:	Closure To Estuary

4.15.3. Spatial Representation

Class Estuary is represented via area features. Class Hyd_Close is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of Hyd_Close intersects with boundary and interior of Estuary.

4.16. Relationship Pair: Estuary (Estuary_to_Tidal_zone) and TZone (Tidal_zone_to_Estuary)

Each record in Estuary is related to one or more records in TZone. Each record in TZone is related to zero or more records in Estuary. This relationship pair is represented spatially.

4.16.1. From Estuary To TZone

Name:	Estuary_to_Tidal_zone
Screen Text:	Estuary To Tidal Zone
Plural:	Estuarys To Tidal Zone
Description:	Estuary To Tidal Zone

4.16.2. From TZone To Estuary

Name:	Tidal_zone_to_Estuary
Screen Text:	Tidal Zone To Estuary
Plural:	Tidal Zone To Estuarys
Description:	Tidal Zone To Estuary

4.16.3. Spatial Representation

Class Estuary is represented via area features. Class TZone is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of Estuary intersects with boundary of TZone AND interior of Estuary intersects with interior and boundary of TZone.

4.17. Relationship Pair: Estuary (Estuary_to_Hyd_Conn) and HydCntr (Hyd_Conn_to_Estuary)

Each record in Estuary is related to one or more records in HydCntr. Each record in HydCntr can be related to (optionally) one record in Estuary. This relationship pair is represented spatially.

4.17.1. From Estuary To HydCntr

Name:	Estuary_to_Hyd_Conn
Screen Text:	Estuary To Connector
Plural:	Estuarys To Connector
Description:	Estuary To Connector

4.17.2. From HydCntr To Estuary

Name:	Hyd_Conn_to_Estuary
Screen Text:	Connector To Estuary
Plural:	Connectors To Estuary
Description:	Connector To Estuary

4.17.3. Spatial Representation

Class Estuary is represented via area features. Class HydCntr is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of HydCntr intersects with boundary of Estuary AND interior of HydCntr intersects with interior and boundary of Estuary.

4.18. Relationship Pair: Estuary (Estuary_to_Sub_reef) and SubReef (Sub_reef_to_Estuary)

Each record in Estuary is related to zero or more records in SubReef. Each record in SubReef is related to zero or more records in Estuary. This relationship pair is represented spatially.

4.18.1. From Estuary To SubReef

Name:	Estuary_to_Sub_reef
Screen Text:	Estuary To Sub Reef
Plural:	Estuarys To Sub Reef
Description:	Estuary To Sub Reef

4.18.2. From SubReef To Estuary

Name:	Sub_reef_to_Estuary
Screen Text:	Sub Reef To Estuary
Plural:	Sub Reef To Estuarys
Description:	Sub Reef To Estuary

4.18.3. Spatial Representation

Class Estuary is represented via area features. Class SubReef is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

No intersection between Estuary and SubReef allowed.

4.19. Relationship Pair: Estuary (Estuary_to_Tdl_Line) and TLine (Tdl_Line_to_Estuary)

Each record in Estuary is related to one or more records in TLine. Each record in TLine is related to zero or more records in Estuary.

4.19.1. From Estuary To TLine

Name:	Estuary_to_Tdl_Line
Screen Text:	Estuary To Tdl Line
Plural:	Estuarys To Tdl Line
Description:	Estuary To Tdl Line
Primary Class:	TLine
Foreign Class:	Estuary

4.19.2. From TLine To Estuary

Name:	Tdl_Line_to_Estuary
Screen Text:	Tdl Line To Estuary
Plural:	Tdl Line To Estuarys
Description:	Tdl Line To Estuary
Primary Class:	TLine
Foreign Class:	Estuary

4.20. Relationship Pair: Flat (Flat_to_Land) and Land (Land_to_Flat)

Each record in Flat is always related to one (and only one) record in Land. Each record in Land is related to zero or more records in Flat. This relationship pair is represented spatially.

4.20.1. From Flat To Land

Name:	Flat_to_Land
Screen Text:	Flat To Land
Plural:	Flats To Land
Description:	Flat To Land

4.20.2. From Land To Flat

Name:	Land_to_Flat
Screen Text:	Land To Flat
Plural:	Lands To Flat
Description:	Land To Flat

4.20.3. Spatial Representation

Class Flat is represented via area features. Class Land is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of Flat intersects with boundary and interior of Land AND interior of Flat intersects with interior of Land.

4.21. Relationship Pair: Flat (Flat_to_Flood_plain) and Floodpl (Flood_plain_to_Flat)

Each record in Flat can be related to (optionally) one record in Floodpl. Each record in Floodpl is related to zero or more records in Flat. This relationship pair is represented spatially.

4.21.1. From Flat To Floodpl

Name:	Flat_to_Flood_plain
Screen Text:	Flat To Flood Plain
Plural:	Flats To Flood Plain
Description:	Flat To Flood Plain

4.21.2. From Floodpl To Flat

Name:	Flood_plain_to_Flat
Screen Text:	Flood Plain To Flat
Plural:	Flood Plain To Flats
Description:	Flood Plain To Flat

4.21.3. Spatial Representation

Class Flat is represented via area features. Class Floodpl is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of Flat intersects with boundary and interior of Floodpl AND interior of Flat intersects with interior of Floodpl.

4.22. Relationship Pair: Flat (Flat_to_Water_lines) and WtrLine (water_lines_to_flat)

Each record in Flat is related to one or more records in WtrLine. Each record in WtrLine can be related to (optionally) one record in Flat. This relationship pair is represented spatially.

4.22.1. From Flat To WtrLine

Name:	Flat_to_Water_lines
Screen Text:	Flat To Water Lines
Plural:	Flats To Water Lines
Description:	Flat To Water Lines

4.22.2. From WtrLine To Flat

Name:	water_lines_to_flat
Screen Text:	Water Lines To Flat
Plural:	Water Lines To Flats
Description:	Water Lines To Flat

4.22.3. Spatial Representation

Class Flat is represented via area features. Class WtrLine is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of WtrLine intersects with boundary of Flat AND interior of WtrLine intersects with boundary of Flat.

4.23. Relationship Pair: Floodpl (Flood_plain_to_Land) and Land (Land_to_Flood_plain)

Each record in Floodpl is related to one or more records in Land. Each record in Land is related to zero or more records in Floodpl. This relationship pair is represented spatially.

4.23.1. From Floodpl To Land

Name:	Flood_plain_to_Land
Screen Text:	Flood Plain To Land
Plural:	Flood Plain To Lands
Description:	Flood Plain To Land

4.23.2. From Land To Floodpl

Name:	Land_to_Flood_plain
Screen Text:	Land To Flood Plain
Plural:	Lands To Flood Plain
Description:	Land To Flood Plain

4.23.3. Spatial Representation

Class Floodpl is represented via area features. Class Land is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of Floodpl intersects with boundary and interior of Land AND interior of Floodpl intersects with interior of Land.

4.24. Relationship Pair: Floodpl (Flood_plain_to_Wetland) and Wetland (Wetland_to_Flood_plain)

Each record in Floodpl is related to zero or more records in Wetland. Each record in Wetland can be related to (optionally) one record in Floodpl. This relationship pair is represented spatially.

4.24.1. From Floodpl To Wetland

Name:	Flood_plain_to_Wetland
Screen Text:	Flood Plain To Wetland
Plural:	Flood Plain To Wetlands
Description:	Flood Plain To Wetland

4.24.2. From Wetland To Floodpl

Name:	Wetland_to_Flood_plain
Screen Text:	Wetland To Flood Plain
Plural:	Wetlands To Flood Plain
Description:	Wetland To Flood Plain

4.24.3. Spatial Representation

Class Floodpl is represented via area features. Class Wetland is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of Floodpl intersects with boundary of Wetland AND interior of Floodpl intersects with interior and boundary of Wetland.

4.25. Relationship Pair: Floodpl (Flood_plain_to_Flat) and Flat (Flat_to_Flood_plain)

See Relationship Pair: Flat (Flat_to_Flood_plain) and Floodpl (Flood_plain_to_Flat)}.

4.26. Relationship Pair: Floodpl (flood_plains_to_water_lines) and WtrLine (water_lines_to_flood_plains)

Each record in Floodpl is related to one or more records in WtrLine. Each record in WtrLine is related to zero or more records in Floodpl. This relationship pair is represented spatially.

4.26.1. From Floodpl To WtrLine

Name:	flood_plains_to_water_lines
Screen Text:	Flood Plains To Water Lines
Plural:	Flood Plains To Water Lineses
Description:	Flood Plains To Water Lines

4.26.2. From WtrLine To Floodpl

Name:	water_lines_to_flood_plains
Screen Text:	Water Lines To Flood Plains
Plural:	Water Lines To Flood Plainses
Description:	Water Lines To Flood Plains

4.26.3. Spatial Representation

Class Floodpl is represented via area features. Class WtrLine is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of WtrLine intersects with boundary of Floodpl AND interior of WtrLine intersects with boundary of Floodpl.

4.27. Relationship Pair: HydCntr (Hyd_Conn_to_Wtr_Body) and WBody (Wtr_Body_to_Hyd_Conn)

Each record in HydCntr can be related to (optionally) one record in WBody. Each record in WBody is related to zero or more records in HydCntr. This relationship pair is represented spatially.

4.27.1. From HydCntr To WBody

Name:	Hyd_Conn_to_Wtr_Body
Screen Text:	Connector To Water Body
Plural:	Connectors To Water Body
Description:	Connector To Water Body

4.27.2. From WBody To HydCntr

Name:	Wtr_Body_to_Hyd_Conn
Screen Text:	Water Body To Connector
Plural:	Water Body To Connectors
Description:	Water Body To Connector

4.27.3. Spatial Representation

Class HydCntr is represented via simple line features. Class WBody is represented via area features. The features are related together via the following boundary/interior intersections:

Line-Polygon (1-2): The following "OR"-ed together:

Boundary of HydCntr intersects with boundary and interior of WBody AND interior of HydCntr intersects with interior of WBody.

4.28. Relationship Pair: HydCntr (Hyd_Conn_to_Estuary) and Estuary (Estuary_to_Hyd_Conn)

See Relationship Pair: Estuary (Estuary_to_Hyd_Conn) and HydCntr (Hyd_Conn_to_Estuary)}.

4.29. Relationship Pair: HydCntr (Hyd_Conn_to_Wcourse2) and Wcrse2D (Wcourse2_to_Hyd_Conn)

Each record in HydCntr can be related to (optionally) one record in Wcrse2D. Each record in Wcrse2D is related to one or more records in HydCntr. This relationship pair is represented spatially.

4.29.1. From HydCntr To Wcrse2D

Name:	Hyd_Conn_to_Wcourse2
Screen Text:	Connector To Watercourse 2D
Plural:	Connectors To Watercourse 2D
Description:	Connector To Watercourse 2D

4.29.2. From Wcrse2D To HydCntr

Name:	Wcourse2_to_Hyd_Conn
Screen Text:	Watercourse 2D To Connector
Plural:	Watercourse 2D To Connectors
Description:	Watercourse 2D To Connector

4.29.3. Spatial Representation

Class HydCntr is represented via simple line features. Class Wcrse2D is represented via area features. The features are related together via the following boundary/interior intersections:

Line-Polygon (1-2): The following "OR"-ed together:

Boundary of HydCntr intersects with boundary and interior of Wcrse2D AND interior of HydCntr intersects with interior of Wcrse2D.

4.30. Relationship Pair: HydCntr (Hyd_Conn_to_Hyd_Clos) and Hyd_Close (Hyd_Clos_to_Hyd_Conn)

Each record in HydCntr is related to zero or more records in Hyd_Close. Each record in Hyd_Close is related to one or more records in HydCntr.

4.30.1. From HydCntr To Hyd_Close

Name:	Hyd_Conn_to_Hyd_Clos
Screen Text:	Hyd Conn To Hyd Clos
Plural:	Hyd Conn To Hyd Closes
Description:	Hyd Conn To Hyd Clos
Primary Class:	Hyd_Close
Foreign Class:	HydCntr

4.30.2. From Hyd_Close To HydCntr

Name:	Hyd_Clos_to_Hyd_Conn
Screen Text:	Hyd Clos To Hyd Conn
Plural:	Hyd Clos To Hyd Conns
Description:	Hyd Clos To Hyd Conn
Primary Class:	Hyd_Close
Foreign Class:	HydCntr

4.31. Relationship Pair: Hyd_Close (Hyd_Clos_to_Sea) and Sea (Sea_to_Hyd_Clos)

Each record in Hyd_Close can be related to (optionally) one record in Sea. Each record in Sea is related to one or more records in Hyd_Close. This relationship pair is represented spatially.

4.31.1. From Hyd_Close To Sea

Name:	Hyd_Clos_to_Sea
Screen Text:	Closure To Sea
Plural:	Closures To Sea
Description:	Closure To Sea

4.31.2. From Sea To Hyd_Close

Name:	Sea_to_Hyd_Clos
Screen Text:	Sea To Closure
Plural:	Seas To Closure
Description:	Sea To Closure

4.31.3. Spatial Representation

Class Hyd_Close is represented via simple line features. Class Sea is represented via area features. The features are related together via the following boundary/interior intersections:

Line-Polygon (1-2): The following "OR"-ed together:

Boundary of Hyd_Close intersects with boundary and interior of Sea.

4.32. Relationship Pair: Hyd_Close (Hyd_Clos_to_Estuary) and Estuary (Estuary_to_Hyd_Clos)

See Relationship Pair: Estuary (Estuary_to_Hyd_Clos) and Hyd_Close (Hyd_Clos_to_Estuary)}.

4.33. Relationship Pair: Hyd_Close (Hyd_Clos_to_Wtr_Body) and WBody (Wtr_Body_to_Hyd_Clos)

Each record in Hyd_Close can be related to (optionally) one record in WBody. Each record in WBody is related to zero or more records in Hyd_Close. This relationship pair is represented spatially.

4.33.1. From Hyd_Close To WBody

Name:	Hyd_Clos_to_Wtr_Body
Screen Text:	Closure To Water Body
Plural:	Closures To Water Body
Description:	Closure To Water Body

4.33.2. From WBody To Hyd_Close

Name:	Wtr_Body_to_Hyd_Clos
Screen Text:	Water Body To Closure
Plural:	Water Body To Closures
Description:	Water Body To Closure

4.33.3. Spatial Representation

Class Hyd_Close is represented via simple line features. Class WBody is represented via area features. The features are related together via the following boundary/interior intersections:

Line-Polygon (1-2): The following "OR"-ed together:

Boundary of Hyd_Close intersects with boundary of WBody AND interior of Hyd_Close intersects with boundary of WBody.

4.34. Relationship Pair: Hyd_Close (Hyd_Clos_to_Hyd_Conn) and HydCntr (Hyd_Conn_to_Hyd_Clos)

See Relationship Pair: HydCntr (Hyd_Conn_to_Hyd_Clos) and Hyd_Close (Hyd_Clos_to_Hyd_Conn)}.

4.35. Relationship Pair: Land (Land_to_Flat) and Flat (Flat_to_Land)

See Relationship Pair: Flat (Flat_to_Land) and Land (Land_to_Flat)}.

4.36. Relationship Pair: Land (Land_to_Wetland) and Wetland (Wetland_to_Land)

Each record in Land is related to zero or more records in Wetland. Each record in Wetland is always related to one (and only one) record in Land. This relationship pair is represented spatially.

4.36.1. From Land To Wetland

Name:	Land_to_Wetland
Screen Text:	Land To Wetland
Plural:	Lands To Wetland
Description:	Land To Wetland

4.36.2. From Wetland To Land

Name:	Wetland_to_Land
Screen Text:	Wetland To Land
Plural:	Wetlands To Land
Description:	Wetland To Land

4.36.3. Spatial Representation

Class Land is represented via area features. Class Wetland is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of Land intersects with boundary of Wetland AND interior of Land intersects with interior and boundary of Wetland.

4.37. Relationship Pair: Land (Land_to_Flood_plain) and Floodpl (Flood_plain_to_Land)

See Relationship Pair: Floodpl (Flood_plain_to_Land) and Land (Land_to_Flood_plain)}.

4.38. Relationship Pair: Land (Land_to_Waterbody) and WBody (Waterbody_to_Land)

Each record in Land is related to zero or more records in WBody. Each record in WBody is related to one or more records in Land. This relationship pair is represented spatially.

4.38.1. From Land To WBody

Name:	Land_to_Waterbody
Screen Text:	Land To Waterbody
Plural:	Lands To Waterbody
Description:	Land To Waterbody

4.38.2. From WBody To Land

Name:	Waterbody_to_Land
Screen Text:	Waterbody To Land
Plural:	Waterbodys To Land
Description:	Waterbody To Land

4.38.3. Spatial Representation

Class Land is represented via area features. Class WBody is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Interior of Land intersects with interior and boundary of WBody.

4.39. Relationship Pair: Land (Land_to_Tdl_Line) and TLine (Tdl_Line_to_Land)

Each record in Land is related to zero or more records in TLine. Each record in TLine can be related to (optionally) one record in Land.

4.39.1. From Land To TLine

Name:	Land_to_Tdl_Line
Screen Text:	Land To Tdl Line
Plural:	Lands To Tdl Line
Description:	Land To Tdl Line
Primary Class:	Land
Foreign Class:	TLine

4.39.2. From TLine To Land

Name:	Tdl_Line_to_Land
Screen Text:	Tdl Line To Land
Plural:	Tdl Line To Lands
Description:	Tdl Line To Land
Primary Class:	Land
Foreign Class:	TLine

4.40. Relationship Pair: Land (Land_to_Wcourse) and Wcourse (Wcourse_to_Land)

Each record in Land is related to zero or more records in Wcourse. Each record in Wcourse is related to one or more records in Land.

4.40.1. From Land To Wcourse

Name:	Land_to_Wcourse
Screen Text:	Land To Wcourse
Plural:	Lands To Wcourse
Description:	Land To Wcourse
Primary Class:	Wcourse
Foreign Class:	Land

4.40.2. From Wcourse To Land

Name:	Wcourse_to_Land
Screen Text:	Wcourse To Land
Plural:	Wcourses To Land
Description:	Wcourse To Land
Primary Class:	Wcourse
Foreign Class:	Land

4.41. Relationship Pair: Land (Land_to_Spring) and Spring (Spring_to_Land)

Each record in Land is related to zero or more records in Spring. Each record in Spring is always related to one (and only one) record in Land.

4.41.1. From Land To Spring

Name:	Land_to_Spring
Screen Text:	Land To Spring
Plural:	Lands To Spring
Description:	Land To Spring
Primary Class:	Land
Foreign Class:	Spring

4.41.2. From Spring To Land

Name:	Spring_to_Land
Screen Text:	Spring To Land
Plural:	Springs To Land
Description:	Spring To Land
Primary Class:	Land
Foreign Class:	Spring

4.42. Relationship Pair: Rapid (Rapid_to_Watercourse) and Wcourse (Watercourse_to_Rapid)

Each record in Rapid is always related to one (and only one) record in Wcourse. Each record in Wcourse is related to zero or more records in Rapid. This relationship pair is represented spatially.

4.42.1. From Rapid To Wcourse

Name:	Rapid_to_Watercourse
Screen Text:	Rapid To Watercourse
Plural:	Rapids To Watercourse
Description:	Rapid To Watercourse

4.42.2. From Wcourse To Rapid

Name:	Watercourse_to_Rapid
Screen Text:	Watercourse To Rapid
Plural:	Watercourse To Rapids
Description:	Watercourse To Rapid

4.42.3. Spatial Representation

Class Rapid is represented via point and area features. Class Wcourse is represented via simple line and area features. The features are related together via the following boundary/interior intersections:

Point-Line (0-1): The following "OR"-ed together:

Boundary of Rapid intersects with interior of Wcourse.

4.43. Relationship Pair: Rapid (Rapid_to_Rapid_0D) and Rapid_0D (Rapid_0D_to_Rapid)

Rapid_0D is derived from Rapid.

4.43.1. From Rapid To Rapid_0D

Name:	Rapid_to_Rapid_0D
Screen Text:	Rapid To Rapid 0D
Plural:	Rapids To Rapid 0D
Description:	Rapid To Rapid 0D
Base Attribute:
Class Type Value:

4.43.2. From Rapid_0D To Rapid

Name:	Rapid_0D_to_Rapid
Screen Text:	Rapid 0D To Rapid
Plural:	Rapid 0D To Rapids
Description:	Rapid 0D To Rapid
Base Attribute:
Class Type Value:

4.44. Relationship Pair: Rapid (Rapid_to_Rapid_2D) and Rapid_2D (Rapid_2D_to_Rapid)

Rapid_2D is derived from Rapid.

4.44.1. From Rapid To Rapid_2D

Name:	Rapid_to_Rapid_2D
Screen Text:	Rapid To Rapid 2D
Plural:	Rapids To Rapid 2D
Description:	Rapid To Rapid 2D
Base Attribute:
Class Type Value:

4.44.2. From Rapid_2D To Rapid

Name:	Rapid_2D_to_Rapid
Screen Text:	Rapid 2D To Rapid
Plural:	Rapid 2D To Rapids
Description:	Rapid 2D To Rapid
Base Attribute:
Class Type Value:

4.45. Relationship Pair: Rapid_0D (Rapid_0D_to_Rapid) and Rapid (Rapid_to_Rapid_0D)

See Relationship Pair: Rapid (Rapid_to_Rapid_0D) and Rapid_0D (Rapid_0D_to_Rapid)}.

4.46. Relationship Pair: Rapid_2D (Rapid_2D_to_Rapid) and Rapid (Rapid_to_Rapid_2D)

See Relationship Pair: Rapid (Rapid_to_Rapid_2D) and Rapid_2D (Rapid_2D_to_Rapid)}.

4.47. Relationship Pair: Sea (Sea_to_Hyd_Clos) and Hyd_Close (Hyd_Clos_to_Sea)

See Relationship Pair: Hyd_Close (Hyd_Clos_to_Sea) and Sea (Sea_to_Hyd_Clos)}.

4.48. Relationship Pair: Sea (Sea_to_Sub_reef) and SubReef (Sub_reef_to_Sea)

Each record in Sea is related to zero or more records in SubReef. Each record in SubReef can be related to (optionally) one record in Sea. This relationship pair is represented spatially.

4.48.1. From Sea To SubReef

Name:	Sea_to_Sub_reef
Screen Text:	Sea To Sub Reef
Plural:	Seas To Sub Reef
Description:	Sea To Sub Reef

4.48.2. From SubReef To Sea

Name:	Sub_reef_to_Sea
Screen Text:	Sub Reef To Sea
Plural:	Sub Reef To Seas
Description:	Sub Reef To Sea

4.48.3. Spatial Representation

Class Sea is represented via area features. Class SubReef is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

No intersection between Sea and SubReef allowed.

4.49. Relationship Pair: Sea (Sea_to_Tdl_Line) and TLine (Tdl_Line_to_Sea)

Each record in Sea is related to one or more records in TLine. Each record in TLine can be related to (optionally) one record in Sea.

4.49.1. From Sea To TLine

Name:	Sea_to_Tdl_Line
Screen Text:	Sea To Tdl Line
Plural:	Seas To Tdl Line
Description:	Sea To Tdl Line
Primary Class:	Sea
Foreign Class:	TLine

4.49.2. From TLine To Sea

Name:	Tdl_Line_to_Sea
Screen Text:	Tdl Line To Sea
Plural:	Tdl Line To Seas
Description:	Tdl Line To Sea
Primary Class:	Sea
Foreign Class:	TLine

4.50. Relationship Pair: Spring (Spring_to_Land) and Land (Land_to_Spring)

See Relationship Pair: Land (Land_to_Spring) and Spring (Spring_to_Land)}.

4.51. Relationship Pair: SubReef (Sub_reef_to_Estuary) and Estuary (Estuary_to_Sub_reef)

See Relationship Pair: Estuary (Estuary_to_Sub_reef) and SubReef (Sub_reef_to_Estuary)}.

4.52. Relationship Pair: SubReef (Sub_reef_to_Sea) and Sea (Sea_to_Sub_reef)

See Relationship Pair: Sea (Sea_to_Sub_reef) and SubReef (Sub_reef_to_Sea)}.

4.53. Relationship Pair: SubTree (Submerged_trees_to_Water_body) and WBody (Water_body_to_Submerged_trees)

Each record in SubTree is always related to one (and only one) record in WBody. Each record in WBody is related to zero or more records in SubTree. This relationship pair is represented spatially.

4.53.1. From SubTree To WBody

Name:	Submerged_trees_to_Water_body
Screen Text:	Submerged Trees To Water Body
Plural:	Submerged Trees To Water Bodys
Description:	Submerged Trees To Water Body

4.53.2. From WBody To SubTree

Name:	Water_body_to_Submerged_trees
Screen Text:	Water Body To Submerged Trees
Plural:	Water Body To Submerged Treese
Description:	Water Body To Submerged Trees

4.53.3. Spatial Representation

Class SubTree is represented via area features. Class WBody is represented via area features. The features are related together via the following boundary/interior intersections:

Polygon-Polygon (2-2): The following "OR"-ed together:

Boundary of SubTree intersects with boundary and interior of WBody AND interior of SubTree intersects with interior of WBody.

4.54. Relationship Pair: TLine (tidal_lines_to_tidal_zones) and TZone (tidal_zones_to_tidal_lines)

Each record in TLine is related to zero or more records in TZone. Each record in TZone is related to one or more records in TLine. This relationship pair is represented spatially.

4.54.1. From TLine To TZone

Name:	tidal_lines_to_tidal_zones
Screen Text:	Tidal Lines To Tidal Zones
Plural:	Tidal Lines To Tidal Zoneses
Description:	Tidal Lines To Tidal Zones

4.54.2. From TZone To TLine

Name:	tidal_zones_to_tidal_lines
Screen Text:	Tidal Zones To Tidal Lines
Plural:	Tidal Zones To Tidal Lineses
Description:	Tidal Zones To Tidal Lines

4.54.3. Spatial Representation

Class TLine is represented via simple line features. Class TZone is represented via area features. The features are related together via the following boundary/interior intersections:

Line-Polygon (1-2): The following "OR"-ed together:

Interior of TLine intersects with boundary of TZone.

4.55. Relationship Pair: TLine (Tdl_Line_to_Sea) and Sea (Sea_to_Tdl_Line)

See Relationship Pair: Sea (Sea_to_Tdl_Line) and TLine (Tdl_Line_to_Sea)}.

4.56. Relationship Pair: TLine (Tdl_Line_to_Estuary) and Estuary (Estuary_to_Tdl_Line)

See Relationship Pair: Estuary (Estuary_to_Tdl_Line) and TLine (Tdl_Line_to_Estuary)}.

4.57. Relationship Pair: TLine (Tdl_Line_to_Land) and Land (Land_to_Tdl_Line)

See Relationship Pair: Land (Land_to_Tdl_Line) and TLine (Tdl_Line_to_Land)}.

4.58. Relationship Pair: TZone (Tidal_zone_to_Estuary) and Estuary (Estuary_to_Tidal_zone)

See Relationship Pair: Estuary (Estuary_to_Tidal_zone) and TZone (Tidal_zone_to_Estuary)}.

4.59. Relationship Pair: TZone (tidal_zones_to_tidal_lines) and TLine (tidal_lines_to_tidal_zones)

See Relationship Pair: TLine (tidal_lines_to_tidal_zones) and TZone (tidal_zones_to_tidal_lines)}.

4.60. Relationship Pair: WBody (Wtr_Body_to_Hyd_Clos) and Hyd_Close (Hyd_Clos_to_Wtr_Body)

See Relationship Pair: Hyd_Close (Hyd_Clos_to_Wtr_Body) and WBody (Wtr_Body_to_Hyd_Clos)}.

4.61. Relationship Pair: WBody (Wtr_Body_to_Hyd_Conn) and HydCntr (Hyd_Conn_to_Wtr_Body)

See Relationship Pair: HydCntr (Hyd_Conn_to_Wtr_Body) and WBody (Wtr_Body_to_Hyd_Conn)}.

4.62. Relationship Pair: WBody (Water_body_to_Dam) and Dam (Dam_to_Water_body)

See Relationship Pair: Dam (Dam_to_Water_body) and WBody (Water_body_to_Dam)}.

4.63. Relationship Pair: WBody (Water_body_to_Submerged_trees) and SubTree (Submerged_trees_to_Water_body)

See Relationship Pair: SubTree (Submerged_trees_to_Water_body) and WBody (Water_body_to_Submerged_trees)}.

4.64. Relationship Pair: WBody (water_bodies_to_water_lines) and WtrLine (water_lines_to_water_bodies)

Each record in WBody is related to one or more records in WtrLine. Each record in WtrLine can be related to (optionally) one record in WBody. This relationship pair is represented spatially.

4.64.1. From WBody To WtrLine

Name:	water_bodies_to_water_lines
Screen Text:	Water Bodies To Water Lines
Plural:	Water Bodies To Water Lineses
Description:	Water Bodies To Water Lines

4.64.2. From WtrLine To WBody

Name:	water_lines_to_water_bodies
Screen Text:	Water Lines To Water Bodies
Plural:	Water Lines To Water Bodieses
Description:	Water Lines To Water Bodies

4.64.3. Spatial Representation

Class WBody is represented via area features. Class WtrLine is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of WtrLine intersects with boundary and interior of WBody.

4.65. Relationship Pair: WBody (Waterbody_to_Land) and Land (Land_to_Waterbody)

See Relationship Pair: Land (Land_to_Waterbody) and WBody (Waterbody_to_Land)}.

4.66. Relationship Pair: Wcourse (Watercourse_to_Waterfall) and Wtrfall (Waterfall_to_Watercourse)

Each record in Wcourse is related to zero or more records in Wtrfall. Each record in Wtrfall is always related to one (and only one) record in Wcourse. This relationship pair is represented spatially.

4.66.1. From Wcourse To Wtrfall

Name:	Watercourse_to_Waterfall
Screen Text:	Watercourse To Waterfall
Plural:	Watercourses To Waterfall
Description:	Watercourse To Waterfall

4.66.2. From Wtrfall To Wcourse

Name:	Waterfall_to_Watercourse
Screen Text:	Waterfall To Watercourse
Plural:	Waterfalls To Watercourse
Description:	Waterfall To Watercourse

4.66.3. Spatial Representation

Class Wcourse is represented via simple line and area features. Class Wtrfall is represented via point and simple line features. The features are related together via the following boundary/interior intersections:

Line-Point (1-0): The following "OR"-ed together:

Boundary of Wtrfall intersects with boundary of Wcourse.

4.67. Relationship Pair: Wcourse (Watercourse_to_Rapid) and Rapid (Rapid_to_Watercourse)

See Relationship Pair: Rapid (Rapid_to_Watercourse) and Wcourse (Watercourse_to_Rapid)}.

4.68. Relationship Pair: Wcourse (Watercourse_to_Watercourse_1D) and Wcrse1D (Watercourse_1D_to_Watercourse)

Wcrse1D is derived from Wcourse. This relationship pair is represented spatially.

4.68.1. From Wcourse To Wcrse1D

Name:	Watercourse_to_Watercourse_1D
Screen Text:	Watercourse To Watercourse 1D
Plural:	Watercourses To Watercourse 1D
Description:	Watercourse To Watercourse 1D
Base Attribute:
Class Type Value:

4.68.2. From Wcrse1D To Wcourse

Name:	Watercourse_1D_to_Watercourse
Screen Text:	Watercourse 1D To Watercourse
Plural:	Watercourse 1D To Watercourses
Description:	Watercourse 1D To Watercourse
Base Attribute:
Class Type Value:

4.68.3. Spatial Representation

Class Wcourse is represented via simple line and area features. Class Wcrse1D is represented via simple line features. The features are related together via the following boundary/interior intersections:


Additionally, the following restrictions apply:


Between Wcourse and Wcrse1D: LA

4.69. Relationship Pair: Wcourse (Watercourse_to_Watercourse_2D) and Wcrse2D (Watercourse_2D_to_Watercourse)

Wcrse2D is derived from Wcourse. This relationship pair is represented spatially.

4.69.1. From Wcourse To Wcrse2D

Name:	Watercourse_to_Watercourse_2D
Screen Text:	Watercourse To Watercourse 2D
Plural:	Watercourses To Watercourse 2D
Description:	Watercourse To Watercourse 2D
Base Attribute:
Class Type Value:

4.69.2. From Wcrse2D To Wcourse

Name:	Watercourse_2D_to_Watercourse
Screen Text:	Watercourse 2D To Watercourse
Plural:	Watercourse 2D To Watercourses
Description:	Watercourse 2D To Watercourse
Base Attribute:
Class Type Value:

4.69.3. Spatial Representation

Class Wcourse is represented via simple line and area features. Class Wcrse2D is represented via area features. The features are related together via the following boundary/interior intersections:

4.70. Relationship Pair: Wcourse (Watercourse_to_Water_pipeline) and Art_Wc (Water_pipeline_to_Watercourse)

See Relationship Pair: Art_Wc (Water_pipeline_to_Watercourse) and Wcourse (Watercourse_to_Water_pipeline)}.

4.71. Relationship Pair: Wcourse (Wcourse_to_Land) and Land (Land_to_Wcourse)

See Relationship Pair: Land (Land_to_Wcourse) and Wcourse (Wcourse_to_Land)}.

4.72. Relationship Pair: Wcourse (Wcourse_to_Dam) and Dam (Dam_to_Wcourse)

See Relationship Pair: Dam (Dam_to_Wcourse) and Wcourse (Wcourse_to_Dam)}.

4.73. Relationship Pair: Wcrse1D (Watercourse_1D_to_Watercourse) and Wcourse (Watercourse_to_Watercourse_1D)

See Relationship Pair: Wcourse (Watercourse_to_Watercourse_1D) and Wcrse1D (Watercourse_1D_to_Watercourse)}.

4.74. Relationship Pair: Wcrse2D (Watercourse_2D_to_Watercourse) and Wcourse (Watercourse_to_Watercourse_2D)

See Relationship Pair: Wcourse (Watercourse_to_Watercourse_2D) and Wcrse2D (Watercourse_2D_to_Watercourse)}.

4.75. Relationship Pair: Wcrse2D (Wcourse2_to_Hyd_Conn) and HydCntr (Hyd_Conn_to_Wcourse2)

See Relationship Pair: HydCntr (Hyd_Conn_to_Wcourse2) and Wcrse2D (Wcourse2_to_Hyd_Conn)}.

4.76. Relationship Pair: Wcrse2D (watercourses_to_water_lines) and WtrLine (water_lines_to_watercourses)

Each record in Wcrse2D is related to one or more records in WtrLine. Each record in WtrLine can be related to (optionally) one record in Wcrse2D. This relationship pair is represented spatially.

4.76.1. From Wcrse2D To WtrLine

Name:	watercourses_to_water_lines
Screen Text:	Watercourses To Water Lines
Plural:	Watercourseses To Water Lines
Description:	Watercourses To Water Lines

4.76.2. From WtrLine To Wcrse2D

Name:	water_lines_to_watercourses
Screen Text:	Water Lines To Watercourses
Plural:	Water Lines To Watercourseses
Description:	Water Lines To Watercourses

4.76.3. Spatial Representation

Class Wcrse2D is represented via area features. Class WtrLine is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of WtrLine intersects with interior of Wcrse2D.

4.77. Relationship Pair: Wetland (Wetland_to_Land) and Land (Land_to_Wetland)

See Relationship Pair: Land (Land_to_Wetland) and Wetland (Wetland_to_Land)}.

4.78. Relationship Pair: Wetland (Wetland_to_Flood_plain) and Floodpl (Flood_plain_to_Wetland)

See Relationship Pair: Floodpl (Flood_plain_to_Wetland) and Wetland (Wetland_to_Flood_plain)}.

4.79. Relationship Pair: Wetland (wetlands_to_water_lines) and WtrLine (water_lines_to_wetlands)

Each record in Wetland is related to one or more records in WtrLine. Each record in WtrLine is related to zero or more records in Wetland. This relationship pair is represented spatially.

4.79.1. From Wetland To WtrLine

Name:	wetlands_to_water_lines
Screen Text:	Wetlands To Water Lines
Plural:	Wetlandses To Water Lines
Description:	Wetlands To Water Lines

4.79.2. From WtrLine To Wetland

Name:	water_lines_to_wetlands
Screen Text:	Water Lines To Wetlands
Plural:	Water Lines To Wetlandses
Description:	Water Lines To Wetlands

4.79.3. Spatial Representation

Class Wetland is represented via area features. Class WtrLine is represented via simple line features. The features are related together via the following boundary/interior intersections:

Polygon-Line (2-1): The following "OR"-ed together:

Boundary of WtrLine intersects with boundary of Wetland AND interior of WtrLine intersects with boundary of Wetland.

4.80. Relationship Pair: Wfall_0D (Wfall_0D_to_Wtrfall) and Wtrfall (Wtrfall_to_Wfall_0D)

Wfall_0D is derived from Wtrfall.

4.80.1. From Wfall_0D To Wtrfall

Name:	Wfall_0D_to_Wtrfall
Screen Text:	Wfall 0D To Wtrfall
Plural:	Wfall 0D To Wtrfalls
Description:	Wfall 0D To Wtrfall
Base Attribute:
Class Type Value:

4.80.2. From Wtrfall To Wfall_0D

Name:	Wtrfall_to_Wfall_0D
Screen Text:	Wtrfall To Wfall 0D
Plural:	Wtrfalls To Wfall 0D
Description:	Wtrfall To Wfall 0D
Base Attribute:
Class Type Value:

4.81. Relationship Pair: Wfall_1D (Wfall_1D_to_Wtrfall) and Wtrfall (Wtrfall_to_Wfall_1D)

Wfall_1D is derived from Wtrfall.

4.81.1. From Wfall_1D To Wtrfall

Name:	Wfall_1D_to_Wtrfall
Screen Text:	Wfall 1D To Wtrfall
Plural:	Wfall 1D To Wtrfalls
Description:	Wfall 1D To Wtrfall
Base Attribute:
Class Type Value:

4.81.2. From Wtrfall To Wfall_1D

Name:	Wtrfall_to_Wfall_1D
Screen Text:	Wtrfall To Wfall 1D
Plural:	Wtrfalls To Wfall 1D
Description:	Wtrfall To Wfall 1D
Base Attribute:
Class Type Value:

4.82. Relationship Pair: WtrLine (water_lines_to_wetlands) and Wetland (wetlands_to_water_lines)

See Relationship Pair: Wetland (wetlands_to_water_lines) and WtrLine (water_lines_to_wetlands)}.

4.83. Relationship Pair: WtrLine (water_lines_to_flat) and Flat (Flat_to_Water_lines)

See Relationship Pair: Flat (Flat_to_Water_lines) and WtrLine (water_lines_to_flat)}.

4.84. Relationship Pair: WtrLine (water_lines_to_flood_plains) and Floodpl (flood_plains_to_water_lines)

See Relationship Pair: Floodpl (flood_plains_to_water_lines) and WtrLine (water_lines_to_flood_plains)}.

4.85. Relationship Pair: WtrLine (water_lines_to_watercourses) and Wcrse2D (watercourses_to_water_lines)

See Relationship Pair: Wcrse2D (watercourses_to_water_lines) and WtrLine (water_lines_to_watercourses)}.

4.86. Relationship Pair: WtrLine (water_lines_to_water_bodies) and WBody (water_bodies_to_water_lines)

See Relationship Pair: WBody (water_bodies_to_water_lines) and WtrLine (water_lines_to_water_bodies)}.

4.87. Relationship Pair: WtrLine (Wtr_Line_to_Art_Wc_2D) and ArtWc2D (Art_Wc_2D_to_Wtr_Line)

See Relationship Pair: ArtWc2D (Art_Wc_2D_to_Wtr_Line) and WtrLine (Wtr_Line_to_Art_Wc_2D)}.

4.88. Relationship Pair: Wtrfall (Waterfall_to_Watercourse) and Wcourse (Watercourse_to_Waterfall)

See Relationship Pair: Wcourse (Watercourse_to_Waterfall) and Wtrfall (Waterfall_to_Watercourse)}.

4.89. Relationship Pair: Wtrfall (Wtrfall_to_Wfall_1D) and Wfall_1D (Wfall_1D_to_Wtrfall)

See Relationship Pair: Wfall_1D (Wfall_1D_to_Wtrfall) and Wtrfall (Wtrfall_to_Wfall_1D)}.

4.90. Relationship Pair: Wtrfall (Wtrfall_to_Wfall_0D) and Wfall_0D (Wfall_0D_to_Wtrfall)

See Relationship Pair: Wfall_0D (Wfall_0D_to_Wtrfall) and Wtrfall (Wtrfall_to_Wfall_0D)}.

5. Code Lists

Code lists are lists of legal values which you can in your programs to ensure that the user picks from a fixed list and which the system uses to define uniquely each subclass of a superclass.

The code lists are listed here with all the codes which make up each code list.

5.1. Code List: AdjFeat

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Water Body
2	Wcourse2d	Wcourse2d
3	Estuary
4	Sea
5	Artwc2d	Artwc2d

5.2. Code List: ArtWcTy

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Water tunnel	A channel formed underground.
2	Spillway	A way for excess water to flow from a dam.
3	Canal	A lined channel for diversion or irrigation, within the ground and more than 10 m wide.
4	Drain	An open channel for removing excess water, runoff or ground water.
5	Flume	A fabricated channel or trough, above ground but not elevated.
6	Water race	A ditch on a gentle gradient, usually associated with certain types of mining.
7	Water channel	A channel for diversion or irrigation, within the ground and less than 10 m wide.
8	Siphon	A pipeline crossing a valley or hill that uses differential atmospheric pressure to cause a flow.
9	Water pipeline	A pipeline other than a penstock or siphon.
10	Penstock	A steeply sloping pipeline leading to a water turbine.

5.3. Code List: AssmdWL

This list contains the following items:

Name	Screen Text	Description
0	Observed	Surface data has been observed.
1	Assumed	Surface data has been interpolated or extrapolated.

5.4. Code List: DamType

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Reservoir wall	Reservoir wall
2	Weir	Raises the level of a stream at times of low flow.
3	Sluice gate	A vertically sliding gate used to control the flow of water.

5.5. Code List: EstFeat

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Stream	That part of a stream between the limit of tidal influence and its mouth. [from ICSM]
2	Lagoon	An area of shallow brackish water that might occasionally be closed from the sea or a lower estuary.
3	Other	Estuaries that are not streams or lagoons.

5.6. Code List: FlatType

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Coastal Flat	An area above MHWM that is periodically flooded by higher than normal tides.
2	Salt Pan	A flat area, mainly salt, occasionally covered with water.

5.7. Code List: FloodDeg

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Severe flood	Frequency is much less than annual, the land might be cultivated, and certain other features may be excluded or included.
2	Moderate flood	Frequency is regular and seasonal, and the land is not cultivated.

5.8. Code List: FlowTy

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Permanent
2	Intermittent

5.9. Code List: HydConTy

This list contains the following items:

Name	Screen Text	Description
-1	No data is available.	No data is available.
1	Minimum flow 2D	The line of minimum permanent flow in a Watercourse 2D.
2	Intermittent flow 2D	A line where flow is intermittent in a Watercourse 2D.
3	Permanent flow 2D	A line where flow is permanent in a Watercourse 2D.
4	Other

5.10. Code List: ImpldWc

This list contains the following items:

Name	Screen Text	Description
-1	Unknown	No data is available.
1	Implied	An invisible or indistinct section of a watercourse.
2	Defined	Defined