...
This theme includes the following feature classes:
*No longer recorded under Topographic schema. See Queensland Roads and Tracks/wiki/spaces/GEOSPDATA/pages/796950567.
Airport Areas
A polygon feature class displaying the extent of sections or zones within and around an airport, usually incorporating runways, aircraft maintenance and passenger facilities.
| Expand |
|---|
|
Airport Areas | A polygon feature class displaying the extent of sections or zones within and around an airport, usually incorporating runways, aircraft maintenance and passenger facilities. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | FUNCTION | No | Text | 30 | A description of the function of the airport. Options: Aerodrome Domestic Airport International Airport Regional Airport
| dm_airport_ function | NAME | Yes | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the feature source information that the location of the feature was obtained from. | | OPERATIONAL_STATUS | No | Text | 20 | The operational status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_aviation_ status | USAGE | No | Text | 20 | The description of the type of civil and/or military use of the feature. Options: Civil Civil - Military Military
| dm_aviation_ usage | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST _EDITED_DATE | No | Date | | Date of the last editing or revision to the feature *internal use only | | DIMENSION_M2 | No | Double | | The area of the feature measured in square metres GDA2020 | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Airport Runways and Taxiways | A polygon feature class displaying the extents of airport infrastructure that facilitate the movement of aircraft on the ground. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | dm_airport_ runway | NAME | Yes | Text | 100 | The name of the feature (if available) Is only populated for a runway feature The name should be that of the airport as named. The suffix of 'Airport' or 'Aerodrome' will be included in the name e.g., Cairns Airport | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the feature source information that the location of the feature was obtained from. | | OPERATIONAL_STATUS | No | Text | 20 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_aviation_ status | SURFACE | No | Text | 10 | A description of the landing surface. Options: | dm_aviation_ surface | USAGE | No | Text | 20 | The description of the type of civil and/or military use of the feature. Options: Civil Civil - Military Military
| dm_aviation_ usage | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | DIMENSION_M2 | No | Double | | The area of the feature measured in square metres GDA2020 | | UPPER_SCALE | Yes | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Air Traffic Control Towers | A point feature class displaying the location of air traffic control towers. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | No | Text | 100 | The name of the feature The name should be that of the airport as named. The suffix of 'Air Traffic Control Tower' will be included in the name e.g., Brisbane Air Traffic Control Tower | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the feature source information that the location of the feature was obtained from. | | USAGE | No | Text | 20 | The description of the type of civil and/or military use of the feature. Options: Civil Civil - Military Military | dm_aviation_ usage | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | UPPER_SCALE | Yes | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Busway Stations | A point feature class displaying the location of busway stations on a dedicated busway network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | No | Text | 100 | The name of the feature | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source map, or data where the name of the feature was obtained. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location of the feature was obtained from. | | FEATURE_DATE | No | Date | | The source imagery, map, or data that the spatial location of the feature was obtained from. | | BUSWAY_NAME | No | Text | 50 | The name of the busway that the busway station is located on e.g., Northern Busway | | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | Yes | Date | | Date of the last editing or revision to the feature *internal use only | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Green bridges | A polyline feature class displaying the location of bridges for green and or sustainable transportation options. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: Footbridge Bikeway Bridge Multi-use Bridge Other Bridge
| | NAME | Yes | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the feature source information that the location of the feature was obtained from. | | OPERATIONAL STATUS | No | Text | 20 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_road_bri_ status | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | Yes | Date | | Date of the last editing or revision to the feature *internal use only | | DIMENSION_M | No | Double | | The length of the feature measured in metres GDA2020 | | UPPER_SCALE | Yes | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | | SEGMENT_ID | Yes | Text | 20 | Corresponding id number for Queensland Roads and Tracks | |
|
...
| Expand |
|---|
|
Helipads | A point feature class displaying the location of a constructed or maintained area for helicopter take-off and landing. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | Yes | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location of the feature was obtained from. | | OPERATIONAL_STATUS | No | Text | 20 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_aviation_ status | USAGE | No | Text | 20 | The description of the type of civil and/or military use of the feature. Options: Civil Civil - Military Military
| dm_aviation_ usage | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Landing Grounds | A polygon feature class displaying the extent of uncertified aircraft landing grounds. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | Yes | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the feature source information that the location of the feature was obtained from. | | OPERATIONAL_STATUS | No | Text | 30 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_aviation_ status | SURFACE | No | Text | 10 | A description of the landing surface. Options: | dm_aviation_ surface | USAGE | No | Text | 20 | The description of the type of civil and/or military use of the feature. Options: Civil Civil - Military Military
| dm_aviation_ usage | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. If no name of the landing ground is available, type in the following in this field: landing ground | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Toll Points | A point feature class displaying the location of toll points on the Queensland road network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | No | Text | 100 | The name of the feature | | ATTRIBUTE_SOURCE | No | Text | 100 | The source map, or data where the name of the feature was obtained. | | ATTRIBUTE_DATE | No | Date | | Date of the source map, or data where the name of the feature was obtained. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location and shape of the feature was obtained from. | | RELATIONSHIP | No | Text | 12 | Relationship to ground level. Options: | dm_toll_ relationship | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Railways | A polyline feature class displaying the location of the Queensland railway network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | FUNCTION | No | Text | 30 | A description of the function of the feature. Options: | dm_railway_ function | ROUTE_NAME | Yes | Text | 100 | The name of the entire railway | | SECTION_NAME | Yes | Text | 100 | The name of individual sections of a railway | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location and shape of the feature was obtained from. | | OPERATIONAL_STATUS | No | Text | 20 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_railway_ status | GAUGE | No | Text | 20 | The width of tracks. Options: Light Narrow Narrow – Light Standard Standard – Narrow Other Railway Gauge Non Applicable
| dm_railway_ gauge | ELECTRIFIED | No | Text | 20 | Is the track electrified? Options: Electrified Non Electrified Non Applicable
| dm_railway_ electrified | CONSTRUCTION_TYPE | No | Text | 10 | Type of construction Options: Bridge Causeway Elevated Overpass Surface Tunnel
| dm_railway_ construction | USAGE | No | Text | 40 | A description of the major use the feature. Options: | dm_railway_ usage | RAILWAY_OWNER | Yes | Text | 50 | The name of the owner/maintainer of the railway. Most non-government railways will be labelled “Private” | | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | DIMENSION_M | No | Double | | The length of the feature measured in metres GDA2020 | | UPPER_SCALE | Yes | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Railway Bridges | A polyline feature class displaying the location of railway bridges and overpasses along the railway network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: Elevated Railway Railway Bridge Railway Causeway Railway Overpass
| dm_railway_ bridge | NAME | Yes | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location and shape of the feature was obtained from. | | OPERATIONAL_STATUS | No | Text | 20 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Proposed Under Construction
| dm_railway_ status | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (SeePersistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | DIMENSION_M | No | Double | | The length of the feature measured in metres GDA2020 | | UPPER_SCALE | Yes | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Railway Stations and Sidings | A point feature class displaying the location of railway stations and sidings on the Queensland railway network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | dm_railway_stn | NAME | Yes | Text | 100 | The name of the feature (if available) | | ALTERNATE_NAME | Yes | Text | 100 | An alternate name of the feature if available from the Queensland Place Names Database, otherwise left blank | | QLD_PNDB_ID | Yes | Long | | Queensland Place Names Database unique identifier | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | Other names of the feature if not recorded in the Queensland Place Names Database. May be commonly known by other names or have different spelling. Multiple names can be shown, separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location of the feature was obtained from. | | OPERATIONAL STATUS | No | Text | 20 | The operation status of the feature. Options: Abandoned Dismantled Operational Non Operational Under Construction Proposed
| dm_railway_ status | USAGE | No | Text | 40 | A description of the major use the railway stops. Options: | dm_railway_stn_ usage | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (SeePersistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Railway Tunnels | A polyline feature class displaying the location of railway tunnels on the Queensland railway network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | Yes | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location and shape of the feature was obtained from. | | OPERATIONAL STATUS | No | Text | 20 | The operation status of the station. Options: Abandoned Dismantled Operational Non Operational Under Construction Proposed
| dm_railway_ status | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *internal use only | | DIMENSION_M | No | Double | | The length of the feature measured in metres GDA2020 | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | |
|
...
| Expand |
|---|
|
Road Bridges and Overpasses | A polyline feature class displaying the location of road bridges and overpasses along the Queensland road network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: Elevated Road Road Bridge Road Causeway Road Overpass
| dm_road_ bridge | NAME | No | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location and shape of the feature was obtained from. | | OPERATIONAL STATUS | No | Text | 20 | The operation status of the station. Options: Abandoned Dismantled Operational Non-Operational Under Construction Proposed
| dm_road_bri_ status | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *Internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *Internal use only | | DIMENSION_M | No | Double | | The length of the feature measured in metres GDA2020 | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | | SEGMENT_ID | Yes | Text | 20 | Corresponding id number for Queensland Roads and Tracks | |
|
...
| Expand |
|---|
|
Road Tunnels | A polyline feature class displaying the location of road tunnels along the Queensland road network. | Column Name | Nulls | Format | Size | Description | Constraints | FEATURE_TYPE | No | Text | 50 | Unique feature type that identifies the type of feature. Options: | | NAME | No | Text | 100 | The name of the feature (if available) | | ATTRIBUTE_SOURCE | No | Text | 100 | If the feature is named, the attribute_source is the source imagery, map, or data from which the features name has been obtained. If the feature is not named, the attribute_source is the source imagery, map, or data used to define what the feature type is. | | ATTRIBUTE_DATE | No | Date | | Date of the source imagery, map, or data used for attributing the feature. | | ADDITIONAL_NAMES | Yes | Text | 100 | The feature may be commonly known by other names or have different spelling. Multiple additional names can be shown and separated by a comma. | | ADD_NAMES_SOURCE | Yes | Text | 100 | The source map or data that the additional names were obtained. Multiple sources can be shown, separated by a comma. If multiple sources are shown, the written sequence will be the same as the written sequence of the names themselves. | | FEATURE_SOURCE | No | Text | 100 | The source imagery, map, or data that the spatial location and shape of the of the feature was obtained from. | | FEATURE_DATE | No | Date | | Date of the source imagery, map, or data that the spatial location and shape of the feature was obtained from. | | OPERATIONAL STATUS | No | Text | 20 | The operation status of the station. Options: Abandoned Dismantled Operational Non-Operational Under Construction Proposed
| dm_road_bri_ status | PFI | No | Text | | A Persistent Feature Identifier (PFI) is generated for each feature at the point of creation in the database. The value of the PFI will stay with the feature through all changes to the feature (both spatial and non-spatial) until the feature is retired. (See Persistent and Unique Feature Identifiers) | | UFI | No | Text | | A Unique Feature Identifier (UFI) is generated for each new feature at the point of creation in the database (at this point the PFI and UFI will be the same). The value of the UFI will stay with the feature through all changes to the feature (both spatial and non-spatial) unless the feature is split into multiple other parts. If the feature is split, the separate parts will retain the original PFI but new UFI’s will be generated for the split parts. (See Persistent and Unique Feature Identifiers) | | CREATED_DATE* | No | Date | | The date the feature was originally captured and first loaded to the database *Internal use only | | LAST_EDITED_DATE* | No | Date | | Date of the last editing or revision to the feature *Internal use only | | DIMENSION_M | No | Double | | The length of the feature measured in metres GDA2020 | | UPPER_SCALE | No | Long | | The upper scale for which the feature should be considered suitable for digital display. | dm_upper_scale | TEXT_NOTE | Yes | Text | 50 | For mapping purposes. Additional annotation that can be shown on a map. | | ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) | | SEGMENT_ID | Yes | Text | 20 | Corresponding id number for Queensland Roads and Tracks | |
|
...
This data no longer falls under Queensland Topographic Dataset. For Information, please email gov-support@spatial-qld-support.atlassian.net about the Queensland Roads and Track (QRT) feature class.
Return to Data Themes