Why do some formats have writer feature types without a Geometry parameter?

• A. They automatically set geometry to the first feature they receive.
• B. They require the user to set geometry using a GeometryCoercer.
• C. They set geometry type based on a proprietary dynamic definition algorithm.
• D. They support multiple geometry types in a single writer feature type, or they do not support any kind of geometry (i.e., non-spatial formats)

Answer: (D)

When a writer feature type has no Geometry parameter, it signals that the target format either doesn’t store geometry at all or can contain more than one geometry type within the same feature type. In FME, geometry is tied to spatial formats, but some outputs are non-spatial (tabular formats) or can carry different geometry types for different features. Without fixing a single geometry parameter, the writer accommodates those cases. That’s why the correct idea is that such writer feature types either handle multiple geometry types in one writer feature type or do not support geometry at all (non-spatial formats).

Other descriptions don’t fit because a writer isn’t automatically assigning geometry to the first feature, nor does it require a GeometryCoercer, and there isn’t a proprietary algorithm that determines geometry type for this scenario.