Attributes

Attributes represent properties of Features. EXAMPLE: Attributes of the Feature "Road Element" include the street name and number of lanes. Attribution abbreviations can be GDF abbreviations (two-alphabet characters), GDF userdefined (one non-alphabet character, one alphabet character) or purely TomTom^®-defined. Attribution codes in MultiNet^® can be GDF definitions or TomTom^®-defined definitions. Some attributes do not have attribute codes representing their values.

Feature Code Type Attributes

Shapefile/OSL field names = FEATTYP, ARETYP, TRPELTYP, ELEMTYP

GDF-AS field name (in documentation) = FEAT_CODE

GDF-AR field name (in documentation) = FeatClass

Feature types are taken from Geographic Data Files (GDF) definitions and are identified by a 4-digit code in TomTom^® MultiNet^® data. See also Features earlier in this user guide.

Feature type codes "9000" to "9999" are TomTom^®-defined features.

For a list of attribute names and codes, refer to the allcodes database included in your data delivery.

Attribute Types

Shapefile/OSL field name = ATTTYP

GDF -AS field name (in documentation) = ATT_TYPE

GDF-AR field name (in documentation) = AttTyp

MultiNet^® Attribute Types are derived from GDF definitions. For a list of attribute names and codes, refer to the allcodes database included in your data delivery.

GDF Attributes

Table 1.
GDF ATTRIBUTION NAME ABBREVIATION	GDF ATTRIBUTION NAME	SHAPEFILE AND OSL FIELD NAME ABBREVIATION	GDF ATTRIBUTION VALUE CODE	GDF ATTRIBUTION VALUE
FT (two-character abbreviation)	FerryType	FT	1 2 3	Ferry Connection Rail Connection Both

Note: Some Shapefile and OSL field name abbreviations differ from GDF attribution abbreviations in data.

Example: Plural Junction

GDF attribution abbreviation = 2P.
Shapefile and OSL field name abbreviation = PJ.

GDF User-Defined Attributes

GDF attributes are two alphabetic characters (e.g., JT). The GDF standard also allows for user-defined attributes, provided the following form is followed: "Any two-character code of which the first character is non alphabetic."

Table 2.
GDF USER-DEFINED ATTRIBUTION NAME ABBREVIATION	GDF USER-DEFINED ATTRIBUTION NAME	SHAPEFILE AND OSL FIELD NAME ABBREVIATION	ATTRIBUTION VALUE CODE	ATTRIBUTION VALUE
8D (one non-alphabetic and one alphabetic abbreviation)	Side of Line	SOL	0 1 2 3	Both sides Left side Right side On line

TomTom-Defined Attributes Without an Attribute Code

Sometimes a feature needs more than one attribute to define a feature characteristic. In these cases, a feature characteristic is called a Composite Attribute and requires "subattributes" to be appropriately defined.

For a list of available Composite Attributes, refer to the allcodes database included in your data delivery.

Note: Composite Attributes codes do not appear in your data—only the sub-attribute codes of the Composite Attributes do.

Example:BPAS is the Composite Blocked Passage attribute. The "BPAS" code does not appear in the data.

Sub-attributes BP (Blocked Passage) and VT (Vehicle Type) do appear in the data, and are mandatory.
Sub-attribute VP (Vehicle Period) appears in data as an optional sub-attribute.

Note: Attributes that are part of an attribute set do not have a definite order unless they are defined as part of a "Composite Attribute".

Segmented Attributes (GDF Format Only)

A Segmented Attribute is an attribute that references part of a feature. See the Data Content GDF-AS or Data Content GDF-AR sections of this user guide for more information.

For a list of attribute names and codes, refer to the allcodes database included in your data delivery.