The ArcInfo workspace is considered to be a database created independently by ArcInfo users from their organizational point of view (policy, MIS standards, etc.). Therefore, one may expect a variety of data definitions and data contents stored in this database. The representation of real-world entities may vary in detail.
The EMME/2 data bank is an aggregate representation of the transportation infrastructure, the economic activities and the socio-economic characteristics of the urban area studied.
The EMME/2 coverage follows the EMME/2 network representation. This implies:
- the base network is an aggregate representation of reality and must respect the one-to-one relationship of the transit network (one stop equals one node); the road infrastructure and attributes are stored at the arc level;
- for the transit network, the infrastructure is represented by a route-system where one segment corresponds to one arc; the itinerary will be kept within a transit line on the basis of the section measures;
- for the zones, all data will be stored in a different coverage (because we need to use the CLEAN command to create the polygon topology, and that would create unnecessary nodes in the base network).
- Case one: There is an EMME/2 data bank but no ArcInfo workspace. One must extract information from the EMME/2 bank and then convert it into an ArcInfo coverage.
- Case two: There is an ArcInfo workspace but no EMME/2 data bank. The goal is then to export the ArcInfo coverage and convert it into an EMME/2 format.
- Case three: There is neither an ArcInfo workspace nor an EMME/2 data bank. In this case, the user will decide wh
