Ticket Created
over 4 years ago

CIQQA-541

Lat and Long not showing up in 945 LTE .Fit Files

I've had users reporting they are not getting maps when using our platform, are the position coordinates written somewhere different for the 945 LTE? 

Thanks

  • I replied to this comment awhile ago but for some reason no longer see it so I will reply again. The issue is we are not seeing any gps data in the native fit file for users using are app with the 945 LTE. No map data shows up in our platform or in connect IQ. I can provide runs and .fit files if needed. Thanks (this only happens with the 945 lte)

  • I replied to this comment awhile ago but for some reason no longer see it so I will reply again. The issue is we are not seeing any gps data in the native fit file for users using are app with the 945 LTE. No map data shows up in our platform or in connect IQ. I can provide runs and .fit files if needed. Thanks (this only happens with the 945 lte)

  • Hi Rachel,

    No the issue is that there are no GPS coordinates written into the native fit file. So when a user runs with our app (only when using the 945 LTE) we cannot provide a map post-run on our plat form and no map shows up in Garmin connect. This only happens with the 945 LTE. I have this documented and can provide the links/ .fit files if needed.

    Thanks

  • Hello . First of all, I apologize for the delayed response.  Second, I pulled in and converted a couple of the 945 LTE fit files for our activity recording app that uses the FitContributor and am seeing lat and long data being recorded.  This is the code we are using to set the FitContributor up and set the data.

    contributorStartLocationLat = session.createField(
        "FitContribLapStartLocationLat",
        7,
        FitContributor.DATA_TYPE_SINT32,
        {:nativeNum=>0, :mesgType=>FitContributor.MESG_TYPE_RECORD,:unit=>""}
    );
    
    contributorStartLocationLong = session.createField(
        "FitContribLapStartLocationLong",
        8,
        FitContributor.DATA_TYPE_SINT32,
        {:nativeNum=>1, :mesgType=>FitContributor.MESG_TYPE_RECORD,:unit=>""}
    );
    
    contributorStartLocationLat.setData(Position.getInfo().position.toDegrees()[0])'
    contributorStartLocationLong.setData(Position.getInfo().position.toDegrees()[1]);

    Are you doing something different? If you don't want to discuss your code here, feel free to email us at [email protected]m and we can continue our conversation there. 

  • Another user just reported software version 3.07