NAME

SYNOPSIS

DESCRIPTION

The module not only can analyse the content of an Arc/Info file, but try to create the objects described (geometry and attributes).

m.in.e00 will be run non-interactively if the user specifies program arguments on the command line, using the form:

m.in.e00 [-ids] input=name [mapset=name] [action=what to do] [verbose=debug level] [logfile=name]

Alternately, the user can simply type:

m.in.e00

on the command line without program arguments. In this case, the user will be prompted for parameter values using the standard GRASS user interface described in the manual entry for parser.

FEATURES

GRASS files created have the name extracted from the first line of the e00 file, i.e. the name of the coverage. The file is read from the current directory unless specified differently.

The following rules are used : A line vector file is created when there is a non-empty ARC section, and neither PAL (Polygon Attribute Label) section, neither PAT (Point/Polygon Attribute Table) table in INFO section. Otherwise a polygon vector file is created, excepted when the ARC section is empty or doesn't exist, in which case a site file is created.

Dig_cats files are created if the PAT or AAT (Arc Attribute Table) tables have more attributes than the standard one. If there is one extra attribute, the dig_cats file has the name of the vector (dig) file created. If there is more than one extra attribute, the dig_cats files have names of the form cover_name.attribute_name. If you want to use one of them, you must rename it so it matches the name of the vector file. Doing this, v.to.rast will use it for the raster file created.

OPTIONS

Flags:

-i

Use the "feature-ID" of the arc info objects to link geometry and attribute's tables. The default is to use the "feature-#" field (which is an internal link, but you should not rely on it for linking Arc/Info objects to an external database. (GRASS 5.0 option)

-d

Use a database instead of as many dig_cats files as you have attributes in the INFO tables (not yet operational). (GRASS 5.0 option)

-s

Automatically run "v.support" on newly created vector file.

Parameters:

mapset=name

For creating a new mapset for the data imported. This may be useful, since we cannot create a projection info file and a default window in an existing mapset. When a file is imported in the current mapset, you should take care that they are in the same projection. Unfortunately, you may run in trouble after that when using g.region (Cf BUGS).

action=what to do

Five options: analyse, raster, lines, vector and all. By default, all is used and everything (grid, points, lines, polygons) is imported. Analyze produces no files, but only a log output (level 5) on stderr, and is useful to see whether the e00 file is clean or not. Raster imports only grid section. Lines imports only the geometry (no label are attached to the lines or polygons) of a point/line/polygon coverage. Vector imports a point/line/polygon coverage with their attributes.

verbose=debug level

Number between 0 (no trace of what's happening) and 9 (very verbose log).

logfile=name

Name of file where log info will be written. By default log info are directed to stderr.

BUGS AND CAVEAT

No attribute (cats) file is produced when importing a grid.

The program may crash when unexpexted data (mainly in INFO section) are found, or when the input file is corrupted.

There is no support for projection. Using verbose=1 lets you see the parameters of the e00 file, but you must create the DEFAULT_WIND and the PROJ file yourself.

New mapset are always created with proj=0 zone=99. If the default proj and zone are not the same, g.region complains and d.vect or d.rast refuse to display your data. The only thing to do is to import in the current mapset.

NOTES

SEE ALSO

AUTHOR