The overall export file structure for both projects
Let us have a look line by line.
The first line – identifies the type of the file. The file content itself follows it. Do not touch this line.
### CE
Lines starting with ### – are header lines followed by the data structures which are defined as follows:
### preferences info
### vehicle info
### fuel_type info
### records info
### money_type info
### pattern info
### expenses info
After the header line the lines with the mandatory data fields description follow. Field names are fixed and can not be changed. Names, like the fields are separated by an invisible symbol – tabs (Tab). Spaces are not taken into account. After the header row and the row with the field names follow the data lines. The fields must be filled in – even if not used – spaces are allowed.
Now, about the meaning of the fields.
### preferences info – field application settings
- calc_rest_period – the period for fuel calculations, 0 – daily, 1-after record input
- calc_costmil – how many kilometers for route cost calculation
- date_format – date format (0 – 25.02.2015, 1 – 02.25.2015, 2 – 2015.02.25, 3 – 2015.25.02)
- date_separator – date separator in the [] brackets
- money_round – the number of decimal places for the money values
- digit_round – the number of decimal places
- digit_separator – decimal separator character in [] brackets
- digit_thou – thousands separator of a number – for example 1’000 rubles – a thousand rubles
- show_dlg_exit_app – show whether the exit dialogue should be displayed (true – yes, false – no)
- show_fuelprice – specify whether the price of fuel refills should be listed or not
- show_consumption_true – for those who are in the subject (which show the flow rate)
- home_visible_button – deprecated
### vehicle info – Transport options
- name* – name, key field, which then binds all the records in the file (shorter is better)
- comment – a comment
- avatar – symbol number (0-15)
- mileage_unit – distance unit (0 – км, 1- mile)
- volume_unit – volume unit (0 – litre, 1 – gallons US, 2 – gallons UK)
- volmil_unit – consumption units (0 – l / 100 km, 1 – l / km, 2 – MPG US, 3 – MPG UK)
- currency_unit – currency symbol
- currency_order – where to draw the currency symbol (0 – before value, 1 – after value)
- tank_volume – Fuel tank capacity
- calc_method – deprecated
- tank_rest – residue in the tank at the checkpoint
- mileage_method – how to add the mileage by default (0 – odometer, 1 – distance)
### fuel_type info – Fuel Options
- name – Name (shorter is better)
- parse – transfer through; keyword, which can identify the type of fuel – is looked at in the parsing comments
- tank_numb – Number of tank
### money_type info – Additional fields for currency
- name – Name
- unit – Currency sign (shorter is better)
- order – where to draw the currency sign (0 – before value, 1 – after value)
- equal – Example 55 rubles is one dollar, here we write 1
- equal_orig – and here 55
### records info – Field records for petrol records
- id_vehicle – the name of the vehicle, to which the record is bound. A record must match the name in the list of auto transport
- date – the date in the format 20150225 (yyyyMMDD)
- note – record note
- mileage – mileage (integer value)
- volume – the volume of fuel filled in (real value – 5.467)
- volumecost – the cost of one unit fuel (real value – 35.467)
- cost – cost of refueling (real value – 1235.467)
- type – the name of the fuel (must match the name in the list of fuels – settings)
- full – deprecated
- mark – type of record – the complete list is here
- costmileage – route cost (a derivative of the field can be left blank)
- mileagevolume -Reverse flow (a derivative of the field can be left blank)
- volumemileage – fuel consumption (a derivative of the field can be left blank)
- mileageadd – the difference from the previous record (a derivative of the field can be left blank)
- tankvolume – residue in the tank, if known
- latitude – Latitude (not yet used)
- longtitude – Latitude (not yet used)
###pattern info – field patterns of spendings
- _id – a unique pattern number – is used in the list of records of expenses
- name – template name
- avatar – Template icon (+ 0..42)
- id_category – cost category template (1 – planned, 2 – unplanned, 3 – maintenance, 4 – tuning, 5- income 6 – fuel and lubricants)
- period_type – Frequency type (0 – nothing, 1 – every n distance, 2 – every n-th month, 3 – earliest occurrence of 1/3/4/5, 4 – once with n mileage, 5 – once at a date
- period_mileage – the same after every n mileage in integers
- period_month – the same after every n months in integers
- period_mileage_once – the best once after n mileage in integers
- period_date_once – this is the date for “once” in the format 20150225 (yyyyMMDD)
- period_last_mileage – last known path for this template (a derivative of the field can be left blank)
- period_last_date – the last known date for this template (a derivative of the field can be left blank)
- period_future_mileage – the projected path for the future of this pattern (a derivative of the field can be left blank)
- period_future_date – Future target date for this template (a derivative of the field can be left blank)
- event_show – whether to show this pattern reminders in the list of events (1 – yes, 0 – no)
### expenses info – fields for expenses
- id_vehicle – the name of the vehicle, to which the record is bound – must match the name in the list of auto transport
- id_pattern – a unique pattern number – must match the pattern number from the list
- avatar – Icon ID (0 … 42+)
- date – the date in the format 20150225 (yyyyMMDD)
- mileage – Distance (integer value)
- name – Name (shows all)
- note – note of recording
- costpart – cost of parts (real value)
- costwork – cost of work (real value)
- latitude – Latitude (not yet used)
- longtitude – Latitude (not yet used)