Data Content and Structure¶
The Roads dataset is a feature-based product. A data model is included (Appendix A - Roads Data Model Diagram) with an associated data dictionary (Appendix B - Roads Data Dictionary).
Feature-Based Data¶
The feature type of a road is a spatial vector line. The table below outlines the features and their integration into related datasets.
Entity |
Description |
Integration |
|---|---|---|
Roads |
A real-world road will have one or more linear spatial representations within the Roads dataset. |
A road does not integrate with other Geoscape products. A road has the State or Territory abbreviation of the jurisdiction its linear geometry predominantly intersects. |
Street Locality Line |
A spatial representation of the relationship between Road features and Locality boundaries. The geometry of Street Locality Line is generated from Roads but may only partially correspond to a Roads record depending on its intersection with a Locality boundary. It is common for records with a null street_loc_pid to not have a matching record in the G-NAF street_locality table and these records are retained because they represent the Road segment’s relationship to a Locality. A Street Locality Line record can relate to one, many or zero G-NAF addresses. |
The table enables linkage to the street_locality table in the G-NAF product via the street_locality_pid attribute enabling linkage to G-NAF addresses. |
Feature-Based Application Schema (Data Model)¶
The Roads dataset Data Model Diagram is set out in Appendix A - Roads Data Model Diagram.
Data Dictionary¶
Feature-Based Feature Catalogue¶
The feature catalogue in support of the application schema is provided in Appendix B - Roads Data Dictionary. Spatial attributes are added to the feature catalogue in the same manner as other attributes for completeness and conformance to the application schema. Table 3 refers to all tables in the Feature Catalogue.
Feature-Based Content Scope¶
All geometry and metadata for lines within the Roads dataset.