[GRASSLIST:528] Re: v.in.dxf updated

[Huidae Cho]

On Fri, Mar 31, 2006 at 12:19:06PM +0200, Radim Blazek wrote:
> On 3/31/06, Huidae Cho <grass4u at gmail.com> wrote:
> > Hi,
> >
> > I have updated v.in.dxf to support LWPOLYLINE and TEXT objects.  LWPOLYLINE was
> > introduced after DXF R10, so the chance is good that newer DXF files will be
> > imported.
> >
> > One problem with TEXT is that the module actually creates points and attaches
> > text labels through the "label" field in the linked table.  Created tables will
> > have two fields: cat (integer), label (varchar(256)) and TEXT will be stored in
> > the label field.  Since the label is actually not a graphic object in this
> > case, rotation of text and the label box (cannot determine the dimension of
> > label) are not supported.
> >
> > Linking labels and objects is not implemented.
> 
> It could be useful to have all the properties of elements imported to the table
> You can look into the v.in.dwg for example, it creates table with
> 
>  cat integer,
>  entity_name varchar(20),
>  color int,
>  weight int,
>  layer varchar(100),
>  block varchar(100),
>  txt varchar(100)

v.in.dwg imports all objects into one layer and use "d.vect where=" to display
some of them.  Then what is the layer concept for?  Actually, having multiple
layers (tables) in the current v.in.dxf can easily mess up dbf/ directory if
one does not use a real database.  What do you think is the best approach to
this problem?

Huidae Cho


> 
> That is useful because many people use colors for example to distinguish
> layers.
> 
> Radim
>