-
Notifications
You must be signed in to change notification settings - Fork 53
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
Comments
Can you please attach an exported CSV file which I can study and take
forward. You can replace all the identifying information with dummy data.
Having Real world historical data would really speed up the process.
Thanks and Regards
Akhil Gupta
…On Mon, 31 May 2021, 7:09 pm Liam Tiemon, ***@***.***> wrote:
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.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#11>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEMVPRZVN4EFB3H4RBC4PTTQOGSPANCNFSM4525HWOA>
.
|
I can do that, I'll get around to it later today and send it your way. |
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 |
I'll also provide an export in case you need more to work with. About a year and a half of data. |
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 |
This has been done. Just rebuild the container with the latest image and it should be available to you. |
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 |
Can you share a few rows from the CSV that are giving an issue? Make sure
you copy them using a text editor and not excel.
Thanks and Regards
Akhil Gupta
…On Wed, 7 Jul 2021, 6:32 am kavemang, ***@***.***> wrote:
sorry to bother about this, is there a guide on proper format to be used
in each field? I'm having an issue with the vehicle not being
identified/matched even though I have it with the same nickname on Hammond
and also am not able to get the date/time of entry to work due to a format
error
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<#11 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEMVPX4F3HLD4HK7R7DNZTTWORSVANCNFSM4525HWOA>
.
|
I have bolded what I think are the issue columns |
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 |
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 |
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 |
Looks like they only work for acar exports not fuelly exports |
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.
The text was updated successfully, but these errors were encountered: