PriusChat Mileage Database - ideas and input for features needed!

[jammin012]

An ADHOC query function so you can create reports/graphs using the data points you choose.

And how about sending a beta test out to 10 or so people so we can break it and see what works and what doesn't before the final program hits the street. Would hopefully get away from Hypermiler v 8.6.3

[TheForce]

Database needs the option to add a gas station brand. This way when we get lots of data we might be able to see if gas brand has an effect on MPG. There will need to be an option for users to insert their own store brand for those mom and pop places or just stick to the major brands and have the option for "other".

[JimboK]

Originally Posted by samiam

2. it is important to use the correct model information. Outside of North America, the current model is known as Gen III. This is important because in NZ and the UK there are a number of "true" Gen I's sold.

This is an excellent point. I was confused when I first started learning about the Prius' model history. These days I always use the Toyota model numbers when differentiating: NHW10, NHW11, and NHW20. If there is to be a model distinction in the database, I suggest this method. This eliminates ambiguity.

[PaulHS]

I think a choice of general terrain conditions would be helpful. FE for mountainous is not likely to be equivalent to flat terrain.

Paul

[dwreed3rd]

Originally Posted by PaulHS

I think a choice of general terrain conditions would be helpful. FE for mountainous is not likely to be equivalent to flat terrain.

Paul

Perhaps an inclination gauge and data logger.

Please, I'm just joking. I hope that I did not offend anyone. A couple of my past hats were worn in Product Planning & Development. Just a reminder that if you try to please everyone you may end up with something really great but no one will use it. I suggest a core of required fields/data that are nessessary to be meaningful with optional data for extended queries. I think this is a great project and in no way want to discourage it. Just be careful, I've seen function kill projects. It's got to be user friendly, intuitively easy to use, not time consuming to enter and perhaps have file import/export capabilities to live beyond initial enthusiasm, some of which has been mentioned in previous posts.
Good luck. I really think it is a great idea.
BTW, I am actually thinking of getting or making an inexpensive inclination gauge, to have an idea of what the actual slope of some of these hills are in the metro Atlanta area. And I had run across data loggers while googling for a remote temperature sensor to put in the HV battery compartment so that I could monitor the temp back there. It just came together and popped out when I read your post. No dis-ing intended.

[bwilson4web]

If there is some desire to rank or give titles to exceptional mileage, I would caution against it. When I got my NHW11 03 Prius, I was on the verge of getting my "hypermiler" star at the minimum mileage, 3,000 miles in January 2006. But I noticed my very first tank from Ft. Worth to Shreveport LA was the problem. I had driven the car from the dealer without modifications. So I asked about taking it out and a chorus of voices said, 'Oh no, we need the mileage records for research." So I kept the first record and three weeks later, got my "star" just as Wayne left to form CleanMPG.

Unfortunately, the "hypermiler" star was based upon USA EPA numbers and the political EPA moved the goal posts last year. Furthermore, it doesn't handle plug-in, ethanol or non-gasoline fuels very well.

My thinking is any mileage 'ranking' should follow a statistical definition, something based upon standard deviations. Furthermore, it should be either by time or distance. If time, use the last year. If distance, use the last 6,250 miles / 10,000 km. This removes external scales, like USA EPA ratings, that can change. Either one works as a moving window to recognize a person's learning curve and changes in technology and fuel.

To some extent, people who live in less hybrid-friendly areas are playing a 'handicap.' I don't have a good handle on how to handle handicaps except to record average trip distance, terrain and temperature. It may be possible with a large collection of records to come up with a 'handicap' formula. There is a practical use for mileage records, especially recent values.

Often a problem with a car, a potentially expensive problem, can be detected when the mileage seems to drift down. Caught early, this can be fixed and mileage return. It can also lead to planning more extensive repair work, scheduled, to minimize down time. For me, keeping these car running in good health is good news for all.

Bob Wilson

[efusco]

Danny,

Temperature - my intention is to make those fields optional. What would be really cool is if you could put in how long your tank lasted, then the system could go backwards from your fill-up date and use the Zip Code to pull in average temperature data. I'm not sure if there are any APIs out there for weather data, though.... hmmm.

This can probably be auto-populated.
1)The start date is the day the previous tank was filled (in the database). The end date would be the date entered for the current tank.
2)For location you've got the zip code (would start/end zips be good or the ability to enter multiple zip codes for those tanks where multiple highway trips were taken??)

Here's the best site/recommendation I've seen, I don't see any reason the programmer couldn't get this to be part of the process or to automatically open another window during data entry that would be automatically populated with the zip and time range.

Turns out there's a nifty little tool there that lets you put in custom dates and it will report the weather averages (including max, min, and mean for highs, lows, and daily mean) and precipitation for your city. Here's how:

1) Go to www.wunderground.com, enter your ZIP code, and hit enter.
2) When your city comes up, scroll down a little to the "History and Almanac" box.
3) Enter the beginning date of your tank in the drop-downs there and click Go.
4) The history for that date should appear. Below the date entry boxes, click "Custom."
5) Enter the end date of your tank and click Go. (The beginning date should be retained.)
6) There it is -- the weather almanac and history for the entire length of your tank.

[Son of Gloin]

i've just read through the entire thread - today's the first time i noticed it! - and i BELIEVE the following four items have not yet been mentioned or suggested:

1 -- an optional data "box" to indicate whether a driver is using "regular" or "synthetic" oil ....

2 -- an optional data "box" to indicate estimated percentage of "city" and "hi-way" driving for each fill-up ( especially useful, i believe, on those occasions that people happen to be making lengthy trips ).

3 -- also, especially for the above-mentioned lengthy trips, an option for indicating average speed driven might be helpful when it comes to collecting / interpreting data ....

4 -- an optional data "box" to indicate the air pressure of the tires ....

if i missed seeing any of the above suggestions in an earlier post, i apologize for the redundancy.

[Dozzer]

How about adding the current odometer reading.. see how the mileage differs over the age of the car.

A graph like this would be nice: http://www.greenhybrid.com/compare/m...-priushsd.html

But with the option of conversion to imperial gallons, maybe both on the graph...Us./Imp

[dwreed3rd]

O.K. I've scanned throught the thread's post several times and unless I'm missing it, I believe there is a significant variable missing. It's at least as significant as tires pressures, E10 vs regular, and oil change overfills. It's load weight! The amount of weight/load above curb weight has a significant affect on MPG. Whether it's a 100lbs of sales manuals in the back, a passenger(s) or a spare tire around your waist, it DOES have a significant affect on gas mileage. I realize this could be, well actually is, a touchy subject and some members could be reluctant to supply the data. Perhaps a generic load weight that is "weight above curb weight" that is in no way defined. This way it could be driver only, include passenger or passengers, add-ons. mods, that 100lbs of sales manuals, etc. and the driver's weight could be kept private. Well perhaps a load weight of 98lbs could be considered " driver only". The point is over 100lbs could mean anything. The point is that if the point is to compare miles per gallon, if would be self defeating to ignore one of the more significant if not major variables affecting the MPG that could be included. That said, this mpg thing has given me additional inspiration to lose some extra weight, not only for health purposes, but an improvement in mpg will be an additional benefit.