• DXFVEC: DXF files import

DXFVEC 0: CONTENTS INFORMATION: Shows a list of the DXF file contents. It reports the number of polylines, lines, arcs, ellipses, circles, solids, points, texts and blocks, broken down by layers. For blocks, each layer lists the names and the number of blocks with that name.

DXFVEC 1: DXF LINES, POLYLINES, ARCS, ELLIPSES, CIRCLES AND SOLIDS WILL BE TRANSFORMED TO VEC LINES OR POLYGONS. If the program detects that all polylines are closed, either in the DXF definition or because the extreme coordinates are identical, it documents the entities as type "polygon"; otherwise as type "line". The layer of the entity becomes the attribute in the VEC file. The number of vertices in a polyline is practically unlimited. The program uses the command-line tolerance to convert arcs, circles and ellipses to polylines. Tolerance is the maximum allowed error when translating DXF arcs, circles and ellipses to VEC polylines (maximum distance between the arc and the chord). Later DXF versions (AutoCAD 2000) allow curvatures between polyline vertices; tolerance also applies to those objects. If 0 is given, the number of vertices is limited to one per degree. Tolerance can only be given in option 1.

DXFVEC 2: DXF POINTS WILL BE TRANSFORMED TO VEC POINTS. The layer name of the entity becomes the point attribute in the VEC file.

DXFVEC 3: DXF TEXTS WILL BE TRANSFORMED TO VEC POINTS WITH TEXT AS ATTRIBUTE. The entity text becomes the point attribute in the VEC file.

DXFVEC 4: DXF TEXTS WILL BE TRANSFORMED TO VEC POINTS WITH LAYER NAME AS ATTRIBUTE. The layer of the entity becomes the point attribute in the VEC file.

DXFVEC 5: DXF BLOCKS WILL BE TRANSFORMED TO VEC POINTS. The block name becomes the point attribute in the VEC file.

DXFVEC 6: DXF LINES, POLYLINES, ARCS, ELLIPSES, CIRCLES AND SOLIDS WILL BE TRANSFORMED TO ARC OR POL FILES, AND POINTS, TEXTS AND BLOCK INSERTION POINTS WILL BE TRANSFORMED TO PNT FILES. A MiraMon Map (MMM) file will be created to group all the new layers.

• CONTENTS INFORMATION:
  Shows a DXF contents enumeration. It presents the number of polylines, lines, arcs, circles, ellipses, solids, points, texts and blocks splitted by layers. Inside block context, for each layer it appears the name and the number of blocks with this name.
• DXF LINES, POLYLINES, ARCS, CIRCLES, ELLIPSES AND SOLIDS WILL BE TRANSFORMED TO VEC LINES OR POLYGONS.
  If the application detects that all the polylines are closed, either in the DXF file definition or by detecting that the extreme coordinates are equal, it will document the objects as being of type "polygon"; in the opposite case it will document them as of type "line".
  Layer that contains the entity becomes attribut in VEC file.
  The number of vertex in a polyline is almost unlimited.
  The application takes parameter tolerance from command line to convert arcs, circles and ellipses to polylines. Tolerance is the maximum permited error when translating DXF lines and circles to VEC polylines. (maximum distance between arc and chord). The last versions of DXF format (AcadCAD 2000) allows you to define curvatures between the vertices of a polyline object. The tolerance also applies in these objects. If a 0 is indicated, the number of vertex is limited to one for degree. Tolerance is only used in option 1.
• DXF POINTS WILL BE TRANSFORMED TO VEC POINTS.
  The name of the layer that contains the entity becomes point attribute in VEC file.
• DXF TEXTS WILL BE TRANSFORMED TO VEC POINTS.
  Entity text becomes point attribute in VEC file.
• DXF TEXTS WILL BE TRANSFORMED TO VEC POINTS.
  Layer that contains the entity becomes point attribute in VEC file.
• DXF BLOCKS WILL BE TRANSFORMED TO VEC POINTS.
  Block name becomes point attribute in VEC file.
• DXF LINES, POLYLINES, ARCS, CIRCLES, ELLIPSES AND SOLIDS WILL BE TRANSFORMED TO ARC AND POL FILES; POINTS, TEXTS AND BLOCKS INSERTION POINTS WILL BE TRANSFORMED TO PNT FILES.
  A MiraMon Map file (MMM) will be created to group all new layers.

For options 1 to 5, the application allows to restrict entities to convert to those with numerical attribute, rejecting those with alphanumerical attributes. In case of choosing only numerical attribute entities, the rounding of non numerical attributes can be forced. These 5 options allows 8 entity filters:

ALL LAYERS ENTITY FILTER (entity filter 1):

Converts all the entities of a determined typed (line, point, etc.) being in all the layers that have a name compatible with the chosen type. If output attribute type is restricted to numerical integer values, only DXF file layers with integer attribute will be converted (except in the case of text type entities with text as attribute and when is the text that gives the attribute and not the layer, so that it must be integer). The application will keep this value as attribute of the VEC file vectors and will ignore entities situated in layers with non-integer names (an advise will be shown by console when incompatible or rounded attributes exist).

ONE LAYER ENTITY FILTER (entity filter 2):

Converts all the entities of a determined typed (line, point, etc.) being in a certain layer that can have as a name an alphanumerical attribute. The application allows to change the attribute of the converted entities (except in text options with text as attribute and blocks, where layer name is only used to filter, and the converted attribute is the own text or the block name). The application converts layer name (or the text string to search) to a numerical attribute or user defined alphanumerical.

SEVERAL LAYERS ENTITY FILTER (entity filter 3):

Allows to choose layers and changes to be performed on the attributes of entities converted to VEC. This selection is read from a file of equivalences. The application will usually convert to capital letters text strings that give name to layers, since DXF format keeps the names in capital letters; however, some software (for ex. A/I) do not respect this rule and may write names using small letters. Therefore DXFVEC offers the chance of NOT performing the conversion. Also you should take into account that accentuated letters (capital or small) can not be translated nor compared with the non-accentuated. This entity filter can also be used to extract several layers from a DXF file without the need to iterate many times with the one layer entity filter (entity filter 2); in this case layer name must be equal to the equivalence name in the file of equivalences. See the example below.

ONE TEXT ENTITY FILTER (entity filter 4):

This entity filter has sense only for texts and blocks. Permits extracting only DXF texts or blocks with the specified text or block name. In case of options 3 and 5 substitute text will be requested.

SEVERAL TEXTS ENTITY FILTER (entity filter 5):

This entity filter has sense only for texts and blocks. Permits extracting only DXF texts or blocks with the text or block name specified in a file of equivalences. As in the former case, if it is required the text or block name will be replaced by another equivalent attribute.

ALTIMETRY ENTITY FILTER (entity filter 6):

Assigns the attribute of each entity from the Z coordinate of the first vertex of each DXF file entity.
Only valid for entities of type polyline, line and point.
Entities from all layers are transformed.

ALTIMETRY LAYER ENTITY FILTER (entity filter 7):

Equal to the former, but only elements specified in an equivalences file will be extracted.

BLOCK DESCRIPCION ENTITY FILTER (entity filter 8):

The previous filters read the entities from the ENTITIES section in the DXF file. On the other filters of the application, and when using blocks, these are extracted with the option 5 as points. Nevertheless, every block presents a geometric description in the BLOCKS section of the DXF file. In some cases it may be interesting to extract every single block description in a VEC file (usually in a 'plane' reference system). This description can be used to generate an EMF that in MiraMon can be associated to points obtained using option 5. Through this way, you get a more faithful visualization. This description could be used to generate an EMF file that, in MiraMon, could be linked as a symbol to the point in the point file obtained with the option 5 and get a better view on MiraMon.

Text_or_bloc_layer_name_1
Substitute_equivalent_name_1
Text_or_bloc_layer_name_2
Substitute_equivalent_name_2
     .
     .
     .
Text_or_bloc_layer_name_n
Substitute_equivalent_name_n
...

GENERAL NOTES ABOUT VEC FILES RESULTS:

1. VEC files are ASCII and compatibles with Idrisi software. However, Idrisi does not recognise (at least until v. 4.1) neither attributes of type "string" nor attributes of type "integer" that contain values of type "long" (greater than 32767 or lower than -32768).
2. VEC files, when used in Idrisi, even with version 4.x, can give problems if they a zero as attribute.
3. Vector-binary Idrisi files have 4 bytes of precision (6-7 significant digits), so, keep in mind when using "CONVERT V" that you can lose precision. We recommend working always with VEC files of type ASCII. MiraMon only supports VEC ASCII files.
4. The VEC format can be structured by topology by using other MiraMon tools (VECPNT, Linarc, etc).

Import/Export tools for vector files: