Welcome to the e-mission Documentation!¶
There are some specialized READMEs in the individual repositories, but they are gradually being moved in here. This means that if you have any questions, you should first search here and if you don't find any existing issues, you should file an issue here.
- e-mission web site
- CODE on GitHub
- LICENCE BSD-3
- Thanks to @PatGendre from FabMob, you can now Read The Docs
What is e-mission¶
E-mission is an open source mobility platform developed at the RISE and BETS labs in the UC Berkeley EECS Department.
E-mission includes a mobile application for Android and iOS, with user consent, automatically collects the user's travel patterns and sends them to the server so as to derive personal mobility information and analyses; depending on user consent for sharing his/her data, the data can also be used for aggregate mobility data studies. The application is also a tool for collecting information filled in by the user (such as incidents, ground truth information about his/her trip purpose and transportation mode, or answers to questions asked in external surveys).
The server is a python web application, the data is stored in a mongoDB database; the client is a Cordova application for both Android and iOS.
The application has been initially designed to be reused in research and academic projects either for conducting and as a good learning project for CS students. It is also freely reusable for any other user cases. If you are using e-mission in your work, please submit a PR, or send email@example.com an email so that you can be added to this list.
e-mission was the first open source mobility platform, with the initial versions created in 2016. Itinerum, the only other open source mobility platform, was developed much earlier, but only open sourced in 2018. e-mission and Itinerum have applied for funding to merge in 2020 and are both members of the Project Management Committee. As far as we know, the merged project will be the only open source mobility platform.
End to end apps¶
@PatGendre generated this list of closed source apps that are similar to e-mission. Since Patrick is from France, they have a strong European focus. If you would like to add other companies to this list, please send a pull request.
Although e-mission is an end-to-end system, it is also modular. The sensing components are cordova plugins and can be incorporated into any app. The server modules are open source and should be able to process any data in the correct format. All the deployments so far, with the exception of UW, have focused on customizing the custom app UI and have not really modified the plugin list. If you are interested in experimenting with plugin subsets, I am happy to work more closely with you. Please also let the community know how it goes. @PatGendre also generated this comparative list of background location tracking SDKs. If you would like to add other SDKs to this list, please send a pull request.
|Itinerum||Open source||app, not SDK. will merge in 2020, pending funding|
|TransistorSoft Background Geolocation||Closed source||Much richer set of interfaces, including react native and flutter|
|Sentiance||Closed source||Includes trip and mode detection|
|Radar.io||Closed source||the API seems to be limited to geofences, focused on retail?|
|LocoKit||Open source||iOS only, "ML based"|
|moprim||Closed source||no public documentation|
Gallery (a first glimpse at the app UI)¶
E-mission has been reused in several projects, here are short videos showing different versions of the UI, which have been presented at the last TRB conference in January 2020 :
- E-mission provides personal mobility metrics including CO2 emissions (MeCO2 a CO2 coach developed in Berlin by DFKI's OSLab)
- E-mission can let the end-user complete the mode and purpose after trip completion
- E-mission can embark third-pary online surveys (a feature developed by the University of New South Wales)
- E-mission can be adapted to mobility nudge experimentations like the Tripaware project conducted at UC Berkley in 2018
- E-mission can be integrated with external survey tools by automatically filling in survey fields with sensed information. The survey prompt can even be context sensitive.
Read these papers for understand context.
- TRB paper describing how to use e-mission functionality
- The in-review paper on the e-mission architecture, please do not distribute
- e-mission started as Shankari's PhD thesis
- A proof of concept of user private clouds in @njriasan's thesis
- A proof of concept for differentially private queries aggregating information over UPC in @jackcsullivan's thesis