Git Product home page Git Product logo

yunsolutions / levin-opendata Goto Github PK

View Code? Open in Web Editor NEW
25.0 8.0 4.0 228 KB

At Yuñ Solutions, we are committed to democratize technology and make information accessible to all. We are sharing the data collected from our proprietary OBD device (LEVIN) during beta testing. The shared data has been collected for almost 4 months on 30 cars.

License: MIT License

Jupyter Notebook 100.00%
accelerometer-data magnetometer gyroscope obd2 driving-behavior car automotive automobiles digital-signal-processing iot

levin-opendata's Introduction

LEVIN-Open Data

LEVIN Vehicle Telematics Data

Current version: v1.1

Owner – Yuñ Solutions

Data Updated – 10th Feb 2018

What is it?

Yuñ Solutions is an India based start-up with its head office in Pune. We are into IoT domain where we collect data about driving and vehicle using our flagship product LEVIN. At Yuñ Solutions, we are committed to democratizing technology and make information accessible to all.

The data is collected using various sensors. The accelerometer sensor gives us insights on acceleration and deceleration, magnetometer tells us about the direction w.r.t earth’s magnetic field and gyroscope gives us insight about rotation.

What is OBD?

On-board diagnostics (OBD) is an automotive term referring to a vehicle's self-diagnostic and reporting capability. OBD systems give the vehicle owner or repair technician access to the status of the various vehicle subsystems.

OBD-II is an improvement over OBD-I in both capability and standardization. The OBD-II standard specifies the type of diagnostic connector and its pinout, the electrical signalling protocols available, and the messaging format.

About Dataset

The dataset provided here is a sample data for data we collect real-time. This dataset is collected for over a 4 month period on approximately 30 4-wheelers. We collect OBD data at 1Hz frequency (1 record per second) while accelerometer data is collected at 25 hz (25 data points per second)

This metadata includes – Device Id, timestamp, trip id, accelerometer data, speed gathered from GPS, battery voltage, coolant temperature, diagnostic trouble codes, engine load, intake air temperature, manifold absolute pressure, calculated mileage, mass airflow, engine RPM, speed collected from OBD, timing advance, throttle position and magnetometer data.

The full data set is available as

  1. A Single CSV and another Single CSV with more obd parameters

  2. A Single SQLite3 Database

  3. A Single Compressed Zip with individual CSVs

  4. Individual CSVs This link will be updated monthly from now onwards

How to use

The dataset can help in various kind of analysis including,

  1. Driving patterns

  2. Gear Detection

  3. Events like hard brakes, hard acceleration, sharp turns and lane changes

  4. Impact detection

Since, dataset contains data collected at different frequencies, it can a task to combine them and use them together. The dataset contains accelerometer data in raw format, to make sense of the data and convert it to usable format, please refer to data_extract.ipynb file.

More about Yun

Website - www.yun.buzz

More about LEVIN

webpage - levin.yun.buzz

LEVIN Vehicle Telematics Data by Yun Solutions is licensed under Creative Commons BY-NC-SA License.

levin-opendata's People

Contributors

katphlab avatar manasimehrotra avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

levin-opendata's Issues

Missing function in detect_gear.ipynb file

In the detect_gear.ipynb file there a function to calculate the borders called "get_segment_borders", but is missing in the notebook, could you include it please or explain how to calculate the segment of the borders please?

Kind Regards.

Variable `psi` is not used in "data_extract.ipynb"

In the cell 'Calculating Rotation Matrix for vehicle', the variable psi is not used, if it is not necessary maybe that line could be removed.

However if it should be used in the equations below, maybe there has been a typo (phi/psi)?

It is quite important to know because if the case is the latter, then rotation results would be wrong.

Thanks.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.