Join The Community

Range estimation on uneven terrain.

I've developed a range estimator webpage for hilly terrain. However before i release it for general use I need data to verify my calculations and accuracy. Here's how anyone can help since i don't have my car yet. Drive a route recording your battery capacity at some increment e.g. 5, 10 ,20 you pick(smaller is better). I'd need exact starting points and end points. To make it simple just record while on a specific road. Example below:

Start: I-90 W, I-5 interchange
End: I-90, exit 52 (Snoqualmie)
0, 220
5, 215
10, 210

Optional Info:
Average Speed
Occupants weight
Luggage Weight
Road Condition

Ryan (prelim beta app)

Hi Ryan,

I think you need to take a look at the web based app Green Race ( which provides similar information and takes into account more variables.

I did a quick comparison to some trips I made from Tucson, AZ to Tempe,AZ and back. I was able to do the trips in range more (270mi range starting). The trip is about 200 miles total. I had about 15 miles left. Traveling about 75mph. Sorry this is all the info I have.

Unfortunately, your app shows too much battery usage. Like I said, I would compare it with Green Race, which seems to be more accurate and takes regeneration on downhill into account. There are allot of factors to take into account, one of the most important ones is speed.


I drove from my house in Seattle (near Volunteer Park) to Bellingham (Sehome Village Shopping Center) and back to my house, which is pretty flat. Google Maps says the distance is 172 miles, but we made a couple of detours and stops along the way, and as I recall, the actual mileage was 180. I started with 230 rated miles and finished with 30 rated miles. I averaged around 60 mph. Our combined weight was about 360 lbs. The weather was in the low 40s, with rain, and lots of stop & go traffic on the return trip.

We expect to be driving down to the Bay Area later this month, so I will try to keep better records. Also, take a look at Chad Schwitters's chart in his long post describing the same trip:

Good luck!

I've been able to keep my daily driving to under 400 Wh/m with all of this uneven terrain. My daily driving always includes one big hill, maybe the Kennydale hill on 405, unless I choose to go around it on Lake Washington Blvd, and maybe another big hill if I decide to visit my parents. All of my other drving is also on small up and down hills.

I am keeping Trip B on the odometer, and I'm never going to reset it, so that I can always see my lifetime Wh/m. Hopefully in the future, they'll release an app that let's you see this and other deeper analysis of your energy usage.

My first week couple weeks of driving, I didn't pay too much attention to my efficiency, and I think my lifetime Wh/m was > 500. Now, I just brought it down to 400 and I'm almost at 2000 miles. Eventually, it will go lower.

Thanks all for the input and info. Visited the Green Race site, looks very similar but in KM and without seeing the battery state on the elevation deltas. Making some architecture changes to the site and improving /verifying the algorithms. AlexK, I in fact do take into consideration regen on downhills currently at 80% efficiency. I did find a bug with this and upped the regen efficiency to 90%. Thanks for the feedback and link. Next comes speed based calculations... fun.


One thing that is amusing about the Green Race application at is that it assumes that your car is submersible and takes into account the terrain under water instead of the bridge elevation.

For example, if your route takes you on a bridge across Lake Washington or the Columbia River, or on a ferry across Puget Sound it will show that you are getting lots of regen when you submerge and drive underwater. You end up using lots of your power coming up the other side as well.

@Captain_Zap | FEBRUARY 28, 2013: One thing that is amusing about the Green Race application at is that it assumes that your car is submersible and takes into account the terrain under water instead of the bridge elevation.

It uses the Google Elevation API which gives you the terrain elevation not road elevation at a given spot. It also fails on tunnels. I don't think there is a Google road elevation API. The program would have to identify the start and end of bridges and tunnels.

X Deutschland Site Besuchen