Output from this program is designed to be used as input to the program v.cadlabel.
The v.in.dxf program will only recognize points, lines, polylines, and text in the DXF format, and will translate these to GRASS vector format; other types of data are ignored.
The names of the GRASS vector (dig, dig_ascii, and dig_att) files output are constructed as prefix.extension, where prefix is the prefix name specified by the user and extension is the number of the DXF layer from which the data were obtained. If the user does not specify a prefix name, the output files take their prefix from the prefix of the input DXF map layer. For example, for the DXF file named streams.dxf containing line data on layer , the GRASS vector map layer output would be named streams..
The below examples are given for a DXF design file named cont.dxf
containing contou
v.in.dxf can be run with default values, as shown below:
Here, this is equivalent to running the following command:
Either of the above commands will produce three
GRASS dig files (named cont.9, cont.11, and cont.12)
and one dig_att file (named cont.12).
In our example, however, the cont.12 file contains intermediate
contou
The above command will generate three dig files
(named contour.9, contour.11, contour.12),
and will create one dig_att file containing text labels
(called contour.12).
No contou
Translation:
Editing:
Attributes:
Revised by Dave Gerdes,
U.S. Army Construction Engineering Reseach Laboratory (12/89)
Revised and appended by Jan Moorman,
U.S. Army Construction Engineering Research Laboratory (7/90)
Code for arcs and circles from National Park Service GIS Division
written by Tom Howard.
intermediate contou
index labels and some intermediate contou
NOTES
Output Filenames:
The output filename, prefix.extension, conforms with the GRASS limit
of 14 characters. The entire prefix name is used, a '.' inserted,
and as much of the extension name is used as the 14 character limit will permit.
Excess characters are truncated.
To minimize the possibility of creating output files with the same names
(resulting in loss of data from the DXF file), use the prefix option to
abbreviate the DXF file name. This will leave the majority of characters
available for differentiating between layer names.
This data translation program does not contain any of the quality control
functions available in v.digit that will prevent data in an improper
format from being input to a GRASS data base. If present, DXF entities
are placed in output file(s) corresponding to the layers on which they
occurred in the DXF design file input.
If the user asks v.in.dxf to output ASCII vector (dig_ascii) files,
they must be converted to binary vector format before they are usable by
most GRASS vector commands. The user can convert GRASS vector files from
ASCII to binary format by running such programs as v.support or
v.in.ascii.
After conversion to binary format the vector files can be displayed
(e.g., with d.vect); however, the user must run v.support
on the binary vector files before they can be edited in v.digit.
The files output by v.in.dxf will preserve the data in whatever form they
exist in the DXF file. This means that output files may contain
unsnapped nodes, overshoots, gaps, and replicated lines.
The data, and the file header information (including the owner's name,
map's name, date, and scale, and UTM zone) for the GRASS vector files output
may require editing by the user in v.digit.
The v.in.dxf program attaches attributes only to DXF text data
that are converted to GRASS vector data (such as contouSEE ALSO
v.cadlabel,
v.digit,
v.in.ascii,
v.out.dxf,
v.support
AUTHORS
Original dxf2dig program written by Jan Moorman,
U.S. Army Construction Engineering Research Laboratory (6/89)