Feature Type Name
Scree boundary
Synonyms
Definition
The boundary of the scree.
Comments
Table Name
SCREE_BOUNDARY
Australia's Implementation Table Names
- SCREE_BOUNDARY_SC_LN
- SCREE_BOUNDARY_LN
None entered in defining this feature type
The following have been used in categorising this feature type
| Code |
Name |
Definition |
|
Data type |
Values |
UoM |
Used by these Feature Types |
| 1029 |
Certainty |
Undoubted fact |
Optional |
character(50) |
| label |
Definition |
| Approximate |
In the data capture process the feature was evident but its location was not entirely clear |
| Connector |
A line that is introduced for data completeness, e.g. a line used to close polygons, to represent missing data or data that is not visible. |
| Definite |
High level of confidence that the feature is correctly located. |
| Inferred |
In the data capture process the feature was not evident but the location of the feature was inferred |
| Interpolated |
The location of the feature was determined by interpolation |
| Unknown |
|
|
|
Types
|
| 1042 |
Dataset_Id |
An unique identifier of the dataset the feature belongs to |
Mandatory |
number(4) |
|
|
Types
|
| 1045 |
Date_Capture |
The date the feature was captured |
Optional |
date |
|
|
Types
|
| 1249 |
Date_Flag |
The type of date been stored, i.e.whether the date is approximate or definite, and for which component of the date is approximate or definite. Also includes seasons |
Optional |
character(50) |
| label |
Definition |
| Appoximate day in a known month and year |
|
| Approximate month in a known year |
The entry must be a full date, e.g. 1/1/2002, but only the month and year are valid. |
| Approximate season of a known year |
The season must be an Antarctic summer, autumn, winter or spring season. Enter season date with the approximate date of the middle of the season. Eg for spring 2002, enter as 15/10/2002. |
| Approximate year |
The entry must be a full date, e.g. 1/1/2002, but only the year is valid. |
| Definite day, month and year |
|
| Definite month and year |
The entry must be a full date, e.g. 1/1/2002, but only the month and year are valid. |
| Definite season and year |
The season must be an Antarctic summer, autumn, winter or spring season. Enter season date with the approximate date of the middle of the season. Eg for spring 2002, enter as 15/10/2002. |
| Definite year |
The entry must be a full date, e.g. 1/1/2002, but only the year is valid. |
| Pre year |
The entry must be a full date, e.g. 1/1/2002, but only the year is valid. The data was sourced before the year listed. |
| Unknown |
Value indicating that an attribute is not applicable or that it is impossible to determine |
|
|
Types
|
| 1297 |
Feat_left |
The feature type to the left of the feature mapped. It is assumed that the features mapped are mapped in a clockwise direction.
This ensures that the left polygon values common to more than one dataset are maintained between each dataset and that the arcs
common to more than one dataset maintained the same direction between each dataset. |
Optional |
character(50) |
|
|
Types
|
| 1298 |
Feat_right |
The feature type to the right of the feature mapped. It is assumed that the features mapped are mapped in a clockwise direction.
This ensures that the right polygon values common to more than one dataset are maintained between each dataset and that the arcs
common to more than one dataset maintained the same direction between each dataset. |
Optional |
character(50) |
|
|
Types
|
| 1150 |
Q_Info |
An unique identifier pointing to additional data quality information not included in the metadata record. |
Mandatory |
number(5) |
|
|
Types
|