|
|
The
following spreadsheet shows an example of the format used for the
import/export to the MileageMeter Blackberry application

- Row 1 contains '0' which defines the field separator to be a comma.
- Row 2 contains the column titles. These are just
to help when entering the data. MileageMeter ignores these rows. There
can be multiple of these rows in the file.
- Row 3 contains the car name. This means that all
of the following fill-ups until the next car name (rows 4-15) belong to
the car 'toyota'
- Row 4 contains a typical fill-up with complete information
- Row 16 contains the name of another car. This means, that the fill-ups of row 17-28 belong to the car 'honda'
- Row 17 contains a fill-up with miles and gallons as units. You can mix multiple units in one data file.
- Row 18 contains a fill-up, where the date is unknown.
- Row 23 contains a fill-up, where the date, refill amount and price are unknown
- Row 26 contains a fill-up, where the date and the
odometer reading are unknown. Even so no mileage data can be calculated
for those "unkown" re-fills they are important, because otherwise the mileage
data of the following entry is incorrect.
Saving the above spreadsheet as 'csv-text-file' will result in the following:

The format used for the import/export to the MileageMeter Blackberry application follows these rules:
- The data has to be stored in a table with seven columns.
- The
first row has to have only an entry in the first column. All other
columns have to be empty. This entry informs the MileageMeter
application which field separator you will be using. Please ensure,
that you will save the file with the same field separator as provided
in this field. The following values are allowed for the entry in the
first column:
- '0' - in case the file will be saved with ',' (= comma) as the field separator
- '1' - in case the file will be saved with ';' (= semicolon) as the field separator
- '2' - in case the file will be saved with '|' (= ASCII character 124) as field separator
- The
seven column titles 'Date, Odometer, Odometer unit, Re-fill
Amount, Re-fill unit, Price per unit, Full refill' can be in as many
rows as needed. These rows are just to help when
entering the data and are ignored by the MileageMeter application
during the import.
- Above any rows containing fill-up data there
has to be a row containing the car's name. The car's name has to be given
in the first field of the row and all other fields have to be empty.
- The fill-up data in the rows must be stored in seven fields using the following syntax
- Date: Can contain three different kind of values:
- The date of the refill in the format MM/DD/YYYY
- No data (in case the row contains a fill-up with at an unknown date but a known odometer reading)
- The
word 'unknown' (in case the row contains a fill-up with an unknown date and
odometer reading. In this case also the odometer field has to contain
the word 'unknown')
- Odometer: Can contain three different kinds of values
- The odometer reading at the time of the refill. This must be the total odometer and not the trip odometer!
- No data (in case the row contains a fill-up with an unknown odometer reading but a known date)
- The
word 'unknown' (in case the row contains a fill-up with an unknown date and
odometer reading. In this case also the date field has to contain
the word 'unknown')
- Odometer unit - Can contain two different kind of values
- km - if the odometer reading is given in the unit km
- mi - if the odometer reading is given in the unit miles
- Re-fill Amount - Can contain two different kind of values
- The amount of the re-fill
- No data in case of a fill-up, where the amount is unknown
- Re-fill unit - Can contain two different kind of values
- l - if the refill amount and the 'price per unit' are given in liter
- gal - if the refill amount and the 'price per unit' are given in US gallons
- Price per unit - Can contain two different kind of values
- The price per re-fill-unit for the fill-up
- No data in case of a fill-up where the price was unknown
- Full refill - Can contain two values
- TRUE - If the tank was filled up completely during the re-fill
- FALSE - If the tank was not completely filled up during the re-fill
(c)
thinkOmatics 2008-09
Contact
us at support@thinkomatics.de
|