1v.in.dxf(1) GRASS GIS User's Manual v.in.dxf(1)
2
3
4
6 v.in.dxf - Converts file in DXF format to GRASS vector map.
7
9 vector, import, DXF, level1
10
12 v.in.dxf
13 v.in.dxf --help
14 v.in.dxf [-etbfli1] input=name output=name [lay‐
15 ers=string[,string,...]] [--overwrite] [--help] [--verbose]
16 [--quiet] [--ui]
17
18 Flags:
19 -e
20 Ignore the map extent of DXF file
21
22 -t
23 Do not create attribute table
24
25 -b
26 Do not build topology
27 Advantageous when handling a large number of points
28
29 -f
30 Import polyface meshes as 3D wire frame
31
32 -l
33 List available DXF layers and exit
34
35 -i
36 Invert selection by DXF layers (don’t import layers in list)
37
38 -1
39 Import all objects into one layer
40
41 --overwrite
42 Allow output files to overwrite existing files
43
44 --help
45 Print usage summary
46
47 --verbose
48 Verbose module output
49
50 --quiet
51 Quiet module output
52
53 --ui
54 Force launching GUI dialog
55
56 Parameters:
57 input=name [required]
58 Path to input DXF file
59
60 output=name [required]
61 Name for output vector map
62
63 layers=string[,string,...]
64 List of DXF layers to import (default: all)
65
67 v.in.dxf converts DXF format CAD files to GRASS vector format. The fol‐
68 lowing graphical objects (DXF entities) are supported:
69
70 · point
71
72 · DXF POINT
73
74 · line
75
76 · DXF LINE
77
78 · DXF POLYLINE
79
80 · DXF LWPOLYLINE
81
82 · DXF ARC
83
84 · DXF CIRCLE
85
86 · DXF TEXT
87
88 · face
89
90 · DXF POLYFACE MESHES
91
92 · DXF 3DFACE
93 Table and column names are changed to lowercase characters for easier
94 SQL usage (lowercase table/column names avoid the need to quote them if
95 the attribute table is stored in a SQL DBMS such as PostgreSQL).
96
97 The "layer" column will contain the name(s) of the DXF input layer(s).
98 The DXF entity type string will be stored in the "entity" column as
99 uppercase.
100
101 The "handle" column can be used to store small bits of data associated
102 with any entity in the DXF file (i.e., entity handle or unique object
103 identifiers in the layer). The entity handle is a "text string of up to
104 16 hexadecimal digits", which is a 64-bit integer (currently not sup‐
105 ported by GRASS database drivers). For text type entities, the text
106 value will be stored in the "label" column of the GRASS vector output
107 map. Neither the "handle" nor "label" column is mandatory.
108
110 AutoCad DXF (from Wikipedia, the free encyclopedia)
111 DXF References (Autodesk-supplied documentation)
112
114 v.out.dxf, v.in.ogr, v.out.ogr
115
116 How-to import DXF files in wxGUI (from GRASS User Wiki)
117
119 Original written by Chuck Ehlschlaeger, 6/1989
120 Revised by Dave Gerdes, 12/1989
121 US Army Construction Engineering Research Lab
122
123 Updated for GRASS 6 and 3D support. Huidae Cho, 3/2006
124 With minor additions by Benjamin Ducke (Oxford Archaeology), 4/2009
125
127 Available at: v.in.dxf source code (history)
128
129 Main index | Vector index | Topics index | Keywords index | Graphical
130 index | Full index
131
132 © 2003-2020 GRASS Development Team, GRASS GIS 7.8.5 Reference Manual
133
134
135
136GRASS 7.8.5 v.in.dxf(1)