Elevation service

[RedHog]

Hi!

I was just playing around with the elevation service API and noticed a
rather important "misfeature":

If you use getElevationAlongPath, the corners of the path are not
included in the output. The output latLng:s seems to evenly spaced
along the length of the path (measured in actual distance).

So, what's the problem with that? Well, it means that you can not use
the output latLng:s to iteratively calculate their distance from the
start of the path, and end up (save for rounding errors) at the actual
distance of the path! In other words, if you where to generate a
height-curve, it's x-axis would be off.

The only rescue I've found is to use getElevationForLocations and
space out my datapoints myself, but that takes me straight into great-
circly-madness for longer path segments, and is also a rather wasteful
use of the API.

So, I guess this is directed at Google employees; if you read this,
please add an option in the next version of the API to include the
path corner points in the output sample of getElevationAlongPath, in
addition to the points returned today (the sample points).

Best regards,
Egil Möller

[Rossko]

The Issue Tracker is also intended for enhancement requests.
http://code.google.com/p/gmaps-api-issues/issues/list
If you create a request, and report it here, you may be able to gain
support for it by other people "starring" it.

[Chris Broadfoot]

Could you not calculate the total distance from the input path, rather than the output "path" (really just a list of points, not a path as such) from the service?

The result from the service is not intended for use as a path.

--
You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group.
To post to this group, send email to google-map...@googlegroups.com.
To unsubscribe from this group, send email to google-maps-js-a...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.

[Barry Hunter]

I'm guessing want to include height in the distance calculation.

will certainly get more complicated (but not impossible) for the user
trying to interpolate the heights of original points from the samples.
(Admittedly that is all Google would probbaly doing - server side :) )

On 23 November 2010 01:00, Chris Broadfoot <cb...@google.com> wrote:
> Could you not calculate the total distance from the input path, rather than
> the output "path" (really just a list of points, not a path as such) from
> the service?
> The result from the service is not intended for use as a path.
>