When writing to Esri Shapefile with geometry set to fme_any, which outcome occurs?

When writing to Esri Shapefile with geometry set to fme_any, which outcome occurs?

• A. Fail if more than one geometry type.
• B. Create a single output shapefile with geometry set to the first output feature, and then ignore any features with a different geometry type.
• C. Create a separate shapefile for each type of geometry encountered, and append the geometry name to the shapefile name.
• D. Create shapefiles named for each geometry supported by FME, even if those shapefiles end up being empty because there were no features with that geometry.

Answer: (C)

Shapefile storage constraints require one geometry type per file, so when you write with fme_any, the writer distributes features by their geometry type instead of forcing them all into one file. The result is a separate shapefile created for each geometry type encountered, with the geometry name appended to the base shapefile name to distinguish them (for example, a shapefile for points, another for lines, another for polygons). This approach preserves all features and keeps each output file compatible with the shapefile format. It only creates shapefiles for geometry types that actually appear in the data, so there won’t be empty shapefiles for types that aren’t present.

Shapefile storage constraints require one geometry type per file, so when you write with fme_any, the writer distributes features by their geometry type instead of forcing them all into one file. The result is a separate shapefile created for each geometry type encountered, with the geometry name appended to the base shapefile name to distinguish them (for example, a shapefile for points, another for lines, another for polygons). This approach preserves all features and keeps each output file compatible with the shapefile format. It only creates shapefiles for geometry types that actually appear in the data, so there won’t be empty shapefiles for types that aren’t present.