/
Waypoint Dependencies [WIP]

Waypoint Dependencies [WIP]

Owned by Thomas Clark
Jan 13, 2025
2 min read

Concepts

Waypoints

The following waypoint types are supported:

  • Vehicular - feature types Parking and Rideshare / Drop-off

  • Pedestrian: feature type Entrance

Prerequisite Knowledge

Location Hierarchy

Waypoint Dependencies are directly reliant on a robust locast hierarchy. Refer [here] for more information on Location Hierarchy.

Requirements

Feature Type Availability

An account must have at least 1x Parking or Rideshare / Drop-off feature type available for Waypoint Dependencies to be enabled. This Parking or Rideshare / Drop-offfeature can be either:

  • Within the same account

  • Within a (visible) parent account

  • Within a (visible) sibling account

See [client account structure] for more information.

Default behaviour

With no Parking or Rideshare / Drop-off feature types available (see section above), Waypoint Dependencies will not be active; standard closest-point routing will be active.

With 1x or more Parking or Rideshare / Drop-offfeature types available, any vehicular path to or from a PAM location will utilise waypoint dependencies by default.

If no waypoint dependencies are assigned to a feature, and no dependencies are available through inheritance, the following will occur:

  • Routing from a PAM location to an external location: the closest (straight-line) Parking or Rideshare / Drop-offfeature to the start location will be selected by default

  • Routing from a PAM location to an external location: the closest (straight line) Parking or Rideshare / Drop-offfeature to the destination will be selected by default

Concepts

Inheritance

A feature will automatically inherit any assigned dependencies from that feature’s parent and grandparent (1 and 2 levels above in the location hierarchy respectively). Additional dependencies can be assigned directly to a feature; a combination of inherited and newly assigned dependencies will be passed on to that feature’s children (if applicable).

Any feature not part of a/the location hierarchy will not inherit any waypoint dependencies, but can have dependencies directly assigned.

Priority

Dependencies added to a feature are prioritised in order of assignment. This priority is retained in any inheritance (see above). Priority affects dependencies as follows:

Vehicular dependencies: The highest priority dependency will be selected by default on any appropriate route. Other dependencies will also be available for selection, sorted in order of priority.

Entrance dependencies: The highest priority dependency will be selected by default, no other dependencies will be shown.

Overall priority as below:

  1. Dependencies assigned directly to a feature

  2. Dependencies assigned to a feature’s parent

  3. Dependencies assigned to a feature’s grand-parent