NZ Topo - object class ford_pnt

This page describe the ford_pnt object class used to represent objects in the NZTopo topographic database.


A shallow or flat portion of the bed of a watercourse where a crossing may be effected

Topo50 description

Only road fords are held in the data and shown on the printed maps. Fords on tracks are not captured. Fords are held in the data as a point feature, but represented as a line on the printed maps.

Representation specification

Representation specification showing ford_pnt

Click to enlarge image

See also: road_cl river_cl

Class attributes

Object classford_pnt
Entity classFORD
Additional entity classNot applicable
Object inheritancesimple_point
Entity sourceUS Standard Entity
Map series Topo50
LSLIFF object class44

Object attributes

AttributeLSLIFF code
Shapefile field
Data type
Attribute descriptionAttribute values*
The name of the ford, 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.
"Evans Crossing"
Indicates whether the entry in the name_ascii field contains a macronated vowel. Where the value is "Y" go to 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.

Change log

Feature versionRevisedDescription
112013-11-05updated information in the Representation field
102013-08-30Provided more detail for the Representation Specification
92012-08-28Updated map image and aerial view; added representation specification and example feature photographs
82012-08-28Added scale-specific definitions
72012-08-16Name attribute in UTF-8 format; added name_ascii attribute
62010-03-01removed orientation attribute, added comment, and added name_macronated attribute
52008-04-10removed reference to seed and void objects
42002-06-18new attribute
32001-11-23unspecified update
22001-11-01new attribute
11999-03-01intial status