-
Notifications
You must be signed in to change notification settings - Fork 120
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
Export data by Torque #57
Comments
Yes, there is an export function to json or csv. |
By the app or autmatically in another way? |
And can I extract this data in an automated way (i.e., without going through app or web app)? |
Not sure what you mean, this whole thing is a couple of components. The torque app is it's own thing, and the author has his own web server solution and storage, I don't know of any automation within that. This project is an API-compatible alternative web server for uploading the torque data to a place you own. With that, you have access to the DB and could construct something to extract things on a schedule, or you could tweak the upload code to trigger the existing export routine when a session is complete. Session completion is a bit tricky to detect though; it's a setting in the torque app when to generate a new session, but there's no "this session is over" event. Basically the app says "we made a session, and are uploading data to it! If the car stops generating data for more than x minutes, call it a new session!" It could make sense to have some nightly php cronjob to say "look for sessions yesterday, then trigger the export function on those to a folder" but you'd have to figure it out, it's not part of this per-se, storing to the DB is where the automation ends. Does that make sense? |
Yes, I think so. I saw your repo about Torque and I think that I need to implement my web server to upload my raw data on my database automatically. |
I need to work with raw data and analyze it on my PC. Can I download, by Torque, data in one of the common formats (csv, json, xml, etc.)?
Thank you in advance!
The text was updated successfully, but these errors were encountered: