Link Data
A run of guide path, as it appears in a serialized network specification.
Both the zone length and the zone count are carried even though either determines the other given the length. That redundancy is deliberate: it makes the specification self-describing, and it lets a validation failure report which of the three quantities the modeler actually supplied rather than guessing. The three are required to agree, within the library's default numerical precision so that a length written as a product of decimals is not rejected for a rounding error the modeler cannot see.
Prefer the companion factory functions to the constructor: they derive the redundant quantity instead of asking for it, which removes the commonest way to write an inconsistent link.
Parameters
unique within the network
the name of the beginning intersection
the name of the ending intersection, different from the beginning
the total length in the modeler's units, strictly positive
the length of each zone, strictly positive
how many zones divide the link, at least one
whether traffic may run one way, both ways, or into a dead end
multiplies transporter velocity on this link, strictly positive
direction of travel in degrees leaving the beginning intersection. Layout metadata only: it does not affect travel time.