NZ Topo - object class tree_pnt
This page describe the tree_pnt object class used to represent objects in the NZTopo topographic database.
A woody perennial plant, having a self-supporting main stem or trunk.
Only a selection of trees are held in the data and shown on the printed maps. Trees (other than very large, isolated ones) next to roads, tracks and other such features are not generally held in the data or shown on the maps. A single tree point feature may be used to indicate a group of trees. Any in residential areas are not held in the data or shown on the printed maps
|Additional entity class||Not applicable|
|Entity source||US Standard Entity|
|LSLIFF object class||172|
|Attribute description||Attribute values*|
|The name of the feature, where known. 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||2012-08-28||Updated map image and aerial view; added representation specification and example feature photographs|
|5||2012-08-28||Added scale-specific definitions|
|4||2012-08-16||Name attribute in UTF-8 format; added name_ascii attribute|
|3||2010-03-01||Added name_macronated attribute|