NZ Topo - object class runway_poly
This page describe the runway_poly object class used to represent objects in the NZTopo topographic database.
The usable surface where aircraft land and take-off.
All known instances captured; note that the oustide perimeter of large airports are held as 'airport_poly'. In the case of airstrips, the availability cannot be relied upon as farmers may graze the land and/or erect temporary fences
See also: airport_poly
|Additional entity class||Not applicable|
|Entity source||US Standard Entity|
|Map series||Topo50 Ant50|
|LSLIFF object class||337|
|Attribute description||Attribute values*|
|The name of the airstrip, where known. Runwaus within airports are, currently, not named. Text data from July 2012 will be in UTF-8 format. If your system is not UTF-8 compliant, you will need to use the name_ascii attribute, which has had any macronated vowels removed. UTF-8 stands for Unicode Transformation Format-8. It is an octet (8-bit) lossless encoding of Unicode characters. UTF-8 encodes each Unicode character as a variable number of 1 to 4 octets, where the number of octets depends on the integer value assigned to the Unicode character. It is an efficient encoding of Unicode documents that use mostly US-ASCII characters because it represents each character in the range U+0000 through U+007F as a single octet. UTF-8 is the default encoding for XML.|
|Indicates whether the entry in the name_ascii field contains a macronated vowel. Where the value is "Y" go to http://www.linz.govt.nz/regulatory/place-names/find-place-name/find-m%C4%81ori-place-names-dual-names-and-alternative-names for a list of places or feature names within New Zealand that are gazetted and include macrons|
|Text data from July 2012 will be in UTF-8 format. If your system is not UTF-8 compliant, you will need to use this attribute, which has had any macronated vowels removed.|
|A unique identifier for use on Topo50 data in the LINZ Data Service. This is not a universal ID. The intention is to manage these ID’s as persistent, however this is not guaranteed and there will be instances where what appears to be a minor change to a feature may result in a new ID being assigned.|
* See explanation of attribute values for more information about how attribute values are represented.
|6||2015-06-03||Provided more information in the Topo50 description field|
|5||2012-08-28||Updated map image and aerial view; added representation specification and example feature photographs|
|4||2012-08-28||Added scale-specific definitions|
|3||2008-04-10||Removed reference to seed and void objects|