Accept barometric altitude data from Osynce Navi2Coach

With Osynce navi2coach the elevation data was recorded by a barometric altimeter.

Please can you add this device to your list of devices with barometric altimeter to stop the automatically elevation correction done by Strava?

4

Comentários

14 comentários
  • I second this request.

    The o_synce navi2coach is a serious competitor to the Garmin Edge 500 and RideWithGPS already supports its barometric altimeter.

    0
    Ações de comentário Permalink
  • I asked for the same in April, and here's the response I received:

     

    Sheila Fretwell, Apr 03 11:28 AM:
    Hello Antti,

    I completely understand your point and the good news is that Strava does have plans to integrate with more devices in the future. I can't provide any specifics or dates at the moment but we appreciate your input and interest. Please feel free to check back with us for future updates.

    Regards,
    Sheila
    Strava Support Team
    0
    Ações de comentário Permalink
  • I find it odd that Strava does not to accept valid barometric altimeter data from other bike computer manufactures such as O-Synce, Polar, SRM, Sigma, etc... Those are well-known products used currently by many pro tour cycling teams.

    As a paid Strava Pro customer, I also find it odd that my valid and accurate altitude data first gets uploaded successfully to the service, is shown correctly there for a while, only to be discarded and replaced by inaccurate guess data just because it was not recorder by a certain device manufacturer (Garmin). And I can't even choose to revert back to the original data, even though it exists there.

    Shouldn't be hard to start accepting other manufacturers' altitude data, since it clearly is understood by Strava, and even shown for a while?

    0
    Ações de comentário Permalink
  • I agree. I also wrote to Strava a couple of times about this and their suggestion was to put add this as a feature suggestion:

    ```

    We do continually add barometric support for other devices so please post your suggestion in our community forums. We use these forums to consolidate and collect feedback from our community so if there is enough interest, it may be something we put on the roadmap.

    ```

    Didn't sound too promising, but worth a try.

    0
    Ações de comentário Permalink
  • I guess we can only keep asking. It's the squeaky wheel principle :-)

    For me, the better support for the o_synce navi2coach by RideWithGPS was a reason to become a paying subscriber of that service while staying with the free service at Strava.

     

    0
    Ações de comentário Permalink
  • I asked the same question for TomTom Sportwatch. Unfortunately I don't think it has priortity. https://strava.zendesk.com/requests/292474

    0
    Ações de comentário Permalink
  • I just noticed, as of last Friday: Strava now recognizes the Navi2Coach, and its barometric data.

    0
    Ações de comentário Permalink
  • Yes, I can confirm that: On my latest Strava upload (152 km with 1329 m of climbing), the total elevation gain shown by Strava exactly matched the value tracked by the Navi2coach.

    Thank you, Strava!

     

    0
    Ações de comentário Permalink
  • As fas as I can see, this stopped working some weeks ago, which is very bad. Any reason for this ? Any chance to get it working again (as it was for years now) ?

    1
    Ações de comentário Permalink
  • @Uwe St, unfortunately you appear to be right. For example, my Sunday ride was listed with 2758 m of elevation gain (https://www.strava.com/activities/1199227366). On the device itself it was showing with less than 2500 m.

    Breaking barometric elevation support on the Nev2Coach removed one of the advantage of Strava over RWGPS.

    0
    Ações de comentário Permalink
  • For me, this change includes 2 more annoyances: I have to change every ride from training (or how it is called in english) to bike ride and, whenever I expect to have some PRs or similar, I have to click on recalculate awards to see them. I opened a bug report for this, but til now I only got 2 automated messages, telling nobody found the time for it. It looks like they only care for premium members.

    0
    Ações de comentário Permalink
  • Yes, it's still reporting the wrong altitude: A recent ride Strava reports 15,304ft whereas device reported 13,044ft (more accurate).

    https://www.strava.com/activities/1242170580

    I've put in a support ticket. Let's see what happens.

    0
    Ações de comentário Permalink
  • Do you also share my other problems:

    - Every ride has to be manually changed from training to bike ride

    - Every ride with PRs and similar only shows them after calling the recalculation of awards

    Btw I received an answer from Strava in the meantime: They changed the fit file parser and o_synce would need to build an update to be compatible with the new version ;-(

    0
    Ações de comentário Permalink
  • Yes, every ride I upload defaults to a Workout, not a ride, even though Cycling is set as my default activity type in the Profile.

    I think I've had once case where no segments were matched at all when I upload as the new default activity type (Workout) and then changed the activity type later. I needed to request the recalculations as you say.

    A change of the fit parser is a weak excuse for getting the workout type wrong. All uploads are clearly tagged as coming from a "O-Synce navi2Coach", which after all is a cycling-specific GPS, not a wrist watch, so they should be able to easily figure that one out.

     

    0
    Ações de comentário Permalink

Por favor, entrar para comentar.

Não encontrou o que estava procurando?

Nova publicação