...
Airport Areas
Airport Runways and Taxiways
Air Traffic Control Towers
Busway Stations
Green bridges
Helipads
Landing Ground
Toll Points
Railways
Railway and Sidings
Railway Bridges and Overpasses
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
Description of feature classA 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: 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) | |
|
...
Heading
...
Airport Runways and Taxiways
A polygon feature class displaying the extents of airport infrastructure that facilitate the movement of aircraft on the ground.
| Expand |
|---|
|
| Expand |
|---|
| title | Feature Type definitions: |
|---|
|
| Expand |
|---|
| title | Function definitions: |
|---|
|
| Expand |
|---|
|
| Expand |
|---|
|
Heading
Description of feature class
...
...
| title | Feature Type definitions: |
|---|
...
| title | Function definitions: |
|---|
...
...
Heading
Description of feature class
...
...
| title | Feature Type definitions: |
|---|
...
| title | Function definitions: |
|---|
...
...
Heading
Description of feature class
...
...
| title | Feature Type definitions: |
|---|
...
| title | Function definitions: |
|---|
...
...
Heading
Description of feature class
| Expand |
|---|
|
| Expand |
|---|
| title | Feature Type definitions: |
|---|
|
| Expand |
|---|
| title | Function definitions: |
|---|
|
| Expand |
|---|
|
| Expand |
|---|
| title | Capture Process: | 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) | |
|
|---|
| Expand |
|---|
| title | Feature Type definitions: |
|---|
|
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. |
| Expand |
|---|
|
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. |
| Expand |
|---|
|
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 |
| Expand |
|---|
|
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.
| 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: 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) | |
|
| Expand |
|---|
| title | Feature Type definitions: |
|---|
|
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. |
| Expand |
|---|
|
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. |
| Expand |
|---|
|
Upper_scale: 1:100 000 – all data |
| Expand |
|---|
|
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.
| 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: 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) | |
|
| Expand |
|---|
| title | Feature Type definitions: |
|---|
|
Busway Station – A facility which is regularly used for loading and unloading of passengers onto buses on a designated network. |
| Expand |
|---|
|
1:100 000 – all data Capture Process: |
| Expand |
|---|
|
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.
| 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 |
|---|
|
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. |
| Expand |
|---|
|
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
| 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: 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) | |
|
| Expand |
|---|
| title | Feature Type definitions: |
|---|
|
Helipad – A constructed and maintained area for helicopter take-off and landing. |
| Expand |
|---|
|
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. |
| Expand |
|---|
|
1:25 000 – all data |
| Expand |
|---|
|
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. |
|
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...
Heading
Description of feature class
...