[Solved] Possible bug on latitude/longitude STREAM

ActivityStream

A value over time trace for an activity. Types: time, watts, cadence, heartrate, distance, altitude, latlng,
velocity_smooth, moving, grade_smooth, temp, torque, fixed_watts, fixed_heartrate, raw_watts, raw_heartrate,
left_right_balance, smo2, thb, smo2_2, thb_2, dfa_a1, epoc, hrv, ga_velocity, fixed_altitude, corrupt_time,
core_temperature, skin_temperature, stride_length, w_bal, respiration, watts_alt, watts_alt_acc.

  • type String
  • name String
  • data Object ~ Integer, Float, Boolean, int (fixed_watts), short (hrv)
  • data2 Object ~ Float only for type latlng
  • anomalies List<ActivityStream.Anomaly>

I was using the “map” API endpoint. (hence, didn’t see this situation)