It rejected my data if I didn't convert the unix timestamp numbers in to something more human readable.

Did you then import successfully? Or was there an error thrown specifically about the timestamp initially and that was then not thrown? Please be as specific and detailed as possible.

these forums are tossing things I added...???

I added an example of what I used that worked to my previous post...

this is the Unix time stamp format that didn't work for me.

1219177554

I made a little PHP program to spit out the dates like this.

2008-09-19 14:43

it worked.

I don't know why the forum would have done anything to your post; I certainly didn't.

That's a nice little program you wrote. Still, you didn't answer my questions about how you *know* the issue was your timestamp. You indicated you knew it wasn't accepting the timestamp but didn't explain how you know; I'm very interested because I don't believe a specific error about timestamps is thrown... or maybe I just don't recall having seen it.

I don't remember the exact message I got. only that after I submitted my data with the Unix time to see if it would take it, it came back and said it didn't like it. somehow... sorry I don't remember exactly how. I'm going to attach a small chunk of my data so you can play with it.

1197411404,Jeep,111554.6,20.944,1,3.139,65.74,87
1201039747,Jeep,111801.5,20.429,1,3.059,62.49,87
1203370747,Jeep,111988.6,21.812,1,2.979,64.98,87
1206736610,Jeep,112207.6,20.683,1,3.479,71.96,87
1210538089,Jeep,112341.6,12.859,1,3.759,48.34,87
1212438566,Jeep,112627.0,22.276,1,4.059,90.42,87
1216153427,Jeep,112858.2,21.857,1,4.359,95.27,87
1219177554,Jeep,113102.5,21.111,1,3.839,81.05,87

Thanks. I've pinged the developers to see if it's a remotely easy fix.

I don't know what your import engine is running on, but since these forums are on PHP I can imagine that may also be. I used the PHP Date() function with these settings to spit out the human readable version that was accepted.

date("Y-m-d H:i", $stamp)

I have read through the entire 10 pages of this thread and would like to ask if the issue with importing fields with no data has yet been tackled? (import fails because a field is empty)

I have just started using Gas Cubby within the last fortnight, and I am currently unable to import a CSV file with about 4 yrs worth of data (fuel purchases, mileage etc) because the importer refuses to import fields in an optional column (cost per litre) as some of the cells are occasionally blank because I didn't have the cost per litre info at that time.

I don't want to enter 0.0 as this will skew the graph data. Is there a character that can be inputted so that the importer & grapher ignore the empty cells?

Thanks. Great looking app so far.

Would you show me some of your data? I'd like to see a mix of lines that are complete along with those that are not. 10 lines should suffice.

Sure, I'll send it through when I get home.