This tool only works with an ArcInfo license and will only be available in ArcToolbox if you have installed ArcInfo Workstation.
Converts a coverage to an interchange file for transfer to another platform.
Learn more about how Export to Interchange File works
Usage tips
-
When exporting a coverage, all associated INFO tables are written to the interchange file. For example, if the coverage name specified for input data is Forest, an INFO table named Forest.LABEL would be saved in the interchange file. A table named Forest1.LABEL, however, would not be saved in the interchange file.
-
Export files created with the Compression option set to Full can be significantly smaller than export files created with the Partial or None options.
-
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.
-
Coverages to be exported must not contain edit masks. In other words, do not export an uncleaned cover. Run the Build or Clean tool to remove edit masks (msk.adf file in the coverage directory). Refer to the Help on Build or Clean for more information how these tools can possibly change your data.
-
Export has a limit of -999999999 on negative User-IDs.
-
Export files for coverages with nondefault text alignment will have data loss if imported to a version prior to 8.0.1.
-
The following environments affect this tool: derivedPrecision, newPrecision, projectCompare, scratchWorkspace, and current workspace.