That is because the "range" and the "energy use for this route" are two different things. Really you -always- want the latter but people seem to think that it can be simplified to the former, it just can't.
Spherical cows in a vacuum and all of that.
Telsa puts a bunch of work into estimating energy use for a given route using elevation data etc, it's why they have their own route planner (that you can also tweak the behavior of).
From memory the only thing that goes into the "range" calc is current temperature, it otherwise just has to assume averages for everything else without knowing the route a priori.
Spherical cows in a vacuum and all of that.
Telsa puts a bunch of work into estimating energy use for a given route using elevation data etc, it's why they have their own route planner (that you can also tweak the behavior of).
From memory the only thing that goes into the "range" calc is current temperature, it otherwise just has to assume averages for everything else without knowing the route a priori.