Importing an ArcInfo interchange file (E00)
This topic applies to ArcInfo only.
The ArcInfo interchange file format, also known as an export file (.e00), is used to enable a coverage, grid to TIN, and associated INFO tables to be transferred between different machines that are not connected by any type of file sharing network. ArcInfo interchange files have an .e00 extension, which increases incrementally to .e01, .e02, and so on, if the interchange file is composed of several separate files.
If you use WinZIP to extract a zipped .e00 file, it can potentially corrupt the data. A configuration setting in the WinZIP program—TAR file smart CR/LF conversion—needs to be unchecked. To learn more, see article 17135 on the ESRI Support site.
Exporting a grid can result in an export file much larger than the original grid, even when full compression is used. This is because each grid cell must be represented in the export file in ASCII format, which is less efficient than the grid's binary format. Also, integer grids are stored in a compressed format, which cannot be maintained in the export file. The best solution is not to export large grids. All ArcInfo platforms that support grids now read the same file format, so exporting is not necessary. To create a single file for transfer, a utility, such as PKZIP (or "tar" on UNIX systems), can be used to place the workspace containing the grid into a single file. Versions of PKZIP and tar are available on both UNIX and PC systems. Warning: Do not PKZIP or tar just the grid, because you'll lose the INFO tables. If you don't want to transfer all the grids in your workspace, create a temporary workspace and copy the grids to be transferred into it.
- The input E00 file cannot be placed in a directory that has a space in the name or a space anywhere in the path to the directory.
- The output coverage or grid cannot be placed in a directory that has a space in the name or a space anywhere in the path to the directory.
- The output coverage or grid name cannot be more than 13 characters long.
- The output coverage or grid name cannot contain special characters; for example, #, @, or %. Underscores are permitted.