Import reference with first column corresponding to coordinate

[Paulo]

Hello,

I have noticed that when I try to import a CSV reference file with first column corresponding to a coordinate (X, Y or Z) then after importing such file, the first coordinate of first row defaults to 0.0000 which is erroneous.

In first capture I show import CSV dialog where first column corresponds to Longitude.

In second attachement, I show markers after import, first marker has longitude equal to 0   .... should be 25.3726347356

[Alexey Pasumansky]

Hello Paul,

I am not able to reproduce this problem in latest 2.3.0 release version. Can you share the text file used as an attachment?

[Paulo]

Hi Alexey,

here is the csv file giving me the errneous first coordinate...

[Alexey Pasumansky]

Hello Paul,

It seems that there is an invisible symbol in the beginning of the first line that causes the problem.

See what is shown, if you read the lines from the file using Python:

Code: [Select]

['п»ї25.3726347356,37.1101675384,9.783,3\n',
'25.3722896688,37.1101742422,7.875,1\n',
'25.3723613019,37.1103212426,9.212,2\n']

[Paulo]

Thank you for the info, Alexey.

These CSV files were produced by Global Mapper using export CSV and does seem that it produces an invisible character at beginning of first line.... so it seems a problem

[Alexey Pasumansky]

Hello Paul,

Maybe that first symbol is BOM? Is there an option to choose encoding when you export csv file?
For example, Notepad++ allows to encode to UTF8 withot BOM, maybe in Global Mapper you can also select this encoding for output?

[Paulo]

Hi Alexey,

yes, when I disable the option Use UTF-8 Encoding for Text Values
in export CSV (global mapper), the special character is no longer present in first line...