One reason at least;

DXF Headers are useful for importing multiple Autocad layers (from a single
DXF file) into different Mapinfo .TABs (I'm sure it's the Header section
that tells Mapinfo what layers to expect). -  If you really want layer-name
as an attribute, import your DXF file into multiple tables, , add a
layer-name variable to each .TAB, then combine your tables.

DXF files output by other programs tend only to have the Entities section
and can seem somewhat simplistic but a true Autocad DXF file is a thing of
beauty (in a nerdish, anorak kind of way).

e.g. The Entities section of a DXF file holds font information as a
font-code and size: the DXF Header stores all the other text font details
(so that it is only written once, not once for every text-object).  Look at
a MIF file with "Font ("Arial",1,0,0)" writen for each text-object - this
could be a single character in a DXF file.

Don't do DXF's down, it's just that Mapinfo isn't all that good at using
the information that's in there!


Brian Forrester

Entities - anything drawn in Autocad, i.e. lines, text, symbols etc.

Previous Message......

MapInfo needs full header section , but why?

None of the programs exports data to DXF properly as much as I know,
DXF  is very stupid and lots of things are messed

So header section should be IGNORED by MapInfo to read full content and
there should be some checkboxes to sotre layer name as an attribute, .

DXF also misses CAD attributes such as color etc..

Beside MIF is a super exchange format ..

To unsubscribe from this list, send e-mail to [EMAIL PROTECTED] and put
"unsubscribe MAPINFO-L" in the message body, or contact [EMAIL PROTECTED]

Reply via email to