Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Import data (Fuelly) #11

Closed
tiemonl opened this issue May 31, 2021 · 13 comments
Closed

Import data (Fuelly) #11

tiemonl opened this issue May 31, 2021 · 13 comments
Labels
enhancement New feature or request

Comments

@tiemonl
Copy link

tiemonl commented May 31, 2021

Fuelly currently supports exporting data as a CSV, would it be possible to have an import functionality? I would love to transition to using this instead of Fuelly.

@akhilrex
Copy link
Owner

akhilrex commented May 31, 2021 via email

@tiemonl
Copy link
Author

tiemonl commented May 31, 2021

I can do that, I'll get around to it later today and send it your way.

@akhilrex akhilrex added the enhancement New feature or request label Jun 1, 2021
@tiemonl
Copy link
Author

tiemonl commented Jun 1, 2021

Fuelly Export.csv

Here's an export, I don't have that much data in there as I haven't used all the features. Hopefully someone else could provide another export if they have more data than I can provide

@poisonthescene
Copy link

Fuelly Export 2.csv

I'll also provide an export in case you need more to work with. About a year and a half of data.

@kavemang
Copy link

I have a dataset from mid 2014 to now which includes the time the android app was called "acar" from before the merge with fuelly, let me know if another set would help, going to try migrating to this as soon as csv import is possible

@akhilrex
Copy link
Owner

This has been done. Just rebuild the container with the latest image and it should be available to you.

@kavemang
Copy link

kavemang commented Jul 7, 2021

sorry to bother about this @akhilrex , is there a guide on proper format to be used in each field?

I'm having an issue with unmapped vehicle error, even though I have it with the same nickname on Hammond as the fuelly car_name field

Also am not able to get the date_added field to work due to a date/time format error

@akhilrex
Copy link
Owner

akhilrex commented Jul 7, 2021 via email

@kavemang
Copy link

kavemang commented Jul 7, 2021

car_name, model, l/100km,  odometer, km, litres, price, city_percentage, fuelup_date, date_added, tags, notes, missed_fuelup, partial_fuelup, latitude, longitude, brand
**Renegade**,Jeep,18.71,186886,306.998,57.432,1.269,50,06/06/2021 **0:00,06/06/2021**,,,0,0,,,
Renegade,Jeep,22.46,186579,248,55.695,1.279,50,04/25/2021 0:00,04/25/2021,,,0,0,,,
Renegade,Jeep,22.31,186331,270,60.245,1.159,100,03/30/2021 0:00,03/30/2021,,,0,0,,,
Renegade,Jeep,23.72,186061,219.997,52.186,1.159,50,03/03/2021 0:00,03/03/2021,,,0,0,,,
Renegade,Jeep,28.65,185841,177.993,51.001,1.049,50,02/13/2021 0:00,02/13/2021,,,0,0,,,

I have bolded what I think are the issue columns

@kavemang
Copy link

kavemang commented Jul 7, 2021

For the vehicle I have added in hammond I do not yet have any entries but the nickname field is definitely "Renegade" with no ending or leading blanks on either side

@jcgoette
Copy link

jcgoette commented Jul 8, 2021

I think the issue is there are two different ways to export data from Fuelly and they seem to be in different formats.

The way built into Hammond currently is from aCar app, but there is also https://www.fuelly.com/index.php/car/<make>/<model>/<year>/<username>/<id>/export/fuelups.

@kavemang
Copy link

kavemang commented Jul 8, 2021

I think the acar app requires premium to export directly from within the app, ironically I had the pro version before they merged with fuelly and was never able to fix my version back to pro

@VeganBiker
Copy link

Looks like they only work for acar exports not fuelly exports

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants