NOMENCLATURE - Spatial Data Model - Specification

Contents

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

1. Overview

The NOMENCLATURE data model has the following characteristics:

Name:	NOMENCLATURE
Description:	A data model for nomenclature data in the LIST
Database Type:	ODBC
Unit of Measure:	meters

2. Class Diagram

3. Class Details

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

3.1. Class: Coords

This class is defined as follows:

Name:	Coords
Screen Text:	Coords
Plural:	Coordinates
Description:	Coordinates
Spatial:	No

It contains the following attributes:

3.1.1. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nom Reg No
Description:	nom reg no
Plural:	Nom Reg Nos
SQL Type:	varchar2(7)
Width:	7
Field Position (Width):	7
Key:	Yes
Mandatory:	Yes

3.1.2. Attribute: easting

Name:	easting
Screen Text:	Easting
Description:	The easting coordinate used as a general spatial identifier.
Plural:	Eastings
SQL Type:	numeric(6,0)
Width:	6
Field Position (Width):	6
Mandatory:	Yes

3.1.3. Attribute: northing

Name:	northing
Screen Text:	Northing
Description:	The northing coordinate used as a general spatial identifier.
Plural:	Northings
SQL Type:	numeric(7,0)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.2. Class: CurCLTy

This class is defined as follows:

Name:	CurCLTy
Screen Text:	CurCLTy
Plural:	Current Class Codes
Description:	Class Code
Spatial:	No

It contains the following attributes:

3.2.1. Attribute: cur_class

Name:	cur_class
Screen Text:	Current Class
Description:	current class
Plural:	Current Classes
SQL Type:	varchar2(1)
Width:	1
Field Position (y):	10
Field Position (Width):	1
Mandatory:	Yes

3.2.2. Attribute: scntext

Name:	scntext
Screen Text:	Screen Text
Description:	screen text
Plural:	Screen Texts
SQL Type:	varchar2(40)
Width:	40
Picture:	M21-DISP M21V M21E M21N
Field Position (y):	20
Field Position (Width):	40
Mandatory:	Yes

3.2.3. Attribute: descript

Name:	descript
Screen Text:	description
Description:	description
Plural:	Descriptions
SQL Type:	varchar2(200)
Width:	200
Field Position (y):	30
Field Position (Width):	200
Mandatory:	Yes

3.2.4. Attribute: class_id

Name:	class_id
Screen Text:	Class Id
Description:	class id
Plural:	Class Ids
SQL Type:	number(6,0)
Width:	6
Picture:	SEQ
Field Position (y):	40
Field Position (Width):	6
Key:	Yes
Mandatory:	Yes
Hidden:	Yes

3.3. Class: CurFeTy

This class is defined as follows:

Name:	CurFeTy
Screen Text:	CurFeTy
Plural:	Current Class Codes
Description:	Class Code
Spatial:	No

It contains the following attributes:

3.3.1. Attribute: cur_feat_c

Name:	cur_feat_c
Screen Text:	Current Feature Code
Description:	current feature code
Plural:	Current Feature Codes
SQL Type:	varchar2(4)
Width:	4
Field Position (y):	10
Field Position (Width):	4
Mandatory:	Yes

3.3.2. Attribute: scntext

Name:	scntext
Screen Text:	Screen Text
Description:	screen text
Plural:	Screen Texts
SQL Type:	varchar2(40)
Width:	40
Picture:	M21-DISP M21V M21E M21N
Field Position (y):	20
Field Position (Width):	40
Mandatory:	Yes

3.3.3. Attribute: descript

Name:	descript
Screen Text:	description
Description:	description
Plural:	Descriptions
SQL Type:	varchar2(200)
Width:	200
Field Position (y):	30
Field Position (Width):	200
Mandatory:	Yes

3.3.4. Attribute: feat_id

Name:	feat_id
Screen Text:	Feat Id
Description:	feat id
Plural:	Feat Ids
SQL Type:	number(6,0)
Width:	6
Picture:	SEQ
Field Position (y):	40
Field Position (Width):	6
Key:	Yes
Mandatory:	Yes
Hidden:	Yes

3.4. Class: Feat_Ext

This class is defined as follows:

Name:	Feat_Ext
Screen Text:	Named Feature Extent
Plural:	Named Feature Extents
Description:	The spatial extent of a Named Feature in terms of a bounding rectangle.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.4.1. Attribute: featext_id

Name:	featext_id
Screen Text:	Named Feature Extent ID
Description:	The unique identifier for a Named Feature Extent record.
Plural:	Named Feature Extent IDs
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 number in the Nomenclature database which relates to the named feature.
Plural:
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Mandatory:	Yes
Unique:	Yes

3.4.3. Attribute: ufi

Name:	ufi
Screen Text:	UFI
Description:	Unique Feature Identifier
Plural:	UFIs
SQL Type:	varchar(12)
Width:	12
Field Position (Width):	12
Mandatory:	Yes

3.4.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.4.5. Attribute: created_on

Name:	created_on
Screen Text:	Created On
Description:	Created On
Plural:	Created Ons
SQL Type:	date
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.4.6. Attribute: retired_on

Name:	retired_on
Screen Text:	Retired_On
Description:	Retired_On
Plural:	Retired_Ons
SQL Type:	date
Width:	8
Field Position (Width):	8

3.5. Class: List_cl

This class is defined as follows:

Name:	List_cl
Screen Text:	LIST Class Table
Plural:	LIST Class Tables
Description:	A table to relate a LIST Class to its respective LIST named feature group.
Spatial:	No

It contains the following attributes:

3.5.1. Attribute: scntext

Name:	scntext
Screen Text:	Screen Text
Description:	screen text
Plural:	Screen Texts
SQL Type:	varchar(40)
Width:	40
Picture:	M21-DISP M21V M21E M21N
Field Position (y):	20
Field Position (Width):	40
Mandatory:	Yes

3.5.2. Attribute: anzlic_id

Name:	anzlic_id
Screen Text:	ANZLIC ID
Description:	anzlic id
Plural:	ANZLIC IDs
SQL Type:	varchar(15)
Width:	15
Field Position (x):	1
Field Position (y):	1
Field Position (Width):	15
Mandatory:	Yes
Unique:	Yes

3.5.3. Attribute: title

Name:	title
Screen Text:	Title
Description:	Title of the dataset
Plural:	Titles
SQL Type:	varchar2(160)
Width:	160
Field Position (x):	1
Field Position (y):	2
Field Position (Width):	160
Mandatory:	Yes

3.5.4. Attribute: list_cl_id

Name:	list_cl_id
Screen Text:	List Class Id
Description:	A unique identifier for the attribute list_class which can represent a single or group of LIST data set(s).
Plural:	List Class Ids
SQL Type:	numeric(6,0)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.6. Class: Maps100

This class is defined as follows:

Name:	Maps100
Screen Text:	Maps100
Plural:	Maps100s
Description:	maps100
Spatial:	No

It contains the following attributes:

3.6.1. Attribute: map_no

Name:	map_no
Screen Text:	Map No
Description:	Map No
Plural:	Map Nos
SQL Type:	varchar2(10)
Width:	10
Field Position (Width):	10
Key:	Yes
Mandatory:	Yes

3.6.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nom Reg No
Description:	nom reg no
Plural:	Nom Reg Nos
SQL Type:	varchar2(7)
Width:	7
Field Position (Width):	7
Key:	Yes
Mandatory:	Yes

3.7. Class: Maps25

This class is defined as follows:

Name:	Maps25
Screen Text:	Maps25
Plural:	Maps25s
Description:	maps25
Spatial:	No

It contains the following attributes:

3.7.1. Attribute: map_no

Name:	map_no
Screen Text:	Map No
Description:	Map No
Plural:	Map Nos
SQL Type:	varchar2(10)
Width:	10
Field Position (Width):	10
Key:	Yes
Mandatory:	Yes

3.7.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nom Reg No
Description:	nom reg no
Plural:	Nom Reg Nos
SQL Type:	varchar2(7)
Width:	7
Field Position (Width):	7
Key:	Yes
Mandatory:	Yes

3.8. Class: Meeting

This class is defined as follows:

Name:	Meeting
Screen Text:	Meeting
Plural:	Meetings
Description:	meeting
Spatial:	No

It contains the following attributes:

3.8.1. Attribute: meeting_no

Name:	meeting_no
Screen Text:	Meeting No
Description:	meeting no
Plural:	Meeting Nos
SQL Type:	number(6,0)
Width:	6
Field Position (Width):	6
Key:	Yes
Mandatory:	Yes

3.8.2. Attribute: meet_date

Name:	meet_date
Screen Text:	Meeting Date
Description:	meeting date
Plural:	Meeting Dates
SQL Type:	date
Width:	10
Field Position (Width):	10

3.9. Class: Municipality

This class is defined as follows:

Name:	Municipality
Screen Text:	Municipality
Plural:	Municipalities
Description:	Municipality
Spatial:	No

It contains the following attributes:

3.9.1. Attribute: munic_code

Name:	munic_code
Screen Text:	Municipality Code
Description:	municipality code
Plural:	Municipality Codes
SQL Type:	varchar2(3)
Width:	3
Field Position (Width):	3
Key:	Yes
Mandatory:	Yes

3.9.2. Attribute: munic_name

Name:	munic_name
Screen Text:	Municipality
Description:	municipality
Plural:	Municipalities
SQL Type:	varchar2(30)
Width:	30
Picture:	M2MDISP M2MORD
Field Position (Width):	30
Mandatory:	Yes

3.9.3. Attribute: repl_date

Name:	repl_date
Screen Text:	Repl Date
Description:	repl date
Plural:	Repl Dates
SQL Type:	date
Width:	10
Field Position (Width):	10

3.10. Class: NameFeat

This class is defined as follows:

Name:	NameFeat
Screen Text:	Named Feature
Plural:	Named Features
Description:	Any feature in the LIST database which has a name associated with it.
Spatial:	No

It contains the following attributes:

3.10.1. Attribute: feat_name

Name:	feat_name
Screen Text:	Feature Name
Description:	The name given to a feature.
Plural:
SQL Type:	char(35)
Width:	35
Field Position (y):	10
Field Position (Width):	35
Mandatory:	Yes

3.10.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Register Number
Description:	The Register Number in the current Nomenclature database
Plural:	Register Numbers
SQL Type:	varchar2(7)
Width:	7
Picture:	SEQ
Field Position (y):	20
Field Position (Width):	7
Key:	Yes
Mandatory:	Yes

3.10.3. Attribute: entry_date

Name:	entry_date
Screen Text:	Entry Date
Description:	The date of entry into the Nomenclature database.
Plural:	Entry Dates
SQL Type:	date
Width:	12
Field Position (x):	110
Field Position (y):	20
Field Position (Width):	12

3.10.4. Attribute: status_id

Name:	status_id
Screen Text:	Status Label
Description:	status label id
Plural:	Status Label ids
SQL Type:	number(6,0)
Width:	6
Picture:	M21-PARENT
Foreign Relationship:	Status
Primary Attribute:	status_id
Field Position (y):	30
Field Position (Width):	6
Mandatory:	Yes

3.10.5. Attribute: class_id

Name:	class_id
Screen Text:	Class Code
Description:	Current Class id
Plural:	Current Class ids
SQL Type:	number(6,0)
Width:	6
Picture:	M21-PARENT
Foreign Relationship:	Current_Class
Primary Attribute:	class_id
Field Position (y):	40
Field Position (Width):	6

3.10.6. Attribute: feat_id

Name:	feat_id
Screen Text:	Feature Code
Description:	Current Feature Code ID
Plural:	Current Feature Code IDs
SQL Type:	number(6,0)
Width:	6
Picture:	M21-PARENT
Foreign Relationship:	current_feature
Primary Attribute:	feat_id
Field Position (y):	50
Field Position (Width):	6

3.10.7. Attribute: list_cl_id

Name:	list_cl_id
Screen Text:	List Class Id
Description:	A unique identifier for the attribute list_class which can represent a single or group of LIST data set(s).
Plural:	List Class Ids
SQL Type:	numeric(6,0)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.10.8. Attribute: nomfile_rf

Name:	nomfile_rf
Screen Text:	File Ref.
Description:	A reference number in the Nomenclature Board file system
Plural:	Nomenclature File Refs
SQL Type:	varchar2(10)
Width:	10
Field Position (x):	110
Field Position (y):	60
Field Position (Width):	10

3.10.9. Attribute: decn_no

Name:	decn_no
Screen Text:	Decision Number
Description:	A number defined when the feature name is gazetted.
Plural:	Decision Numbers
SQL Type:	number(9,0)
Width:	9
Field Position (y):	70
Field Position (Width):	9

3.10.10. Attribute: offic_date

Name:	offic_date
Screen Text:	Official Date
Description:	Records the date on which the entry receives official status.
Plural:	Official Dates
SQL Type:	date
Width:	12
Field Position (x):	110
Field Position (y):	70
Field Position (Width):	12

3.10.11. Attribute: meeting_no

Name:	meeting_no
Screen Text:	Meeting No
Description:	meeting no
Plural:	Meeting Nos
SQL Type:	number(6,0)
Width:	6
Foreign Relationship:	Meeting
Primary Attribute:	meeting_no
Field Position (y):	80
Field Position (Width):	6

3.10.12. Attribute: from_folio

Name:	from_folio
Screen Text:	From Folio
Description:	The number of the first folio in the file which makes reference to the feature.
Plural:	From Folios
SQL Type:	number(5,0)
Width:	6
Field Position (y):	100
Field Position (Width):	6

3.10.13. Attribute: to_folio

Name:	to_folio
Screen Text:	To Folio
Description:	The number of the last folio in the file which makes reference to the feature.
Plural:	To Folios
SQL Type:	number(5,0)
Width:	6
Field Position (x):	110
Field Position (y):	100
Field Position (Width):	6

3.10.14. Attribute: forwd_ref

Name:	forwd_ref
Screen Text:	Foward Reference
Description:	The Register number of the named feature which superseeded the current record.
Plural:	Foward References
SQL Type:	varchar2(7)
Width:	7
Field Position (y):	90
Field Position (Width):	7

3.10.15. Attribute: remarks

Name:	remarks
Screen Text:	Remarks
Description:	Any general comments about the entry.
Plural:	Remarks
SQL Type:	varchar2(2000)
Width:	2000
Picture:	MULTILINE5
Field Position (y):	140
Field Position (Width):	2000

3.10.16. Attribute: gaz_date

Name:	gaz_date
Screen Text:	Gazette Date
Description:	gazette date
Plural:	Gazette Dates
SQL Type:	date
Width:	10
Field Position (Width):	10
Hidden:	Yes

3.11. Class: NomenMunic

This class is defined as follows:

Name:	NomenMunic
Screen Text:	NomenMunic
Plural:	NomenMunics
Description:	nomenmunic
Spatial:	No

It contains the following attributes:

3.11.1. Attribute: munic_code

Name:	munic_code
Screen Text:	Municipality Code
Description:	municipality code
Plural:	Municipality Codes
SQL Type:	varchar2(3)
Width:	3
Foreign Relationship:	Municipality_Name
Primary Attribute:	munic_code
Field Position (Width):	3
Key:	Yes
Mandatory:	Yes

3.11.2. Attribute: nom_reg_no

Name:	nom_reg_no
Screen Text:	Nom Reg No
Description:	nom reg no
Plural:	Nom Reg Nos
SQL Type:	varchar2(7)
Width:	7
Foreign Relationship:	Feature
Primary Attribute:	nom_reg_no
Field Position (Width):	7
Key:	Yes
Mandatory:	Yes

3.12. Class: StatusTy

This class is defined as follows:

Name:	StatusTy
Screen Text:	StatusTy
Plural:	Status Labels
Description:	Status Label
Spatial:	No

It contains the following attributes:

3.12.1. Attribute: status_lbl

Name:	status_lbl
Screen Text:	Status Label
Description:	status label
Plural:	Status Labels
SQL Type:	varchar2(2)
Width:	2
Field Position (y):	10
Field Position (Width):	2
Mandatory:	Yes

3.12.2. Attribute: scntext

Name:	scntext
Screen Text:	Screen Text
Description:	screen text
Plural:	Screen Texts
SQL Type:	varchar2(40)
Width:	40
Picture:	M21-DISP M21V M21E M21N
Field Position (y):	20
Field Position (Width):	40
Mandatory:	Yes

3.12.3. Attribute: descript

Name:	descript
Screen Text:	Description
Description:	description
Plural:	Descriptions
SQL Type:	varchar2(200)
Width:	200
Field Position (y):	30
Field Position (Width):	200
Mandatory:	Yes

3.12.4. Attribute: status_id

Name:	status_id
Screen Text:	Status Id
Description:	status id
Plural:	Status Ids
SQL Type:	number(6,0)
Width:	6
Picture:	SEQ
Field Position (y):	40
Field Position (Width):	6
Key:	Yes
Mandatory:	Yes
Hidden:	Yes

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: Coords (Feature) and NameFeat (Coordinates)

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

4.1.1. From Coords To NameFeat

Name:	Feature
Screen Text:	Feature
Plural:	Features
Description:	feature
Primary Class:	NameFeat
Foreign Class:	Coords

4.1.2. From NameFeat To Coords

Name:	Coordinates
Screen Text:	Coordinates
Plural:	Coordinateses
Description:	coordinates
Primary Class:	NameFeat
Foreign Class:	Coords

4.2. Relationship Pair: CurCLTy (Features) and NameFeat (Current_Class)

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

4.2.1. From CurCLTy To NameFeat

Name:	Features
Screen Text:	Features
Plural:	M21-REL
Description:	features
Primary Class:	CurCLTy
Foreign Class:	NameFeat

4.2.2. From NameFeat To CurCLTy

Name:	Current_Class
Screen Text:	Current Class
Plural:	M21-REL
Description:	current class
Primary Class:	CurCLTy
Foreign Class:	NameFeat

4.3. Relationship Pair: CurFeTy (features) and NameFeat (current_feature)

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

4.3.1. From CurFeTy To NameFeat

Name:	features
Screen Text:	Feature
Plural:	M21-REL
Description:	feature
Primary Class:	CurFeTy
Foreign Class:	NameFeat

4.3.2. From NameFeat To CurFeTy

Name:	current_feature
Screen Text:	Current Features
Plural:	M21-REL
Description:	current features
Primary Class:	CurFeTy
Foreign Class:	NameFeat

4.4. Relationship Pair: Feat_Ext (Feat_ext_to_NameFeat) and NameFeat (NameFeat_to_Feat_Ext)

Each record in Feat_Ext is always related to one (and only one) record in NameFeat. Each record in NameFeat can be related to (optionally) one record in Feat_Ext.

4.4.1. From Feat_Ext To NameFeat

Name:	Feat_ext_to_NameFeat
Screen Text:	Feat Ext To NameFeat
Plural:	Feat Ext To NameFeats
Description:	Feat Ext To NameFeat
Primary Class:	NameFeat
Foreign Class:	Feat_Ext

4.4.2. From NameFeat To Feat_Ext

Name:	NameFeat_to_Feat_Ext
Screen Text:	NameFeat To Feat Ext
Plural:	NameFeats To Feat Ext
Description:	NameFeat To Feat Ext
Primary Class:	NameFeat
Foreign Class:	Feat_Ext

4.5. Relationship Pair: List_cl (List_cl_to_NameFeat) and NameFeat (NameFeat_to_List_cl)

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

4.5.1. From List_cl To NameFeat

Name:	List_cl_to_NameFeat
Screen Text:	List Cl To NameFeat
Plural:	List Cl To NameFeats
Description:	List Cl To NameFeat
Primary Class:	List_cl
Foreign Class:	NameFeat

4.5.2. From NameFeat To List_cl

Name:	NameFeat_to_List_cl
Screen Text:	NameFeat To List Cl
Plural:	NameFeats To List Cl
Description:	NameFeat To List Cl
Primary Class:	List_cl
Foreign Class:	NameFeat

4.6. Relationship Pair: Maps100 (Feature) and NameFeat (Map100s)

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

4.6.1. From Maps100 To NameFeat

Name:	Feature
Screen Text:	Feature
Plural:	Features
Description:	feature
Primary Class:	NameFeat
Foreign Class:	Maps100

4.6.2. From NameFeat To Maps100

Name:	Map100s
Screen Text:	Map100s
Plural:	Map100ses
Description:	map100s
Primary Class:	NameFeat
Foreign Class:	Maps100

4.7. Relationship Pair: Maps25 (Feature) and NameFeat (Map25s)

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

4.7.1. From Maps25 To NameFeat

Name:	Feature
Screen Text:	Feature
Plural:	Maps
Description:	feature
Primary Class:	NameFeat
Foreign Class:	Maps25

4.7.2. From NameFeat To Maps25

Name:	Map25s
Screen Text:	Maps
Plural:	Featureses
Description:	maps
Primary Class:	NameFeat
Foreign Class:	Maps25

4.8. Relationship Pair: Meeting (Features) and NameFeat (Meeting)

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

4.8.1. From Meeting To NameFeat

Name:	Features
Screen Text:	Features
Plural:	Featureses
Description:	features
Primary Class:	Meeting
Foreign Class:	NameFeat

4.8.2. From NameFeat To Meeting

Name:	Meeting
Screen Text:	Meeting
Plural:	Meetings
Description:	meeting
Primary Class:	Meeting
Foreign Class:	NameFeat

4.9. Relationship Pair: Municipality (munics) and NomenMunic (Municipality_Name)

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

4.9.1. From Municipality To NomenMunic

Name:	munics
Screen Text:	Municipality
Plural:	Municipalities
Description:	municipality
Primary Class:	Municipality
Foreign Class:	NomenMunic

4.9.2. From NomenMunic To Municipality

Name:	Municipality_Name
Screen Text:	Municipality Name
Plural:	M2M-2
Description:	municipality name
Primary Class:	Municipality
Foreign Class:	NomenMunic

4.10. Relationship Pair: NameFeat (Status) and StatusTy (Features)

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

4.10.1. From NameFeat To StatusTy

Name:	Status
Screen Text:	Status
Plural:	M21-REL
Description:	status
Primary Class:	StatusTy
Foreign Class:	NameFeat

4.10.2. From StatusTy To NameFeat

Name:	Features
Screen Text:	Features
Plural:	M21-REL
Description:	features
Primary Class:	StatusTy
Foreign Class:	NameFeat

4.11. Relationship Pair: NameFeat (Current_Class) and CurCLTy (Features)

See Relationship Pair: CurCLTy (Features) and NameFeat (Current_Class)}.

4.12. Relationship Pair: NameFeat (current_feature) and CurFeTy (features)

See Relationship Pair: CurFeTy (features) and NameFeat (current_feature)}.

4.13. Relationship Pair: NameFeat (Map25s) and Maps25 (Feature)

See Relationship Pair: Maps25 (Feature) and NameFeat (Map25s)}.

4.14. Relationship Pair: NameFeat (Map100s) and Maps100 (Feature)

See Relationship Pair: Maps100 (Feature) and NameFeat (Map100s)}.

4.15. Relationship Pair: NameFeat (Coordinates) and Coords (Feature)

See Relationship Pair: Coords (Feature) and NameFeat (Coordinates)}.

4.16. Relationship Pair: NameFeat (munics) and NomenMunic (Feature)

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

4.16.1. From NameFeat To NomenMunic

Name:	munics
Screen Text:	Municipalities
Plural:	M2M-1 LIST
Description:	municipalities
Primary Class:	NameFeat
Foreign Class:	NomenMunic

4.16.2. From NomenMunic To NameFeat

Name:	Feature
Screen Text:	Feature
Plural:	Features
Description:	feature
Primary Class:	NameFeat
Foreign Class:	NomenMunic

4.17. Relationship Pair: NameFeat (Meeting) and Meeting (Features)

See Relationship Pair: Meeting (Features) and NameFeat (Meeting)}.

4.18. Relationship Pair: NameFeat (NameFeat_to_Feat_Ext) and Feat_Ext (Feat_ext_to_NameFeat)

See Relationship Pair: Feat_Ext (Feat_ext_to_NameFeat) and NameFeat (NameFeat_to_Feat_Ext)}.

4.19. Relationship Pair: NameFeat (NameFeat_to_List_cl) and List_cl (List_cl_to_NameFeat)

See Relationship Pair: List_cl (List_cl_to_NameFeat) and NameFeat (NameFeat_to_List_cl)}.

4.20. Relationship Pair: NomenMunic (Feature) and NameFeat (munics)

See Relationship Pair: NameFeat (munics) and NomenMunic (Feature)}.

4.21. Relationship Pair: NomenMunic (Municipality_Name) and Municipality (munics)

See Relationship Pair: Municipality (munics) and NomenMunic (Municipality_Name)}.

4.22. Relationship Pair: StatusTy (Features) and NameFeat (Status)

See Relationship Pair: NameFeat (Status) and StatusTy (Features)}.

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.

6. Miscellaneous Information

The miscellaneous settings which are part of the data model currently refer only to system variables.

6.1. Defined System Variables

These are listed as follows:

Name	Setting
CUSTOM_QUERY_VIEW	FeatView.sql
SECURITY	Y