Feedback on Trips Tab
Joe, I just had a chance to try out the Trips functionality (0.25.00) during a trip between Bay Area and Sacramento via the new Vacaville Supercharger (pics
here) and it is fantastic. I had a few feedback items and questions (plus future requests):
1) I notice occasionally getting a "glitch trip" consisting of two data points a few feet from each other and zero mileage. I know the heuristics on your trip determination must be quite complicated. One thing you might consider adding is a "glitch rejection" that rejects trips below a certain distance, to exclude in particular 0 mi or km.
2) For many trips spread over days and months, it would help to find them if you indicated the days that contain trips with some alternate coloring in the calendar, for example shading either the day box or number differently. This would enable quick picking of trips. It also adds functionality to your new ability to highlight multiple days and see all the trips within that range (the current workaround for quickly finding trips).
3) Also for quicker visual id of trips, since there is room in the upper right box listing trips, it would be useful to put one other summary item after <date> @ <time>. I suggest <distance><unit>, the difference between Odo at end vs start. This will also add value to your new ability to highlight a range of trips there and map them, so you can more easily pick them out by distance traveled (also helps reject the glitch trips without needing to highlight each one and check the fields).
4) Since there is now room in the tab where you have the graphic, it would be useful to have additional "average" values placed on the page when you highlight each trip. I think the most useful averaged values for each trip would be, based on the data collected already, the average power, average speed, (and perhaps average battery current). This requires doing an off-line average of data on each trip, but from number of points collected, should be quick.
5) Finally on data export and altitude/location data. I tried the export location data but I get a binary file and could not find out more info on its format in the docs. I have a suggestion that I think will make this a killer feature that also solves the altitude requests by many. Also for me, I would like the altitude data very much to quantify energy usage and help estimate altitude impact on range. In the export (perhaps even after selecting the trip or trips you want in the list), my suggestion is have a button to export, but use KML format. It appears you have all the data to do this to make the XML-type file. In addition, during the export, my suggestion is to look up the altitude for each data point from the general topo databases (see, e.g., KML on wikipedia). This format then has all the capability of holding the markers, their orientation, GPS coordinates, and even the time information (not currently used in your google map visualization), etc., and then these KML files can be used in Google Earth or host of other mapping programs to visualize and analyze. In the KML file I believe you could even export all the recorded data during the trip as custom fields, such as instantaneous speed, power, etc. that is seen in your "graphs" tab, but now not directly linked with "trips". The KML format is a standard and seems to be a great way to combine the car metrics and location data into a powerful visualization tool.