Reputation: 1
{
"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"
}
]
}
Upvotes: 0
Views: 308
Reputation: 140514
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
.
Upvotes: 0