Autodesk AutoCAD Map 3D Object Data Writer Parameters

File Options

Specify the AutoCAD release that will be compatible with the output file.

Template File

A template file is an AutoCAD file that defines layers, line styles, blocks and shape definitions which are referenced during translation. This option allows you to define the template file by entering a template filename or browsing to a file location.

Note   Template files are also known as prototype files.

This parameter can be used to allow the file specified in the Destination Autodesk AutoCAD File parameter to be written as the concatenation of the Model Space contents of the file specified by the Template File parameter with all written data.

  • No (default) – Only header information is used from the template file if one is specified. No Model Space entities are used.
  • Yes – The full header and Model Space entities are used from the template file.

This parameter can be used to allow the file specified in the Destination Autodesk AutoCAD File parameter to be written as the concatenation of the Paper Space contents of the file specified by the Template File parameter with all written data.

  • Yes (default) – The Paper Space entities are used from the template file if one is specified.
  • No – The Paper Space entities are not used from the template file.

Spatial

Coordinate systems may be extracted from input feature data sources, may come predefined with FME, or may be user-defined. FME allows different output and input coordinate systems, and performs the required coordinate conversions when necessary.

How FME Processes Coordinate Systems in the Workspace

If a coordinate system is specified in both the source format and the workspace, the coordinate system in the workspace is used. The coordinate system specified in the source format is not used, and a warning is logged. If a source coordinate system is not specified in the workspace and the format or system does not store coordinate system information, then the coordinate system is not set for the features that are read.

If a destination coordinate system is set and the feature has been tagged with a coordinate system, then a coordinate system conversion is performed to put the feature into the destination system. This happens right before the feature enters into the writer.

If the destination coordinate system was not set, then the features are written out in their original coordinate system.

If a destination coordinate system is set, but the source coordinate system was not specified in the workspace or stored in the source format, then no conversion is performed. The features are simply tagged with the output system name before being written to the output dataset.

For systems that know their coordinate system, the Coordinate System field will display Read from Source and FME will read the coordinate system from the source dataset. For most other input sources, the field will display Unknown (which simply means that FME will use default values). In most cases, the default value is all you'll need to perform the translation.

You can always choose to override the defaults and choose a new coordinate system. Select More Coordinate Systems from the drop-down menu to open the Coordinate System Gallery.

Changing a Reprojection

To perform a reprojection, FME typically uses the CS-MAP reprojection engine, which includes definitions for thousands of coordinate systems, with a large variety of projections, datums, ellipsoids, and units. However, GIS applications have slightly different algorithms for reprojecting data between different coordinate systems. To ensure that the data FME writes matches exactly to your existing data, you can use the reprojection engine from a different application.

Note  To use this feature, you must have a supported GIS application installed on your system (for example, Esri ArcGIS®).

To change the reprojection engine, Select Workspace Parameters > Spatial > Reprojection Engine. In the example shown, you can select Esri (but the selection here depends on your installed applications):

For more information, see the links below:

Advanced

The application name that is used when writing extended entity data.

  • Yes (default) – Only those attributes defined as part of the layer definition will be stored.
  • No – Most feature attributes (except those that start with autocad) are stored.

Specifies the folder in which to look for shape files (*.shp) from which information about SHAPE entities will be extracted for writing. For more information, see Shapes.

The names of blocks created by the writer during automatic block creation.

This parameter may be used to specify a prefix for block names that are created by the writer during automatic block generation. Automatic block generation occurs for features written with aggregate and other geometries which are best represented by block entities.

This parameter is only used when Use the Block Name to Create Blocks parameter is set to No, and is not used for features that already have an autocad_block_name attribute specified.

The names of created blocks will take the form:

<Block Name Prefix>_<blocknumber>

Coordinate System Storage

This parameter controls whether the writer will optionally store the coordinate system of its features. The coordinate system can be stored in the following ways:

  • None – Projection information is not stored anywhere.
  • External PRJ – Externally in a companion Esri .prj file that shares the output AutoCAD file's base name, but has a .prj extension.
  • Internal Native – Internally using the native Coordinate System storage which will be recognized by the native AutoCAD application.
  • Internal WKT – Inside the output AutoCAD file as Esri Well-Known Text (in an ESRI_PRJ entry in an internal dictionary in the file), according to Esri specifications.

AutoCAD data files written this way with projection information will be recognized by FME and the ArcGIS for AutoCAD application, which installs on top of the AutoCAD application.

Toggle purging of unused objects or entities before the final drawing file is written out.

Unused objects are those which are not referenced by other objects in the drawing. For example, for a layer to be eligible to be purged, there must be no entities on that layer.

If set to Yes, the AutoCAD writer will attempt to purge the following object types:

  • Blocks
  • Layers
  • Detail View Styles
  • Dimension Styles
  • Groups
  • Linetypes
  • Materials
  • MLine Styles
  • MLeader Styles
  • Registered Applications
  • Section View Styles
  • Table Styles
  • Text Styles
  • Visual Styles

This parameter can be used to change how donut geometries on features with autocad_entity attributes not set to autocad_hatch or autocad_mpolygon, are represented as AutoCAD entities.

If this parameter is set to Yes, and a donut is planar, then it will be written as a hatch entity. Donuts with three dimensions will only be written as hatches if they have a constant Z value, which can be stored as the hatch elevation.

If a donut is not oriented in the XY plane, then the feature must have autocad_extrusion_x, autocad_extrusion_y, and autocad_extrusion_z attributes set which indicate the normal vector direction, orthogonal to the plane of the object. If not, the hatch may have Z values dropped, to force it into the XY plane.

If this parameter is set to No, or a donut is not planar, then that donut will be handled like a multi-area geometry, and will be written as a block.

Write block object data to

This parameter can be used specify how an FME feature with composite geometry (such as those with fme_geometry type of fme_aggregate or fme_donut) will store its attribute information as object data.

  • Insert:  This is the default value. It indicates that object data will only be stored on the insert entity (block reference) that will be created from the composite geometry.
  • All: This value indicates that copies of the object data will be stored on the insert as well as on every entity part that is created within the block definition. This is a good option if the insert will later be exploded into parts and object data is desired on each part.
Note   In an AutoCAD-to-AutoCAD translation, if insert entities in the source dataset are not exploded, this parameter is not applicable to that insert data, because it is not stored as FME features with composite geometry.