This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

GPS Data Corruption in XLS Format for Longer Measurements
(10-24-2023, 04:33 PM)Jens Noritzsch Wrote: Ok, that's weird: I have (accidentally) recorded almost one hour of data, 3k+ rows. Excel on Mac complains about the file, however, correctly reads it. Neither Numbers nor Excel on iOS report any issues… ?

The .csv export should be a safe alternative. You should check which of the formats both, Google Spreadsheet and Excel, could deal with. In Germany, just semicolon and decimal comma work out-of-the-box in Excel. The dot is used as a decimal separator in Japan, isn't it. So, likely semicolon and decimal dot could be ok…


Thank you for your helpful information.

I will check if students have saved their experiment data and try to reproduce the issue. I've spoken to 30 students, and 3 faced problems on their iOS devices. However, some could save 30-minute data without issues.

I'm looking into it, thinking it might be an iOS version issue. For the .xls file problems, reopening with iOS Numbers seemed to help. But any data corruption stops us from editing on Google Drive.

Thanks for the .csv advice. Using .zip on iPads is a bit tricky, but I'll give it a try.

I'll keep you updated. Thanks for your support.

Messages In This Thread
RE: GPS Data Corruption in XLS Format for Longer Measurements - by physken_JPN - 10-25-2023, 04:43 PM

Forum Jump: