Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Hatch group codes (continued)<br />
Group codes<br />
varies<br />
Description<br />
Pattern line data. Repeats number of times specified by code 78. See<br />
“Pattern Data” on page 83<br />
47 Pixel size used to determine the density to perform various intersection<br />
and ray casting operations in hatch pattern computation for associative<br />
hatches and hatches created with the Flood method of hatching<br />
98 Number of seed points<br />
10 Seed point (in OCS)<br />
DXF: X value; APP: 2D point (multiple entries)<br />
20 DXF: Y value of seed point (in OCS); (multiple entries)<br />
Boundary Path Data<br />
The boundary of each hatch object is defined by a path (or loop) that consists<br />
of one or more segments. Path segment data varies depending on the entity<br />
type (or types) that make up the path. Each path segment is defined by its<br />
own set of group codes. For information about abbreviations and formatting<br />
used in this table, see “Formatting Conventions in This Reference” on page<br />
6.<br />
Hatch boundary path data group codes<br />
Group codes<br />
Description<br />
92 Boundary path type flag (bit coded):<br />
0 = Default; 1 = External; 2 = Polyline;<br />
4 = Derived; 8 = Textbox; 16 = Outermost<br />
varies<br />
Polyline boundary type data (only if boundary = polyline). See Polyline<br />
boundary data table below<br />
93 Number of edges in this boundary path (only if boundary is not a<br />
polyline)<br />
72 Edge type (only if boundary is not a polyline):<br />
1 = Line; 2 = Circular arc; 3 = Elliptic arc; 4 = Spline<br />
varies<br />
Edge type data (only if boundary is not a polyline). See appropriate<br />
Edge data table below<br />
97 Number of source boundary objects<br />
80 | Chapter 6 ENTITIES Section
Change language