Exported Data File format Feature Request

dewittpayne · Post by **dewittpayne** » Sun Dec 11, 2016 9:31 pm

Currently, the exported data log has multiple lines with the same time stamp. It would be much more convenient for post processing and decrease file size if those lines were combined so there were no duplicate time stamps.

Post by **brentp** » Mon Dec 12, 2016 4:26 pm

Our CSV file format is sparsely populated for minimum file size to minimize repeated data. We report the log file time stamp in UTC milliseconds and also an interval counter also in milliseconds.

If you can upload a sample log file and point out what line number we should look at we can check it for anything wayward. A suggested upload site is http://dropcanvas.com if you're not sure what to use. Thanks!

dewittpayne · Post by **dewittpayne** » Mon Dec 12, 2016 10:21 pm

https://dl.dropboxusercontent.com/u/91578766/trip.log

some rows with the same time stamp after importing into Excel are 5,6,7,8 utc 1481314555831

26-35 1481314556292

45-72 1481314556652

There are lots more. These rows are empty of data except for AccelX, Y ,Z, pitch, roll and yaw. The data in these columns for the same time stamp are identical.

I have the logging rate for the accelerometer and gyro data at 50Hz.

Post by **brentp** » Tue Dec 13, 2016 2:17 am

Thank you, that's very helpful. I took a look at it and it seems like a bug in the export.

Do you have the file explorer on your android device? if so, can you find the datastore.sq3 file? If you can find it that would be good to have for troubleshooting. Not super critical, I think we might be able to reproduce it as well.

dewittpayne · Post by **dewittpayne** » Tue Dec 13, 2016 2:33 am

It's iOS, not Android. I first posted in the iOS beta app thread, but you asked for it to be moved here. It may actually be a bug in the iOS beta app. Here's the file courtesy of iBrowse:

https://dl.dropboxusercontent.com/u/915 ... astore.sq3

Post by **brentp** » Tue Dec 13, 2016 2:36 am

Thanks, this will help. Actually hoping it's not iOS specific, as that would be very a very strange problem. Nonetheless, I'll see what info this yields.