ZONED_LAND - Spatial Data Model - Specification

Contents

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

1. Overview

The ZONED_LAND data model has the following characteristics:

Name:	ZONED_LAND
Description:	A data model to accommodate the various classes and attributes for existing Tasmanian planning schemes.
Database Type:	ODBC
Unit of Measure:	meters

2. Class Diagram

3. Class Details

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

3.1. Class: Cat_Road

This class is defined as follows:

Name:	Cat_Road
Screen Text:	Road Category
Plural:	Road Categories
Description:	A public road which has special provisions under the Planning Scheme.
Spatial:	Yes
Feature Types:	l

It contains the following attributes:

3.1.1. Attribute: rd_cat_id

Name:	rd_cat_id
Screen Text:	Road Category ID
Description:	Road Category ID
Plural:	Road Category IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.1.2. Attribute: plansch_id

Name:	plansch_id
Screen Text:	Planning Scheme ID
Description:	The unique identifier for a Planning Scheme.
Plural:	Planning Scheme IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.1.3. Attribute: rd_cat

Name:	rd_cat
Screen Text:	Road Category
Description:	The public road category as assigned by the Department of Transport.
Plural:	Road Categorys
SQL Type:	smallint
Width:	6
Field Position (Width):	6
Mandatory:	Yes

3.1.4. Attribute: clause_ref

Name:	clause_ref
Screen Text:	Clause Reference
Description:	The Clause in the Planning Scheme to which the entity is related.
Plural:	Clause References
SQL Type:	varchar(8)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.1.5. Attribute: ufi

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

3.1.6. Attribute: dqp

Name:	dqp
Screen Text:	DQP
Description:	Data Quality Pointer
Plural:	Dqps
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.1.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.1.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.2. Class: P_Scheme

This class is defined as follows:

Name:	P_Scheme
Screen Text:	Planning Scheme
Plural:	Planning Schemes
Description:	The area covered by a particular Planning Scheme.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.2.1. Attribute: plansch_id

Name:	plansch_id
Screen Text:	Planning Scheme ID
Description:	The unique identifier for a Planning Scheme.
Plural:	Planning Scheme IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.2.2. Attribute: plansch_na

Name:	plansch_na
Screen Text:	Planning Scheme Name
Description:	The name of the Planning Scheme.
Plural:	Names
SQL Type:	varchar(50)
Width:	50
Field Position (Width):	50
Mandatory:	Yes

3.2.3. Attribute: ufi

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

3.2.4. Attribute: dqp

Name:	dqp
Screen Text:	DQP
Description:	Data Quality Pointer
Plural:	Dqps
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.2.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.2.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.3. Class: P_Zone

This class is defined as follows:

Name:	P_Zone
Screen Text:	Planning Zone
Plural:	Planning Zones
Description:	A zone applicable to a particular area.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.3.1. Attribute: planzone_id

Name:	planzone_id
Screen Text:	Planning Zone ID
Description:	The unique identifier for a Planning Zone area.
Plural:	Planning Zone IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.3.2. Attribute: plansch_id

Name:	plansch_id
Screen Text:	Planning Scheme ID
Description:	The unique identifier for a Planning Scheme.
Plural:	Planning Scheme IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.3.3. Attribute: plan_zone

Name:	plan_zone
Screen Text:	Planning Zone
Description:	The zone in a particular Planning Scheme into which an area has been zoned.
Plural:	Planning Zones
SQL Type:	smallint
Width:	6
Field Position (Width):	6
Mandatory:	Yes

3.3.4. Attribute: ufi

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

3.3.5. Attribute: dqp

Name:	dqp
Screen Text:	DQP
Description:	Data Quality Pointer
Plural:	Dqps
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.3.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.3.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.4. Class: Spc_Area

This class is defined as follows:

Name:	Spc_Area
Screen Text:	Special Area
Plural:	Special Areas
Description:	An area which has special provisions under a particular Clause in a Planning Scheme.
Spatial:	Yes
Feature Types:	a

It contains the following attributes:

3.4.1. Attribute: special_id

Name:	special_id
Screen Text:	Special Area ID
Description:	The unique identifier for a Special Area.
Plural:	Special Area IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.4.2. Attribute: plansch_id

Name:	plansch_id
Screen Text:	Planning Scheme ID
Description:	The unique identifier for a Planning Scheme.
Plural:	Planning Scheme IDs
SQL Type:	integer
Width:	11
Field Position (Width):	11
Mandatory:	Yes

3.4.3. Attribute: clause_ref

Name:	clause_ref
Screen Text:	Clause Reference
Description:	The Clause in the Planning Scheme to which the entity is related.
Plural:	Clause References
SQL Type:	varchar(8)
Width:	8
Field Position (Width):	8
Mandatory:	Yes

3.4.4. Attribute: special_ty

Name:	special_ty
Screen Text:	Special Area Type
Description:	The type of Special Area.
Plural:	Special Area Types
SQL Type:	smallint
Width:	6
Code List:	SpecArea
Field Position (Width):	6
Mandatory:	Yes

3.4.5. Attribute: extent

Name:	extent
Screen Text:	Extent
Description:	Extent if applicable to the type of Special area.
Plural:	Extents
SQL Type:	varchar(8)
Width:	8
Field Position (Width):	8

3.4.6. Attribute: ufi

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

3.4.7. Attribute: dqp

Name:	dqp
Screen Text:	DQP
Description:	Data Quality Pointer
Plural:	Dqps
SQL Type:	varchar(7)
Width:	7
Field Position (Width):	7
Mandatory:	Yes

3.4.8. 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.9. 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: Cat_Road (Road_category_to_Scheme) and P_Scheme (Scheme_to_Road_category)

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

4.1.1. From Cat_Road To P_Scheme

Name:	Road_category_to_Scheme
Screen Text:	Road Category To Scheme
Plural:	Road Category To Scheme
Description:	Road Category To Scheme

4.1.2. From P_Scheme To Cat_Road

Name:	Scheme_to_Road_category
Screen Text:	Scheme To Road Category
Plural:	Scheme To Road Catego
Description:	Scheme To Road Category

4.1.3. Spatial Representation

Class Cat_Road is represented via simple line features. Class P_Scheme 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 and interior of Cat_Road intersects with boundary and interior of P_Scheme.

4.2. Relationship Pair: P_Scheme (Planning_scheme_to_Zone) and P_Zone (Zone_to_Planning_scheme)

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

4.2.1. From P_Scheme To P_Zone

Name:	Planning_scheme_to_Zone
Screen Text:	Planning Scheme To Zone
Plural:	Planning Scheme To Zones
Description:	Planning Scheme To Zone

4.2.2. From P_Zone To P_Scheme

Name:	Zone_to_Planning_scheme
Screen Text:	Zone To Planning Scheme
Plural:	Zones To Planning Scheme
Description:	Zone To Planning Scheme

4.2.3. Spatial Representation

Class P_Scheme is represented via area features. Class P_Zone 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 P_Scheme intersects with boundary of P_Zone AND interior of P_Scheme intersects with interior and boundary of P_Zone.

4.3. Relationship Pair: P_Scheme (Scheme_to_Special_area) and Spc_Area (Special_area_to_Scheme)

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

4.3.1. From P_Scheme To Spc_Area

Name:	Scheme_to_Special_area
Screen Text:	Scheme To Special Area
Plural:	Scheme To Special Are
Description:	Scheme To Special Area

4.3.2. From Spc_Area To P_Scheme

Name:	Special_area_to_Scheme
Screen Text:	Special Area To Scheme
Plural:	Special Area To Schem
Description:	Special Area To Scheme

4.3.3. Spatial Representation

Class P_Scheme is represented via area features. Class Spc_Area 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 P_Scheme intersects with boundary of Spc_Area AND interior of P_Scheme intersects with interior and boundary of Spc_Area.

4.4. Relationship Pair: P_Scheme (Scheme_to_Road_category) and Cat_Road (Road_category_to_Scheme)

See Relationship Pair: Cat_Road (Road_category_to_Scheme) and P_Scheme (Scheme_to_Road_category)}.

4.5. Relationship Pair: P_Zone (Zone_to_Planning_scheme) and P_Scheme (Planning_scheme_to_Zone)

See Relationship Pair: P_Scheme (Planning_scheme_to_Zone) and P_Zone (Zone_to_Planning_scheme)}.

4.6. Relationship Pair: Spc_Area (Special_area_to_Scheme) and P_Scheme (Scheme_to_Special_area)

See Relationship Pair: P_Scheme (Scheme_to_Special_area) and Spc_Area (Special_area_to_Scheme)}.

4.7. Relationship Pair: Spc_Area (Special_area_overlaps) and Spc_Area (Special_area_overlaps)

See Relationship Pair: Spc_Area (Special_area_overlaps) and Spc_Area (Special_area_overlaps)}.

4.8. Relationship Pair: Spc_Area (Special_area_overlaps) and Spc_Area (Special_area_overlaps)

See Relationship Pair: Spc_Area (Special_area_overlaps) and Spc_Area (Special_area_overlaps)}.

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: SpecArea

This list contains the following items:

Name	Screen Text	Description
1	Attenuation Area	An area in which certain polution conditions apply.
2	Precinct	An area in which special provisions such as lot size or building density apply.
3	Potential Impact Area	An area in which there is potential for impact by another use.
4	Domestic Water Supply Areas	Domestic Water Supply Areas
5	Special Areas	Special Areasfor purposes other than those otherwise specified.
6	Flood Plain Areas	Flood Plain Areas
7	Scenic Corridors	Scenic Corridors
8	Historic Protection Areas	Historic Protection Areas

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