Development of a Data Exchange Protocol between EMME/2 and ArcInfo

  presented as a route; the transit line attributes are maintained in the route attribute table (RAT);

a transit line segment is represented as a section; the segment attributes are maintained in the section table (SEC).

C3) Relationship between data elements and features contained in both models

The following table contains general object descriptions found in a transportation planning infrastructure, and the corresponding element in both software packages:

Objects ArcInfo items EMME/2 items street route - street section section - directed street section arc link intersection node node traffic light node node transit line route line transit section section
(within a route) segment
(within a line) transit stops point event, node node region region zone, group, ensemble TAZ (traffic analysis zone) polygon zone Origin and Destination node, center centroid O-D matrix - matrix supply center node centroid demand center node centroid turns turn (arc-node-arc) turn (at_node-from_node-to_node) arc-to-arc barrier arc selection set turn penalties drawing polyline, patterns annotation, demarcations text annotation annotation

C4) Differences and "inconsistencies" between the two data models

ArcInfo EMME/2 - arcs can be bidirectional (with directional attributes) - links are unidirectional (represent flow of traffic) - each arc can be composed of up to 500 vertices, including from-node and to-node - each link

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