Author Topic: hasSpeed() inconsistency in track obtained via API  (Read 711 times)

Offline Radim V

  • Global Moderator
  • More than Newbie
  • *****
  • Posts: 10
    • View Profile
hasSpeed() inconsistency in track obtained via API
« on: December 04, 2018, 22:47:16 »
Hallo, I am developing something with Locus API, and in one of my debug dumps I noticed some inconsistency regarding methods  location.hasSpeed(). If you check attached files, namely lines 26, 34, 39 in the .dump file you should see what I mean. GPX file that I imported in locus and consequently got via standard API mechanism (ActionTools.getLocusTrack()) also attached.
Only first "trackpoint" has speed false, all other have speed true, but 0 which is incorrect I think. (location and timestamp are available) 
This is not pressing issue to me as I use location and timestamps to recalculate speed or force constant speed if track is not fully timestamped.
Thanks, Radim
« Last Edit: December 05, 2018, 18:15:06 by Radim V »

Offline Menion

  • Administrator
  • Professor of Locus
  • *****
  • Posts: 12032
  • Thanked: 518 times
    • View Profile
  • Device: Pixel 2
Re: hasSpeed() inconsistency in track obtained via API
« Reply #1 on: December 14, 2018, 12:15:56 »
Just note: discussed over email.
Ideas, wishes, problems
Advanced topics, public discussion, sharing of knowledges, testing beta versions: you're here!
Support email: