Monav : total route length and trip duration?
Thierry Bur
Christoph Eckert
> I've founded how to display the detailed navigating instructions, but how
> can I display the total length for my route as well as the total trip
> duration ? (I don't want to sum up the route segments and I've no clue of
> the speed parameters).
currently you will get neither the route length not the track length.
A "trip computer" to display stats about the taveled and remaining trip length
is in my to do list, but not at the topmost priority. So if someone else wants
to step in...
:)
--
Beste Grüße,
Best regards,
ce
Christoph Eckert
as it turned out to be simple enough:
http://christeck.de/stuff/monavtripstats.png
And yes, the -128.5m of altitude appear in the tracklog, though I have no clue
why :) .
BTW: The code is not publicly available yet, as it requires some refactoring
first.
Christoph Eckert
http://christeck.de/stuff/monavtripstats.png
I added a label to display the elevation profile of the tracklog (which
obviously is still buggy :).
The problem is that the stats require filtering trackpoints
* with weird elevation data (which I see every now and then on the N900)
* clouds which are far away from the actual position (e.g. the position was
miscalculated inside trains, tunnels and the like)
* clouds recorded during breaks
* by tracksegments to avoid a trip distance which is inaccurate
* by amount. At 1Hz, the tracklog can host a maximum of 86400 points. Even
smaller tracklogs require a significant amount of computation time to calculate
the statistics.
But anyway, I think it is just great to have some rough figures about the time
and distance passed and the distance remaining.
Any opinions?
Christian Vetter
Looks nice so far.
On Sun, May 1, 2011 at 11:54 PM, Christoph Eckert <c...@christeck.de> wrote:
> The problem is that the stats require filtering trackpoints
> * with weird elevation data (which I see every now and then on the N900)
> * clouds which are far away from the actual position (e.g. the position was
> miscalculated inside trains, tunnels and the like)
> * clouds recorded during breaks
If you store the complete GPS information you can make use of the
vertical / horizontal accuracy, e.g., omit all points that are not
accurate within 20m. Does the GPX format have fields for this
information, so that we can store it?
Otherwise it looks great.
Also we should be able to see this information for the current route
as well ( a heightprofile will be added later for that ).
Regards,
Christian Vetter
Christoph Eckert
> If you store the complete GPS information you can make use of the
> vertical / horizontal accuracy, e.g., omit all points that are not
> accurate within 20m.
the logger uses GpsInfo objects for that, so the logger could decide which
data to omit. I'd like to do that, as sometimes the tracklog displayed really
looks weird (see the attached screenshot). Obviously, keeping such data makes
the trip info rather useless.
> Does the GPX format have fields for this
> information, so that we can store it?
AFAIK no, which is why many people are still keen in NMEA tracklogs.
> Otherwise it looks great.
>
> Also we should be able to see this information for the current route
> as well ( a heightprofile will be added later for that ).
You mean adding a field to the remaining time?
