The Shapefile writer processes the DATASET, DEF, and MEASURES_AS_Z directives as described in the Reader Directives subsection. It does not make use of the IDs or SEARCH_ENVELOPE directives.
The ENCODING directive is used to specify which character encoding should be used when writing text attributes into shapefiles. If the value of this directive is not set, the current OS language is used. The syntax of the ENCODING writer directive is the same as the ENCODING reader directive, as described in the Reader Directives section.
UPPER_CASE_ATTR_NAMES
This option specifies whether the writer should change attribute names to uppercase text. If set to NO, mixed-case attribute names will be allowed. The default value is YES.
Note: This directive is used when generating workspaces and mapping files. As a result, it is not editable within Workbench after the workspace has been generated.
Workbench Parameter: Not applicable.
STRICT_COMPATIBILITY
This option specifies whether the writer should write shapefiles that are compatible with other products by taking a stricter interpretation of the specification.
This directive is used when executing workspaces and mapping files. As a result, it is not editable after the workspace has been generated.
Values
YES | NO
The default value is YES in all generated workspaces. Omission of this option implies NO.
Workbench Parameter
Strict Compatibility
PRESERVE_RING_VERTEX_ORDER
This advanced option specifies whether the writer should:
- preserve the order of the vertexes within the rings of polygons and donuts of input features (Yes), or
- force ring vertex order to be compatible with the format specification by orienting the ring vertexes to identify inner and outer rings and allow disambiguation of aggregates and donuts (No).
Note that ellipses are stroked into polygons with counterclockwise orientation and thus also may be affected by the option to not orient the rings properly as clockwise according to the specification.
Note also that because the vertex order is the only mechanism to distinguish between donut and aggregate geometry types when there are multiple polygon rings that the type may not be the same when read back if the input vertex order is preserved but does not match the input geometry type vertex order requirements.
The safest setting for this advanced option is to leave it at the default value of 'No'.
Values
YES | NO
The default value is NO in all generated workspaces. Omission of this option implies NO.
Workbench Parameter
Preserve Ring Vertex Order
SURFACE_AND_SOLID_STORAGE
This option specifies whether the writer should write input 3D surfaces and solids as shape_multipatch to preserve their original structure or as 3D shape_polygon to break them down into polygon components. The default value is multipatch.
Note: This directive is used when generating workspaces and mapping files. As a result, it is not editable within Workbench after the workspace has been generated.
Workbench Parameter
Not applicable
WRITE_SPATIAL_INDEX
This option specifies whether or not to generate spatial index files when writing shape files. Writing the spatial index files requires that ArcGIS be installed and licensed on the machine running the workspace.
Note: If any attributes are flagged for indexing, spatial indexes are produced regardless of this setting. For more information, see User Attributes
Values
Yes | No
The default value is No in all generated workspaces. Omission of this option implies No.
Workbench Parameter
Write Spatial Index
MEASURES_AS_Z
This Navigator parameter controls how measure data associated with geometric data is treated. The default is No, which preserves the measures on the features. If Yes, measure data is treated as elevation values, and the existing z values are overwritten with the measure values, if they exist.
Workbench Parameter
Treat Measures as Elevation