crenninger wrote:
I would agree this would be great.
alternatively, maybe allow the data to be loaded on Fuelly.com instead. maybe linking the account or something like that.
thx
christian
I agree, Fuelly import would be good.
Here is what the columns need to be
The first row of your CSV file must contain column names, outlined below. The data for each column should be separated by commas and match the following types:
odometer (Required for odometer trackers)
Your odometer reading as number with up to one decimal place.
miles or km (Required for tripometer trackers)
The distance traveled as a number with up to one decimal place.
gallons or litres (Required)
The fuel volume as a number with up to three decimal places.
fuelup_date (Required)
Date of Fuel-up in this format: YYYY-MM-DD or M/D/YY.
price (Optional)
The price/gallon or price/L as number less than 15 with up to three decimal places.
notes (Optional)
Text up to 500 characters.
tags (Optional)
Up to 15 keywords separated by spaces with up to 50 characters/tag. English characters only.
missed_fuelup (Optional)
A bit field (1 = yes, 0 = no) for odometer trackers that lets Fuelly know a fuel-up reading was missed.
partial_fuelup (Optional)
A bit field (1 = yes, 0 = no) that lets Fuelly know a fuel-up was not completely full.
