FitContributor - Is the data recognised by 3rd Party Sites? eg: Trainer Power

Before I dive into looking at fit contributor, was wondering if anyone here have any info on how the data will be parsed into the FIT file.
Basically I just want to contribute data for my Dumb Trainer by converting speed to power based on the trainer's power curve.

I want to be able to just emulate an actual power meter and have it fed into the FIT file.

From the top of my head and reading the forums, I think this is NOT doable. (it won't be a drop-in) in that whatever is being generated by CIQ will need to be interpreted by CIQ and GC and i basically won't get power as a "normal metric"

Just want to confirm if this is true, cos if it is, then it's a BIG turnoff. might as well just use Zswift / Trainerroad which actually forms a true FIT file and such.

Thanks
  • ahhh, ok
    then look at the moxy example. everything is there. once you understand the process it is actually pretty straightforward.
  • Yup, using that as the example.
    Everything works except GC doesn't and except it forms some Malformed FIT file that cyclemeter doesn't like and which tapiriik.com doesn't like but Strava is able to interpret it properly.
  • i have spent sometime uploading a FIT file containing developer fields to some 3rd party sites. i though it might be useful to have a summary, where is supported right now. my fit file is for a swim activity, containing pace and distance as developer fields.

    :cool:
    sportracks.mobi: 100% working. all developer fields are properly identified, also for intervals. great job.
    TrainingPeaks.com: support confirmed that from 2.11.16 they are reading record messages and identifying native ids.
    mapmyfitness.com: record messages working. session messages not working. lap messages not working either.

    :)
    runalyze.com: file is accepted, but developer fields are not identified. just duration is shown (also intervals). contacted support. they will implement!


    Strava: file is accepted, but developer fields are not identified. just duration is shown (also for intervals). I created new feature idea, they answered they will consider it. https://support.strava.com/hc/en-us/community/posts/203927790-add-support-for-garmin-developer-fields-created-by-ConnectIQ-apps-using-FIT2-format



    swim.com: file not accepted, shown as corrupted. contacted support. they might consider this long term. right now they are very busy with apple watch 2.
  • :o
    Strava: file is accepted, but developer fields are not identified. just duration is shown (also intervals). contacted support. no reply yet.



    I've had reports of some files failing to import into Strava while other fit files made from the same data field but on a different device have worked. I've been able to reproduce the problem on the same devices myself. There are some subtle differences in the FIT files due to some bugs on the Garmin devices (Fenix 3 doesn't write session messages), however I've not been able to correlate the problem strictly to the absence or presence of a session message. Some fit files with session messages have worked.

    I put up a post on the Strava board at the following link.
    https://support.strava.com/hc/en-us/community/posts/203927790/comments/204831670

    The links below are to FIT files that fail.

    https://dl.dropboxusercontent.com/u/11785186/FIT%20Files/735XT%202%20Moxy%20Data%20Fields.FIT

    https://dl.dropboxusercontent.com/u/11785186/FIT%20Files/Edge520%202%20Moxy%20Data%20Fields.fit

    https://dl.dropboxusercontent.com/u/11785186/FIT%20Files/Edge1000%202%20Moxy%20Data%20Fields.fit

    The links below are to FIT files that import as expected.

    https://dl.dropboxusercontent.com/u/11785186/FIT%20Files/735XT%201%20Moxy%20Data%20Field.FIT

    https://dl.dropboxusercontent.com/u/11785186/FIT%20Files/Fenix3%202%20Moxy%20Data%20Fields.FIT
  • I've had reports of some files failing to import into Strava while other fit files made from the same data field but on a different device have worked.

    good to know. for now i never had a failed import. anyway my fields are not shown. Only duration & lap duration are shown, therefore it is not very useful.

    I put up a post on the Strava board at the following link.
    https://support.strava.com/hc/en-us/community/posts/203927790/comments/204831670

    this is my new feature idea. strange, i cannot see your comment there. just a comment from some strava guy. i am not very optimistic about strava.
  • This is the reply I got back from Strava Support. Sounds like a work in progress. I don't have any information on why some fit files work and some don't.

    Hello Roger,

    Thank you for contacting Strava. Sorry for the strange activity uploads from your Garmin device. The issue is the ConnectIQ app changes something in the FIT file that is sent to Strava. We're working with Garmin on a resolution for the issue.

    In the meantime, you can export a TCX version of your activity using the instructions found in our article on exporting files from Garmin Connect and that should upload properly to Strava.

    We are working on supporting the new file format. Thanks for your patience.

    I hope this helps. If you have any questions, please do not hesitate to ask.

    Best,
    Sean
    Strava Support Team
  • I asked Strava for an update on what exactly was causing some files to work and not others and when it would be fixed and this is the response I got back (Bold emphasis is mine).

    I pretty understanding of Strava not displaying CIQ data, but having CIQ data make the FIT file incompatible for import is pretty ugly.

    Could someone from Garmin comment on if there is a good way for CIQ developers to work around this? Are there particular CIQ features in the FIT file that are more likely to cause incompatibility? Is Garmin working with Strave on the incompatibility issue?

    Hey Rodger,

    You are very welcome. At the moment, I do not have an estimate on the timeframe that this will be resolved. Sorry about that. There are currently no plans in development to support ConnectIQ app data on Strava, but we haven't ruled it out either.

    Currently, any device with a ConnectIQ app installed on it will not be parsed by our system correctly. In the meantime, you can export a TCX version of your activity using the instructions found in our article on exporting files from Garmin Connect and that should upload properly to Strava.

    I hope this helps. If you have any questions, please do not hesitate to ask.

    Best,
    Sean
    Strava Support Team
  • I asked Strava for an update on what exactly was causing some files to work and not others and when it would be fixed and this is the response I got back (Bold emphasis is mine).

    I pretty understanding of Strava not displaying CIQ data, but having CIQ data make the FIT file incompatible for import is pretty ugly.

    Could someone from Garmin comment on if there is a good way for CIQ developers to work around this? Are there particular CIQ features in the FIT file that are more likely to cause incompatibility? Is Garmin working with Strave on the incompatibility issue?


    I have reached out to Strava on multiple occasions about integrating native number fields and I've never gotten much interest. I could only speculate on what is happening on their end but I don't think it is a stance they can maintain. Training Peaks and Sport Tracks already support the data generated in all cases I've submitted and it works really quite well. You obviously installed the Connect IQ application to give you something you didn't already have so I would recommend taking your data to a place you can use it rather than not use it :confused: