Relationships

A Relationship can exist between Features, but not between Attributes. The GDF catalogue pre-defines a number of feature relationships. Relationships are identified by 4-digit codes. GDF allows user-defined relationships as 4-digit codes beginning with "9000".
Note: As with Feature Codes, "9000" to "9999" are TomTom®-defined Relationship Codes. No Feature Code values are repeated as Relationship Code values, i.e., all "9000" to "9999" codes are unique.

Example of a GDF-Defined Relationship:

GDF RELATIONSHIP CODE RELATIONSHIP NAME FEATURES INVOLVED
1001 Road Element in Aministrative Area Order 8 Area; Road Element

Example of a TomTom-Defined Relationship:

RELATIONSHIP CODE RELATIONSHIP NAME FEATURES INVOLVED
9501 Road Element in Order 9 Area Order 9 Aera; Road Element
Note: Features involved in a Relationship are sometimes referred to as "Partners."
Note: Relationship records show full feature reference (GDF Datasets, GDF Section ID, and GDF Feature ID.

Please see Theme 11: Relationships in the MultiNet Data Specifications and Data Model document for details.

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

AN IMPORTANT NOTE CONCERNING POI RELATIONSHIPS:
  • The only Relationships available involving Services are ones where both partners are available in standard MultiNet.
Example: The Service Belonging To Service Relationship is available for Airports and Airline Accesses (Access Gateway) since both Services are available in the standard MultiNet product.
  • If one of the features of the Relationship is only defined in the MultiNet POI enhancement product, then all its relationships are defined in the MN POI enhancement product only.

Example: 1: The Service in Order 8 Area Relationship involving Shops is only available in the MultiNet POI product because only one partner (Order 8 Area) is available in the standard MultiNet product.

Example: 2: The Service in Order 8 Area Relationship involving Railway Stations is available in the standard MultiNet product.

See the MultiNet Data Specifications and Data Model document for more details.