Ticket Created
over 4 years ago

WERETECH-8543, WERETECH-8544

Two Glaring API Gaps - Easy Additions

1. You already pull HR Zones. You are missing POWER Zones. The "pattern" already exists. The system call is essentially identical to HR Zones. It has been asked for for years. Please add the ability to pull POWER Zones into CIQ. Thanks. Our work around is to ask users to enter in all their Power Zone limits in User Settings, when it is already in their Garmin Profile.

2. You already have fillCircle() and drawCircle(). But you only have fillPolygon(). Again, this is a no brainer, simple to add, based on a known pattern. Probably would take someone a few minutes to add. just an oversight I'm sure that it was missing. I work around it by drawing three line segments. But consider adding this as a Class 1 feature request. If Class 1 means it fills an obvious API gap and is extremely easy.

Thanks!

Parents
  • On Power Zones: besides the suggested function

    UserProfile.getPowerZones(sport as UserProfile.SportPowerZone) as Lang.Array<Lang.Number>

    , I believe

    UserProfile.Profile.ftpCycling as Lang.Number or Null
    UserProfile.Profile.ftpXcSki as Lang.Number or Null

    for querying the user's FTP could be similarly useful.

Comment
  • On Power Zones: besides the suggested function

    UserProfile.getPowerZones(sport as UserProfile.SportPowerZone) as Lang.Array<Lang.Number>

    , I believe

    UserProfile.Profile.ftpCycling as Lang.Number or Null
    UserProfile.Profile.ftpXcSki as Lang.Number or Null

    for querying the user's FTP could be similarly useful.

Children