- Created by Cathie Campbell , last modified by Daisey Brothers on 21, Oct, 2024
You are viewing an old version of this page. View the current version.
Compare with Current View Version History
« Previous Version 21 Next »
Transport networks, also known as transportation or transit networks, are interconnected systems that facilitate the movement of people, goods, and information within and between different geographical locations. Identifies the routes, infrastructure and zones of rail, air, and environmentally friendly transport options. The majority of features under this data theme for the Queensland Digital Topographic data are considered Transport infrastructure.
This theme includes the following feature classes:
Railway and Sidings
Railway Tunnels
Road Bridges and Overpasses
Road Tunnels
Queensland Road and Tracks*
*No longer recorded under Topographic schema. See Queensland Roads and Tracks.
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.
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: Airport Area
|
|
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) |
|
Feature Types:
Airport Area – The area set aside for use as a licenced, certified or registered facility by the Civil Aviation Safety Authority, usually equipped with runways, taxiways and aircraft maintenance and passenger facilities.
Aerodrome – An area of land or water, the use of which as an aerodrome is authorised under the regulations, intended to be used wholly or partly for the arrival, departure, or movement of aircraft. (including any buildings, installations, and equipment).
Domestic Airport – An airport that provides access to intrastate and interstate flights (no custom or immigration facilities available)
International Airport – Designated as an airport of entry and departure for international air traffic where customs, immigration, public health, animal, and plant quarantine checks are carried out. Also, can receive scheduled domestic and regional airline traffic.
Regional Airport - All non-principal state airports including rural and remote airports, they provide limited scheduled flights. (no custom or immigration facilities available)
Civil – Primarily used by civilian aircraft
Civil_Military – Used by both civilian and military aircraft on a regular basis
Military – Restricted to military use only *not often mapped due to restrictions.
Individual features may not agree with the following specifications to improve mapping legibility.
1:100 000 – < 250,000 m²
1:250 000 – >/= 250,000 m² and < 1,000,000 m²
1:1 000 000 – >/= 1,000,000 m²
AERODROME
Definition: An area of land or water, the use of which as an aerodrome is authorised under the regulations, intended to be used wholly or partly for the arrival, departure, or movement of aircraft. (including any buildings, installations, and equipment).
Alternate Terms: Military installation
|
· Capture as a 2D polygon · If appropriate, the cadastre is used to delineate the extent of the feature, including facilities and associated grounds · If the cadastre does not represent the maintained or used area of the feature, the extent can be plotted from orthorectified imagery (the extent may follow fence lines, maintained area or in combination with the cadastre) · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
DOMESTIC AIRPORT
Definition: An airport that provides access to intrastate and interstate flights (no custom or immigration facilities available).
Alternate Terms:
|
· Capture as a 2D polygon · If appropriate, the cadastre is used to delineate the extent of the feature, including facilities and associated grounds · If the cadastre does not represent the maintained or used area of the feature, the extent can be plotted from orthorectified imagery (the extent may follow fence lines, maintained area or in combination with the cadastre) · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
INTERNATIONAL AIRPORT
Definition: Designated as an airport of entry and departure for international air traffic where customs, immigration, public health, animal, and plant quarantine checks are carried out. Also, can receive scheduled domestic and regional airline traffic.
Alternate Terms:
|
· Capture as a 2D polygon · If appropriate, the cadastre is used to delineate the extent of the feature, including facilities and associated grounds · If the cadastre does not represent the maintained or used area of the feature, the extent can be plotted from orthorectified imagery (the extent may follow fence lines, maintained area or in combination with the cadastre) · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material. |
REGIONAL AIRPORT
Definition: All non-principal state airports including rural and remote airports, they provide limited scheduled flights. (no custom or immigration facilities available)
Alternate Terms:
|
· Capture as a 2D polygon · If appropriate, the cadastre is used to delineate the extent of the feature, including facilities and associated grounds · If the cadastre does not represent the maintained or used area of the feature, the extent can be plotted from orthorectified imagery (the extent may follow fence lines, maintained area or in combination with the cadastre) · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
Airport Runways and Taxiways
A polygon feature class displaying the extents of airport infrastructure that facilitate the movement of aircraft on the ground.
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: Apron Runway Taxiway
| 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: Grass Gravel Sealed
| 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) |
|
Apron – The defined area of an airport or aerodrome where aircraft are parked, loaded, unloaded, refuelled, boarded, or maintained.
Runway – The defined area of an airport or aerodrome (a straight path) used by aircraft for landing and take-off.
Taxiway – The defined area of an airport or aerodrome connecting runways to the aprons and the terminals.
Civil – Primarily used by civilian aircraft
Civil_Military – Used by both civilian and military aircraft on a regular basis
Military – Restricted to military use only. *not often mapped due to restrictions.
Individual features may not agree with the following specifications to improve mapping legibility.
1:100 000 – all Aprons/Taxiways and abandoned Runways
1:250 000 – all Runways except abandoned Runways
APRON
Definition: The defined area of an airport or aerodrome where aircraft are parked, loaded, unloaded, refuelled, boarded, or maintained.
Alternate Terms:
|
· Capture the marked apron area as a 2D polygon · The marked apron is plotted from orthorectified imagery · The surfaced area outside of the marked apron is not included · If the apron is not marked, the extent is shown as the edge of bitumen or concrete · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
RUNWAY
Definition: The defined area of an airport or aerodrome (a straight path) used by aircraft for landing and take-off.
Alternate Terms:
|
· Capture the marked runway area as a 2D polygon · The marked runway area is plotted from orthorectified imagery · The surfaced area outside of the marked runway area is not included · If the runway area is not marked, the extent is shown as the edge of bitumen or concrete · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
TAXIWAY
Definition: The defined area of an airport or aerodrome connecting runways to the aprons and the terminals.
Alternate Terms:
|
· Capture the marked taxiway area as a 2D polygon · The marked taxiway area is plotted from orthorectified imagery · The surfaced area outside of the marked taxiway area is not included · If the taxiway area is not marked, the extent is shown as the edge of bitumen, concrete, gravel, or grass · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
Air Traffic Control Towers
A point feature class displaying the location of air traffic control towers.
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: Air Traffic Control Tower
|
|
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) |
|
Air Traffic Control Tower – A structure that houses the personnel and equipment used to direct and control the flow of air traffic in a specified airspace.
Civil – Primarily used by civilian aircraft
Civil_Military – Used by both civilian and military aircraft on a regular basis
Military – Restricted to military use only*not often mapped due to restrictions.
Upper_scale:
1:100 000 – all data
AIR TRAFFIC CONTROL TOWER
Definition: A structure that houses the personnel and equipment used to direct and control the flow of air traffic in a specified airspace.
Alternate Terms: Control Tower
|
· Capture as a 2D point at the base of the feature · The location is plotted from orthorectified imagery · Location can be obtained from AirServices Australia · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material. · Reference with “Airport Areas” feature class data set
|
Busway Stations
A point feature class displaying the location of busway stations on a dedicated busway network.
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: Busway Station
|
|
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) |
|
Busway Station – A facility which is regularly used for loading and unloading of passengers onto buses on a designated network.
1:100 000 – all data
Capture Process:
1:100 000 – all data
Capture Process:
Green Bridges
A polyline feature class displaying the location of bridges for green and or sustainable transportation options.
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 |
|
Foot Bridge – A structure erected over a depression or obstacle to carry pedestrian traffic only.
Bikeway Bridge – A structure erected over a depression or obstacle to carry bicycle traffic only.
Multi-use Bridge – A structure erected over a depression or obstacle to carry multi forms of traffic.
Other Bridge – Any bridge not covered by the above.
FOOTBRIDGE
Definition: A structure erected over a depression or obstacle to carry pedestrian traffic
Alternate Terms: Pedestrian overpass
|
· Capture as a 2D polyline along the centre of the feature · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material. · Capture features with a length greater than 25 metres · End points to coincide with the vertex of any pathway feature. · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres
|
BIKEWAY BRIDGE
Definition: A structure erected over a depression or obstacle to carry bicycle traffic
Alternate Terms: Bikeway overpass, Cycleway bridge, Cycleway overpass
|
· Capture as a 2D polyline along the centre of the feature · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material. · Capture features with a length greater than 25 metres · End points to coincide with the vertex of any pathway feature. · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres
|
MULTI-USE BRIDGE
Definition: A structure erected over a depression or obstacle to carry multi forms of traffic
Alternate Terms: mixed use bridge, mixed use overpass
|
· Capture as a 2D polyline along the centre of the feature · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material. · Capture features with a length greater than 25 metres · End points to coincide with the vertex of any pathway feature. · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres
|
Helipads
A point feature class displaying the location of a constructed or maintained area for helicopter take-off and landing
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: Helipad
|
|
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. If the feature has no name. In this field, type in lower case the following: helipad
|
|
ADD_INFORMATION | Yes | Text | 255 | A comment field (additional information) |
|
Helipad – A constructed and maintained area for helicopter take-off and landing.
Civil – Primarily used by civilian aircraft
Civil_Military – Used by both civilian and military aircraft on a regular basis
Military – Restricted to military use only *not often mapped due to restrictions.
1:25 000 – all data
HELIPAD
Definition: A constructed and maintained area for helicopter take-off and landing.
Alternate Terms: Heliport
|
· Capture as a 2D point at the centre of the feature. · The location is plotted from orthorectified imagery · Information can be obtained from QldSpatial, Transport features Heliports and Landing Grounds – Qld download. · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
Landing Grounds
A polygon feature class displaying the extent of uncertified aircraft landing grounds.
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: Landing Ground
|
|
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: Grass Gravel Sealed
| 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) |
|
Landing Ground – An area of flat land used by small aircraft for landing and take-off and having only rudimentary facilities or none. (Uncertified Aerodrome)
Civil – Primarily used by civilian aircraft
Civil_Military – Used by both civilian and military aircraft on a regular basis
Military – Restricted to military use only. *not often mapped due to restrictions.
1:250 000 – all data
LANDING GROUND
Definition: An area of flat land used by small aircraft for landing and take-off and having only rudimentary facilities or none. (Uncertified Aerodrome)
Alternate Terms: Aircraft Landing Area, Airstrip, Landing Area
|
· Capture as a 2D polygon · If under 20 metre wide, capture 10 metres either side of the landing strip centreline · The location is plotted from orthorectified imagery · If the feature is less than 500 metres, exaggerate the length to a minimum of 500 metres · Locations can be obtained from QldSpatial, Transport features Heliports and Landing Grounds – Qld download. · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
Toll Points
A point feature class displaying the location of toll points on the Queensland road network.
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: Toll Point
|
|
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: Surface Underground
| 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) |
|
Toll Point – A location at which a fee is collected for use of the toll road.
1:25 000 – all data
TOLL POINT
Definition: A location at which a fee is collected for use of the toll road.
Alternate Terms: Toll booth, Tollgate
|
· Capture as a 2D point at the centre of the feature co-incident with the centreline of the road · The location is plotted from orthorectified imagery · If the feature is underground, determine the location from other available resources · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
Railways
A polyline feature class displaying the location of the Queensland railway network.
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: Railway
|
|
FUNCTION | No | Text | 30 |
A description of the function of the feature. Options: Light Rail Monorail Railway Railway Siding Sugar Cane Railway Tourist – Historic Railway Other Railway
| 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: Freight Freight - Passenger Mining Mining – Freight Mining – Freight - Passenger Passenger Rail Freight Facility Rail Siding Rail Yard Railway Workshop Stabling Yard Sugar Cane Tourist – Historic Railway Other Railway Usage Non Applicable
| 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) |
|
Feature Types:
Light Rail – A form of passenger urban rail transit characterized by a combination of tram and metro features. While its rolling stock is more like a traditional tram, it operates at a higher capacity and speed, and often on an exclusive right-of-way
Monorail – An elevated railway running on a single line and generally used for tourist purposes
Railway – A transportation system using one or more rails to carry freight, passengers or mining products.
Railway Siding – A short section or sections of track by the side of a railway used for shunting as well as for loading and unloading of freight.
Sugar Cane Railway – A railway built specifically to carry small trains carrying sugar cane from the cane fields to the sugar mills for processing
Tourist – Historic Railway – A railway that has been built specifically for the use of tourist or one that has been preserved for historical purposes.
Other Railway – Any railway not covered by the above.
Light – 610 mm wide
Narrow – 1067 mm wide
Standard – 1435 mm
Narrow – Light (Dual tracks running parallel with one rail in common)
Standard – Narrow (Dual tracks running parallel with one rail in common)
Other Railway Gauge – Any railway gauge not covered by the above
Bridge – The feature utilises a bridge
Causeway – The feature utilises a causeway
Elevated – The feature is elevated off the ground
Overpass – The feature utilises an overpass
Surface – The feature is located on the ground
Tunnel – The feature is a tunnel through the ground
Freight – The feature is used to in the transportation of goods in bulk for commercial purposes.
Freight – Passenger – The feature is used in the transportation of goods and passengers.
Mining – The feature is used for the transportation of mining by-products
Mining – Freight – The feature is for the transportation of goods mining by-products and goods.
Mining – Freight – Passenger – The feature is for the transportation of mining by-products, goods, and passengers.
Passenger – The feature is used for the transportation of passengers.
Rail Freight Facility –The feature is used as part of the intermodal freight terminal,
Rail Siding –The feature is used for shunting and loading and unloading of freight.
Rail Yard – The feature is used for storing, sorting, or loading/unloading, railroad cars and/or locomotives.
Railway Workshop – The feature is used in the maintenance or repairing of railroad cars, locomotives or rolling stock.
Stabling Yard – The feature is used to store or park passenger trains when not in use.
Sugar Cane – The feature is used specifically in the transportation of sugar cane.
Tourist – Historic Railway – The feature is used for tourist or historic railway journeys.
Other Railway Usage - Any usage not covered by the above.
Individual features may not agree with the following specifications to improve mapping legibility.
1:100 000 – all Light Rails, Monorails, Sugar Cane Railways, Railway Sidings, Tourist-Historic Railways.
1:250 000 – all Railways other than Usage includes Passenger.
1:1 000 000 – all Railways where the Usage includes Passenger.
CANE RAILWAY
Definition: A railway built specifically to carry small trains carrying sugar cane from the cane fields to the sugar mills for processing
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature. · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
LIGHT RAIL
Definition: A form of passenger urban rail transit characterized by a combination of tram and metro features. While its rolling stock is more like a traditional tram, it operates at a higher capacity and speed, and often on an exclusive right-of-way
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature. · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
MONORAIL
Definition: An elevated railway running on a single line and generally used for tourist purposes
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature. · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, address details, tourist publications, organisations, Government websites, or other source material.
|
RAILWAY
Definition: A transportation system using one or more rails to carry freight or passengers.
Alternate Terms: Railway spur
|
· Capture as a 2D polyline along the centre of the feature. · The location is plotted from orthorectified imagery unless GPS points have been received from Queensland Rail · Locations can be obtained from other datasets, existing mapping, tourist publications, organisations, Government websites, or other source material.
|
RAILWAY SIDING
Definition: A short section or sections of track by the side of a railway used for shunting as well as for loading and unloading of freight.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature. · The location is plotted from orthorectified imagery unless GPS points have been received from Queensland Rail · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
TOUIST - HISTORIC RAILWAY
Definition: A railway that has been built specifically for the use of tourist or one that has been preserved for historical purposes.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature. · The location is plotted from orthorectified imagery unless GPS points have been received from Queensland Rail · Locations can be obtained from tourist or historical mapping, Local Authorities, or other sources
|
Railway Bridges and Overpasses
A polyline feature class displaying the location of railway bridges and overpasses along the railway network.
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. (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) |
|
Elevated Railway – A structure carrying rail traffic that is built above the surrounding landscape.
Railway Bridge - A structure erected over a waterway, depression, or obstacle to carry rail traffic
Railway Causeway - An embankment of earth or masonry erected across open water or an area subject to inundation and carrying a railway.
Railway Overpass –A separation of surface levels constructed to prevent direct intersection with other road or rail networks.
1:25 000 – >/= 25 m and < 250 m
1:100 000 – >/= 250 m
ELEVATED RAILWAY
Definition: A structure carrying rail traffic that that is built above the surrounding landscape
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the railway. · Capture features with a length greater than 25 metres · The location is plotted from orthorectified imagery · Vertex points to coincide with the vertex points on the railway. · Locations can be obtained from other datasets, existing mapping, tourist publications, organisations, Government websites, or other source material.
|
RAILWAY BRIDGE
Definition: A structure erected over a waterway, depression, or obstacle to carry rail traffic
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the railway. · Capture features with a length greater than 25 metres · The location is plotted from orthorectified imagery · Vertex points to coincide with the vertex points on the railway. · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres · Locations can be obtained from other datasets, existing mapping, tourist publications, organisations, Government websites, or other source material.
|
RAILWAY CAUSEWAY
Definition: An embankment of earth or masonry erected across open water or an area subject to inundation and carrying a railway.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the railway. · Capture features with a length greater than 25 metres · The location is plotted from orthorectified imagery · Vertex points to coincide with the vertex points on the railway. · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
RAILWAY OVERPASS
Definition: A separation of surface levels constructed to prevent direct intersection with other road or rail networks.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the railway. · Capture features with a length greater than 25 metres · The location is plotted from orthorectified imagery · Vertex points to coincide with the vertex points on the railway. · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
Railway Stations and Sidings
A point feature class displaying the location of railway stations and sidings on the Queensland railway network.
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: Cane Railway Siding Point Railway Station Railway Siding Point
| 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: Coal Handling Freight Handling Mineral Handling Passenger Stop Railway Junction Railway Siding Railway Yard Railway Workshop Stabling Yard Sugar Cane Siding Tourist – Historic Railway Stop Other Railway Stop Usage Non Applicable
| 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. (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) |
|
Cane Railway Siding Point - A junction point of railroad tracks connected to the main track by switches used for temporary storage and loading or unloading of sugar cane.
Railway Station – A facility which is regularly used for loading and unloading of people or materials onto trains
Railway Siding Point – A junction point of railroad tracks connected to the main track by switches used for temporary storage and loading or unloading of trains.
Upper_scale:
1:100 000 – all Cane Railway Siding Points, Railway Siding Points
1:250 000 – all Railway Stations
CANE RAILWAY SIDING POINT
Definition: A junction point of railroad tracks connected to the main track by switches used for temporary storage and loading or unloading of sugar cane.
Alternate Terms:
|
· Capture as a 2D point at the centre of the feature coincident with the cane railway · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
RAILWAY STATION
Definition: A facility which is regularly used for loading and unloading of people or materials onto trains
Alternate Terms:
|
· Capture as a 2D point at the centre of the feature coincident with the railway line · The location is plotted from orthorectified imagery · If multiple tracks, capture the point coincident with the track with the largest Upper Scale value and where trains on this track are travelling towards Brisbane. · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
RAILWAY SIDING POINT
Definition: A junction point of railroad tracks connected to the main track by switches used for temporary storage and loading or unloading of trains.
Alternate Terms:
|
· Capture as a 2D point at the centre of the feature coincident with the railway siding · The location is plotted from orthorectified imagery · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
Railway Tunnels
A polyline feature class displaying the location of railway tunnels on the Queensland railway network.
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: Railway Tunnel
|
|
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) |
|
Railway Tunnel – A constructed passage that may be underground, underwater or passing under infrastructure.
1:25 000 – >/= 25 m and < 50 m
1:100 000 – >/= 50 m
RAILWAY TUNNEL
Definition: A constructed passage that may be underground, underwater or passing under infrastructure.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature. · Vertex points to coincide with the vertex points on the railway. · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
Road Bridges and Overpasses
A polyline feature class displaying the location of road bridges and overpasses along the Queensland road network.
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 |
|
Elevated Road – A structure carrying road traffic that is built above the surrounding landscape.
Road Bridge - A structure erected over a waterway, depression, or obstacle to carry road traffic.
Road Causeway - An embankment of earth or masonry erected across open water or an area subject to inundation and carrying a road.
Road Overpass – A separation of surface levels constructed to prevent direct intersection with other road or rail networks.
1:25 000 – >/= 25 m and < 250 m
1:100 000 – >/= 250 m
ELEVATED ROAD
Definition: A structure carrying road traffic that is built above the surrounding landscape.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the road · The location is plotted from orthorectified imagery · Capture features with a length greater than 25 metres · Vertex points to coincide with the vertex points on the road · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
ROAD BRIDGE
Definition: A structure erected over a waterway, depression, or obstacle to carry road traffic
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the road · The location is plotted from orthorectified imagery · Capture features with a length greater than 25 metres · Vertex points to coincide with the vertex points on the road · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
ROAD CAUSEWAY
Definition: An embankment of earth or masonry erected across open water or an area subject to inundation and carrying a road.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the road · The location is plotted from orthorectified imagery · Capture features with a length greater than 25 metres · Vertex points to coincide with the vertex points on the road · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
ROAD OVERPASS
Definition: A separation of surface levels constructed to prevent direct intersection with other road or rail networks.
Alternate Terms:
|
· Capture as a 2D polyline along the centre of the feature co-incident with the road · The location is plotted from orthorectified imagery · Capture features with a length greater than 25 metres · Vertex points to coincide with the vertex points on the road · If the feature is less than 25 metres and is named, exaggerate the length to a minimum of 25 metres · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material
|
Road Tunnels
A polyline feature class displaying the location of road tunnels along the Queensland road network.
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: Road Tunnel
|
|
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 |
|
Road Tunnel – A constructed passage that may be underground, underwater or passing under infrastructure.
1:25 000 – >/= 25 m and < 50 m
1:100 000 – >/= 50 m
ROAD TUNNEL
Definition: A constructed passage that may be underground, underwater or passing under infrastructure.
Alternate Terms: Underpass
| · The location of the tunnel along with entrances and exits are to align to the ‘Feature Type – Tunnel’ in Queensland Road and Track dataset. · Capture as a 2D polyline along the centre of the feature. · Vertex points to coincide with the vertex points in the Queensland Road and Track dataset. · Underground alignment can be verified using the spatial cadastre (coverage – Volumetric) plan. · Locations may be plotted from orthorectified imagery. · Locations can be obtained from other datasets, existing mapping, organisations, Government websites, or other source material.
|
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.
- No labels