Examining the source code for v.in.dxf/find_lines.c (I
encountered this problem with GRASS 5.0.0, but the source
code for 5.0.2 is the same), I noted that find_lines.c
expects all LINE and similar entities to be contained within
the ENTITIES section of a dxf file. However, the dxf format
allows entities to appear within the BLOCKS section as well
(cf.: www.relief.hu/h_dxf12.html). Any lines defined outside
the ENTITIES section will apparently be missed.
I've tried one workaround ...
[snip]
Taking a quick look at the above referenced dxf site and
knowing a little about dxf, I think the problem is bigger
than just reading the BLOCKS section. It seems to me that
one must store the entity defined in the block section and
be prepared to insert, scale and rotate the stored block
(possibly multiple times) when it is later referenced in the
ENTITIES section.
John
--
PS: I don't know how to send a message back to the originator
of the bug.
On Wednesday 18 June 2003 17:52, John Gillette wrote:
> Examining the source code for v.in.dxf/find_lines.c (I
> encountered this problem with GRASS 5.0.0, but the source
> code for 5.0.2 is the same), I noted that find_lines.c
> expects all LINE and similar entities to be contained within
> the ENTITIES section of a dxf file. However, the dxf format
> allows entities to appear within the BLOCKS section as well
> (cf.: www.relief.hu/h_dxf12.html). Any lines defined outside
> the ENTITIES section will apparently be missed.
>
> I've tried one workaround ...
[snip]
Taking a quick look at the above referenced dxf site and
knowing a little about dxf, I think the problem is bigger
than just reading the BLOCKS section. It seems to me that
one must store the entity defined in the block section and
be prepared to insert, scale and rotate the stored block
(possibly multiple times) when it is later referenced in the
ENTITIES section.
I hope that this is done in v.in.dwg/5.1, at least I attempted
to handle this (recursive for AD_ENT_INSERT, transformation
for all levels).
Radim
On Wed, Jun 18, 2003 at 11:52:38AM -0400, John Gillette wrote:
PS: I don't know how to send a message back to the originator
of the bug.
Send a carbon copy to the request tracker at grass-bugs@intevation.de
and keep the bug number in the subject, ala "[bug #1950]".
Usually the replying subject is fine.
Another possibility would be to use the webinterface.