Kate Bauer

Cost2Drive is a tool that estimates the cost of ur trip for your driving destination (particularly beneficial now that snowboarding season has arrived and weekend trips have become much more prevalent.)

A couple of things:

- there is no persistance of data for the car data and let’s be honest, how many different cars does a person really own?? the persistence of data should reflect the more frequent use-case scenario which im thinking is probably one-car-per-person. even when there is more than one car involved, there is usually ‘the one’ for trips (aka the one w/the rack on top)

- the address data must be super precise (i had to re-enter my cities a few times because it wasnt exactly postal-quality)

- i wanna see the formula used for this estimation. does it take into account the various gas stations between the destinations (more precise perhaps) or use a national average and multiply that number instead or something else

 - a friend of mine plugged in some numbers (he drives much more often than i do) and challenged the accuracy

- i want more feedback, like what are the emissions stats and how does that compare to a hybrid and what alternatives are available to cut cost and emissions (besides flying, which they do suggest for my mt snow scenario)

I give it an A for concept; version 2.0, however, might want to reflect a bit more accuracy and take into consideration some of the same variables that googlemaps, yahoo and mapquest have had to consider in their mileage approximations.