Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[sassota]

Guys, I've sent some emails to strava crew about an issue. All elevation profile recorded by GB are discarded and Strava uses their own database provided by satellite, so, there are a lot of errors. An exemple, there's a route over here that total climb are very low, maybe 500 meters total, but when I upload to strava, they considerer more than 2000 meters, just because they are ignoring elevation profile on TCX file.

Here is what I wrote and what they wrote me back:

Mat Gordon, Apr 25 09:52 am (PDT):
Hello-

Unfortunately not; there are only a few devices with elevation data that we 'trust' - and at this point there isn't a way to convince Strava to use that data from other devices.

Sorry for the trouble.

Mat
strava.com/athletes/mat_gordon
Strava Support Team


Daniel Sasso, Apr 24 11:49 am (PDT):
Hi, I'm using a Globalsat GB 580P device, it has barometric altimeter, and when I export TCX file, it contains correct elevation profle, but when I upload to Strava, it "corrects" elevation using Strava database. Sometimes when a ride is longer I can see the elevation profile recorded before the "correction" and appears to be pretty fine... Is there a way to use elevation profile on TCX file instead using your own satelitte database?

Tks a lot.

-end

Since the problem "appears" to be only "trusted" devices, Can Globalsat do something to gain their trust?

[gerhard]

You may get a workaround with SportTracks and tcxexport plugin:
http://www.zonefivesoftware.com/sporttracks/forums/viewtopic.php?f=24&t=10143&start=75