What happens when a writer feature type receives data with geometry that is different from the schema, and the destination format does not support multiple geometry types?

• A. The writer writes the features with different geometry types
• B. The writer sets the geometry type back to a fixed value
• C. The writer drops the features instead of writing them
• D. FME automatically changes the schema source to point to another dataset

Answer: (C)

When a writer is targeting a format that supports only a single geometry type, FME enforces that constraint at write time. Each feature’s geometry must match the writer’s configured geometry type; if a feature arrives with a different geometry type, it cannot be written to that destination and is dropped from the output. This ensures the destination remains valid for that format.

To handle data with multiple geometry types, you’d split or route the stream by geometry type (or convert geometries so they all match the required type) and write each subset with the appropriate writer. The other options would require a writer that supports multiple geometry types or explicit schema changes, which doesn’t happen automatically.