more decimal latitudes out of range

[klausriede]

No idea how this latitude out of range affects map display, but it is definitely wrong. Should be easy to check for latlongs out of range.

Ephippigerini DcW https://orthoptera.speciesfile.org/otus/841663/overview

[mjy]

@klausriede thanks for exploring the DwC!!

[LocoDelAssembly]

@klausriede what system locale are you using in Windows? Spanish?

Looks good at my end using LibreOffice Calc in Ubuntu:

I think although I have the OS in English language, locale is Spanish (Argentina), but I think Calc ignores and interpretes period as decimal separator rather than thousands separator.

[klausriede]

ah ok, strange that only some values are corrupt. In any case did you check ranges?

[LocoDelAssembly]

Because if following a period there are not exactly 3 digits then it is not assumed to be thousands separator and cell becomes text type (notice alignment is different in your capture for those coordinates that were not messed up).

I believe georeferences are checked both by TW and database system. Don't remember what happens with verbatim lat/log, but DwC is probably validated? @mjy

[mjy]

There is a corresponding taxonworks issue IIRC, but yes, when we export values to DwC then we use Georeference values that may not appear the same as the verbatim IIRC.

[klausriede]

Does this mean that the respective field has no datatype declaration?

[klausriede]

ANOTHER outofrange case from nemobiinae csv, using

[klausriede]

...and bingo, correct in CSV