Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

If FIT file has missing elevation data avoid adding <ele></ele> param instead of nan #16

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

If FIT file has missing elevation data avoid adding <ele></ele> param instead of nan #16

wants to merge 2 commits into from

Commits on Aug 6, 2024

  1. Represent missing elevation data as 0 rather than nan 

    Resolves: dodo-saba#15
    @mbacchi
    mbacchi committed Aug 6, 2024
    Configuration menu
    Copy the full SHA
    c11cebc View commit details
    Browse the repository at this point in the history

Commits on Sep 5, 2024

  1. After discussing with @dodo-saba, decided to not arbitrarily add 0 ra… 

    …ther to not add any <ele></ele> parms if the FIT value is NaN
    @mbacchi
    mbacchi committed Sep 5, 2024
    Configuration menu
    Copy the full SHA
    ac92044 View commit details
    Browse the repository at this point in the history