Page History
Provides a reference for NT Government (NTG) spatial data custodians to make their data available via the NTG Spatial Data Infrastructure (SDI), the framework for accessing spatial information across the NT government.
| Table of Contents |
|---|
AIM
...
The aim of this project is to improve the visibility, accessibility and usability of Spatial Datasets made available by the Northern Territory Government (NTG).
...
The components of the NTG SDI including the relationship of data custodians, dissemination databases, access mechanisms and end users are depicted in Figure 1: The Northern Territory Government Spatial Data Infrastructure (NTG SDI).
Figure 1: The Northern Territory Government Spatial Data Infrastructure (NTG SDI)
...
Figure 1 provides a representation of how data is accessed via the NTG SDI. It is up to the custodian whether data is maintained internally and published periodically to the dissemination ‘point of truth’, or alternatively if the dissemination point of truth is a read-only view of the source data.
data model should be described in here somwhere establish layer in dissemination database schema
For example, the cadastre dataset is maintained in the Digital Cadastre Database (DCDB) environment using a legacy application rich in business rules and based on older (CAD) technology. To provide external users with current cadastre information, DPI provide a read-only view of the data, refreshed nightly on the Oracle-based Spatial Database 1 (SDB1). All use of the cadastre other than maintenance operations are sourced from SDB1 to ensure currency and compliance to the metadata documentation. The mechanism for update using this model is very important and must be documented in the metadata. In contrast, the Administrative Boundaries dataset is maintained by DPI stored directly on SDB1 in a special authenticated schema, with a read-only view forming the dissemination point of truth. Either approach is acceptable, it is up to the custodian to decide which is more appropriate for each dataset.
...
Data Dictionary: Column descriptions
Column Name | Description |
zone_code | The zone code of the feature. Used for thematic styling. See the table below relating to the Zone Code descriptions. |
zone_text | The descriptive value of the planning zone of the feature. Used for labelling, identifying etc. |
Data Dictionary: Column ‘CODE’ attribute descriptions (note thematic hints are optional)
CODE value | Description | Recommended Colour | Recommended Colour Code |
A | Agriculture | Tan | 232,214,153 |
CV | Caravan Park | Raspberry | 201,123,158 |
CB | Central Business | Bright Aqua | 31,255,255 |
C | Commercial | Light Aqua | 140,217,231 |
CL | Community Living | Red | 189,57,53 |
CP | Community Purpose | Yellow | 255,233,87 |
All methods that assist in describing the data to enable a user to identify if a particular dataset is “fit for purpose” should be included in the data dictionary, if it is not already part of the essential metadata descriptors. This could include preferred layer name (e.g. how the dataset does / should appear in a viewing application) and thematic hints such as appropriate scale range and colours.
...