If the CSV or Excel reader does not automatically identify geometry fields, is it possible to identify them manually?

If the CSV or Excel reader does not automatically identify geometry fields, is it possible to identify them manually?

• A. True
• B. It is sometimes possible
• C. It can be done manually
• D. False

Answer: (D)

In this scenario, the capability being tested is whether you can manually designate which fields should be treated as geometry when the CSV or Excel reader doesn’t auto-detect them. In FME, if the reader doesn’t automatically identify geometry, there isn’t a built-in option to map specific columns to geometry inside the reader itself. Geometry must be created after reading, using downstream transformers (for example, converting coordinates with XY to Point, or converting a WKT string with a WKT-to-Geometry transformer). Because manual geometry-field mapping isn’t supported directly in the reader, the idea of doing it manually within the reader isn’t possible. That's why the correct stance is that it cannot be done manually.

In this scenario, the capability being tested is whether you can manually designate which fields should be treated as geometry when the CSV or Excel reader doesn’t auto-detect them. In FME, if the reader doesn’t automatically identify geometry, there isn’t a built-in option to map specific columns to geometry inside the reader itself. Geometry must be created after reading, using downstream transformers (for example, converting coordinates with XY to Point, or converting a WKT string with a WKT-to-Geometry transformer). Because manual geometry-field mapping isn’t supported directly in the reader, the idea of doing it manually within the reader isn’t possible. That's why the correct stance is that it cannot be done manually.