In databases, date-time is usually stored as the number of seconds past the beginning of 1970, rather than a text string. Then, that date-time data is displayed according to the local or requested text format.

Yeah I have suggested to turbo3 using epoch time as a more universal timecode. It removes any ambiguity.

I plan on making the "trips" more flexible at some point in the future. Right now it just checks for a gap in time of more than 20 minutes. So for 2 log points more than 20 minutes apart it assumes this is a new "trip".

kevinleaf wrote:Yeah I have suggested to turbo3 using epoch time as a more universal timecode. It removes any ambiguity.

I plan on making the "trips" more flexible at some point in the future. Right now it just checks for a gap in time of more than 20 minutes. So for 2 log points more than 20 minutes apart it assumes this is a new "trip".

tried to view latest file upload and its listed in options for selecting trips but not populating any data so i tried viewing previous uploads that worked fine before and they are showing nothing either?

Was just testing the viewer with a log using the latest Leaf Spy Pro test version 0.29.21 which supports background logging.

I started up Leaf Spy Pro on the phone then put the phone to sleep and put it in the glove box just before my wife went out this morning.

When she got back I thought I would edit the csv file so it would just have today's trips. Big mistake. I used excel to read the file in then deleted the earlier entries then resaved as csv. When I uploaded it to Leaflogger the samples were only every minute not the every 3 seconds that were in the original log. Problem was that default excel date/time only shows minutes not down to seconds so when it wrote the file out again it stripped off the seconds information.

I ended up just using a text editor to modify the csv file and delete the earlier entries. However, when I re-uploaded to Leaflogger it made no difference. The new data would not replace the old bad data. I had to go in and change the date to make it finally display the data with full resolution.

We really need a way to delete bad uploads or the app should not try to filter and keep old data if the new data is different.

Thanks for doing that test Jim. That is a good reason for allowing deletion of trips. I need to add a lot of trip-related features and the ability to treat trips as a thing onto their own, which will allow things like deleting, naming trips, tagging trips (like "To Work", "From Work" to make it easier to show all trips of a certain type together) and sharing trips. Coming soon!

For now let me know if you have a bad upload that I need to remove from the database. It takes me just a few minutes to do this deletion manually.

kevinleaf wrote:Thanks for doing that test Jim. That is a good reason for allowing deletion of trips. I need to add a lot of trip-related features and the ability to treat trips as a thing onto their own, which will allow things like deleting, naming trips, tagging trips (like "To Work", "From Work" to make it easier to show all trips of a certain type together) and sharing trips. Coming soon!

For now let me know if you have a bad upload that I need to remove from the database. It takes me just a few minutes to do this deletion manually.

The bad uploads are the 3/25/2014 ones. I re-dated them to 3/26/2014 (tomorrow) to get the new good ones in.