ArcInfMM: Conversion of vector and raster files between MiraMon and ArcGIS/ArcInfo (Export/interchange file)

Access this help text as a web page: ArcInfMM

Presentation and options	Dialog box of the application
Syntax

Presentation and options

This program performs the format conversion from a family of structured vector files of MiraMon to the Export/"interchange file" (E00) format of ArcInfo (currently ArcGIS), and vice versa. The export format can also be read by ArcView.

MM-ArcInf

ArcInf-MM

In the direction from Export to MiraMon, points, arcs and polygons are supported and the databases linked to these files are created. ArcInfo layers holding arcs and polygons have to be topologically structured (CLEAN/BUILD); a polygon layer cannot contain arcs with end nodes. Own MiraMon binary files are generated supporting (and preserving) the topology. Converting from ArcInfo raster file to MiraMon is also possible. During the conversion, a scaling factor and a displacement can be applied. It must be considered that the displacement X, Y is applied after the scaling factor; these parameters are used to make conversions from m to km, to remove first figures in the UTM coordinates, etc. If no geometric conversions are required, simply enter Scal=1, DisplacX=0 and DisplacY=0.

In the direction from MiraMon polygon files (POL) to Export, only those arcs needed for the cycling of the polygons are exported, not all the arc database. MiraMon points (PNT) and arcs (ARC) can also be exported.

In the direction from MiraMon to Export, and when there is more than one record per graphic identifier, only the last one is transformed. The databases associated by relational links are not translated, but can be easily relinked using the appropriate operation (join, etc).

To export MiraMon rasters to ArcInfo, it is recommended to use, from the MiraMon menu, "File | Export | IMG -> TIFF, GeoTIFF". The option "File | Export | IMG -> TXT (ASCII)..." may also be appropriate. On the other hand, the "File | Export | IMG -> LAN/GIS (Erdas 7.4)" option can present problems with the accuracy of the coordinates.

In the direction from MiraMon to Export another additional parameter can be specified that indicates whether the exportation will be in double precision. ArcView for PC (v. 2.1) supports files in double precision, but they are treated like simple precision and, therefore, it is not required to store them in double precision if not working in a workstation. In the case of creating a MiraMon file from an ArcInfo file, double and simple precision are supported, and it is inferred by ArcInfMM.

NOTES about the Export format (E00):

The Export format is a backup ArcInfo format. ArcInfMM do not accept the compressed Export format: NONE compression have to be specified when exporting ArcInfo layers.

To generate an E00 file from an ArcInfo PC or workstation it should be done:: EXPORT COVER LayerName E00FileName(without extension) N
(The hardware key must be connected to the computer; N indicates compression NONE)
To restore a coverage from ArcView:: IMPORT E00FileName LayerName
(Program to convert E00 files to layers ready for ArcInfo or ArcView on PC: Import71.)
To restore a layer from ArcInfo:: IMPORT COVER E00FileName LayerName

NOTE: If possible use import71 instead of import because it generates doble precision layers. Import generates simple precision layers, and it can not be enough for local area scopes.
In new versions of ArcInfo or ArcView (v.8) Export file is refereed as "Interchange file". This version has an ArcToolBox application. A tool has to be selected:
To use an e00: Import to coverage|Import from interchange file
To generate an e00: Export from coverage|Coverage to interchange file

ArcInfMM can only perform the translation of a single export E00 file, but not of a series of files E00, E01, E02, etc. Therefore, all your ArcInfo layer must be saved in a unique E00 file; this can be controlled with the parameter MAXNRLINES of the ArcInfo's EXPORT.

Although MiraMon can work with practically un unlimited number of vertices per arc, ArcInfo does not support arcs with 500 vertices or more (the ArcInfo documentation under \"Coverage Data Limitations\" can be readed for further information). In order for ArcInfo or ArcView to be able to read the E00 resulting from a arc file that contains elements with more than 500 vertices, it is necessary for the application to go through a slow process of cutting all arcs with which surpass this limitation followed by rebuilding the topology of the layer.

It must be considered that the number of arcs and its geometric characteristics may eventually be different now. For instance, an arc delimiting a polygon or a road which was a single arc in MiraMon may now have become more than one graphical object in ArcInfo due to this limitation of 500 vertices per arc. However, the exporting process will assign to each fragment the corresponding thematic attributes of the original arc.

These changes do not modify neither the number of polygons nor their geometric and attribute characteristics.

Dialog box of the application

ArcInfMM dialog box.

Syntax

Syntax:

ArcInfMM TopMMFile E00File Scaling DisplacX DisplacY [/a]
ArcInfMM E00File MMFile Scaling DisplacX DisplacY

Parameters:

TopMMFile (Topological input File - Input parameter): Is a point, arc or polygon file (with extension PNT, ARC, or POL).
E00File (E00 File - Output parameter): Is an Arc/Info Export file (with extension).
Scaling (Scaling Factor - Input parameter): Scaling factor
DisplacX (Displacement X - Input parameter): X Displacement factor
DisplacY (Displacement Y - Input parameter): Y Displacement factor

MMFile (Output File - Output parameter): Is a point, arc, polygon or raster file (PNT, ARC, POL or IMG).

Modifiers:

1: Arc/Info with double precision. This is the default option.
2: Arc/Info with simple precision, like some PC-Arc/Info versions.
Note that in the conversions from Arc/Info to MM (E00 as origin), the 'a' parameter is not required, because MiraMon always works with double precision coordinates.

ArcInfo and ArcView are registered trademarks of Esri, Inc.
MiraMon is a registered trademark of Xavier Pons.