0
{
  "minStartTimeNs": "1636419661000000000",
  "maxEndTimeNs": "1636439595000000000",
  "dataSourceId": "derived:com.google.heart_rate.bpm:com.google.android.gms:merge_heart_rate_bpm",
  "point": [
    {
      "startTimeNanos": "1636435597175000000",
      "endTimeNanos": "1636435597175000000",
      "dataTypeName": "com.google.heart_rate.bpm",
      "originDataSourceId": "raw:com.google.heart_rate.bpm:com.google.android.apps.fitness:user_input",
      "value": [
        {
          "fpVal": 98.061103820800781,
          "mapVal": [
            
          ]
        }
      ],
      "modifiedTimeMillis": "1636436192037"
    }
  ]
}
Stephen C
  • 698,415
  • 94
  • 811
  • 1,216
Himanshu Dadhich
  • 1
  • Based on the docs. Mapval is a list which has valid key space and units for the corresponding value of each entry should be documented as part of the data type definition. Keys should be kept small whenever possible. Data streams with large keys and high data frequency may be down sampled. – Arel Guatno Jun 28 '22 at 15:59
  • please refer to https://googleapis.dev/dotnet/Google.Apis.Fitness.v1/latest/api/Google.Apis.Fitness.v1.Data.Value.html#Google_Apis_Fitness_v1_Data_Value_MapVal – Mbula Mboma Jean gilbert Jul 01 '22 at 12:30

1 Answers1

0

mapVal is simply there as an artefact of the fact that JSON can't distinguish between an unset map field and an empty map in the map field.

It will never be non-empty for com.google.heart_rate.bpm data: you can see that only 1 float-valued field is used in the documentation.

You can ignore the mapVal.

Andy Turner
  • 137,514
  • 11
  • 162
  • 243