Enif - Toward a New Interface for EMME/2

   Element type: Pointers: Flags: mode next mode in sequence isAuto, isTransit, isAuxAuto, isAuxTransit node next node in sequence, first outgoing link, first incoming link isZone, isIntersection link I-node, J-node, next link with same I-node, next link with same J-node, first outgoing turn, first incoming turn isAccess, isEgress, isConnector, isAuto, isTransit, isAuxAuto, isAuxTransit transit vehicle next transit vehicle in sequence, transit mode   transit line next transit line in sequence, first transit segment, transit mode   transit segment next segment of same line, transit line, I-node, link isFirst, isMidLayover, isLast, isHidden turn incoming link, outgoing link, next turn with same incoming link, next turn with same outgoing link isUTurn zone node   origin zone   destination zone   O-D pair origin, destination        

The network element types include all those already used in EMME/2, i.e. mode, node, link, transit vehicle, transit line, transit segment and turn. In contrast to EMME/2, matrix related data is also considered part of the generalized network. This leads to the additional network element types zone, origin, destination and O-D pair.

While most data handling can be implemented at the abstract network element level, all network specific aspects have to be implemented at the level of the specific element type, e.g. finding the outgoing or incoming links of a node or following the segments along the itinerary of a transit line. This is achieved by associating with each network element type a type specific set of pointers to other network elements, as well as a set of flags. These are shown i

上一页  [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]  ... 下一页  >>