Using CSV with XY Location Mode

[GeoffroyRicher-Lalonde]

Hello, me again 😅

Importing a CSV with the XY Location Mode, the process will fail if the columns used for X or Y coordinates are named with a special character or a space.

The columns do get new (special-character-free) names in the "attributeFields" section of the JSON, but the "xFieldName" and "yFieldName" still use the original problematic names.

Thank you !

[YujingChang]

Thank you very much for notifying us of this issue. We would like to investigate this further to provide a prompt and accurate resolution. Could you kindly provide us with some sample CSV data that exhibits the problem? This will greatly assist our technical team in their debugging efforts.

We truly appreciate your assistance and patience as we work to enhance our application.

Best，
Yujing

[GeoffroyRicher-Lalonde]

Hello @YujingChang. Of course, here is some sample CSV data.

• If you use WorkingX and WorkingY for X and Y coordinates, it will work because these attribute names do not contain spaces or special characters.
• Broken X and Broken Y won't work because of the spaces in the names.
• Broken(X) and Broken(Y) won't work because of the parentheses in the names.

Note that any attribute that is not used for X and Y coordinates can contain spaces or special characters.

[YujingChang]

Thank you for providing the details and data. This enhancement will be included in the upcoming 2.2 release, scheduled for mid-May. We invite you to use and enjoy the improved user experience.