Which scenario requires the user to set geometry manually with a GeometryCoercer?

Which scenario requires the user to set geometry manually with a GeometryCoercer?

• A. The format automatically uses the geometry of the first feature
• B. The format supports multiple geometry types in a single writer feature type
• C. The format lacks a Geometry parameter and requires manual geometry
• D. The format is non-spatial

Answer: (C)

The situation is about having to provide the feature geometry yourself because the target format doesn’t expose a geometry parameter. When a writer doesn’t define a Geometry parameter, the workspace must create or assign geometry for each feature rather than it being carried through from the input. In that case you would use a transformer like GeometryCoercer to set or build the geometry from attributes or coordinates, ensuring the writer gets a valid geometry even though the format itself doesn’t supply one. If the format automatically uses the geometry of the first feature, you rely on incoming geometry rather than constructing it yourself, so manual geometry isn’t needed. If the format supports multiple geometry types within a single writer feature type, you still have geometry to work with or coerce, but it isn’t a case of lacking a geometry parameter. A non-spatial format has no geometry to set at all, so the scenario described doesn’t apply there.

The situation is about having to provide the feature geometry yourself because the target format doesn’t expose a geometry parameter. When a writer doesn’t define a Geometry parameter, the workspace must create or assign geometry for each feature rather than it being carried through from the input. In that case you would use a transformer like GeometryCoercer to set or build the geometry from attributes or coordinates, ensuring the writer gets a valid geometry even though the format itself doesn’t supply one.

If the format automatically uses the geometry of the first feature, you rely on incoming geometry rather than constructing it yourself, so manual geometry isn’t needed. If the format supports multiple geometry types within a single writer feature type, you still have geometry to work with or coerce, but it isn’t a case of lacking a geometry parameter. A non-spatial format has no geometry to set at all, so the scenario described doesn’t apply there.