Re: [Qlandkartegt-users] QMapShack V 1.5.1

[Christian E. <qm...@ch...>]

Hi,

the slope is not stored in the .gpx-file (it is neither part of the GPX-std.,
nor part of the Garmin extensions), it is always calculated by QMS (based
on the elevation and distance of two subsequent trackpoints).

The empty field at the top of the selector list is intentional, even though
I do not really understand why one would want to select that entry, answering
that question is up to Oliver.

I assume, the entry "Slope (directed)" does either show up in both or none of
the comboboxes in the "Style" / "Graphs" tabs, but not "mixed".
Missing entries in the comboboxes are, by the way, not related to timestamps.

The only reason I can think of at this point:
If there isn't any change in slope at all (that is both minimum and maximum
are identical), the entry will be hidden.

If that is not the case a sample GPX file would useful, but keep in mind that
those files might contain sensitive data (such as heart rate and locations), 
you maybe want to remove those prior to sending the files.

-chris

On Mon, 23 Nov 2015 22:23:53 +0100
Pierre Baldensperger <ba...@li...> wrote:

> Hi Christian,
> 
> Thanks for the clarification. In the mean time, I have digged a little 
> further and I think there must definitely be something wrong with my 
> data or my installation. At first I could swear that I saw the slope 
> data was available for graphing, but then when I tried to analyze some 
> other tracks I could not find it any more. I thought it was the update 
> to 1.5.1 that triggered the disappearance, but I tried reverting to 
> 1.5.0 and it did not help.
> 
> As far as I know, my GPS device (Mio Cyclo 305) does not save the slope 
> data in the GPX files (I don't see it anywhere in the XML data), so it 
> must have been a slope computed automatically by QMS upon loading of the 
> GPX file.
> 
> One thing I noticed is that I have an empty field name at the top of the 
> selector list for graph data. When I select this field, I get an empty 
> graph saying "no data or invalid data". Is this normal or maybe this is 
> where the slope data used to be ?
> 
> Actually, after further experimentation the "slope (directed)" field is 
> available for some track files but not others. I don't understand why 
> because I don't see anything unusual about those track files : they 
> don't seem any different, but the slope is just not showing up for them.
> 
> As far as I can tell, the timestamps in my tracks are OK. And I am also 
> able to graph the other data without problem. Only the slope is missing.
> 
> I also tried to close all projects and re-load the GPX files from 
> scratch, but still no slope. I can send or upload sample GPX files if 
> you want to try to reproduce the problem.
> 
> 
> -Pierre.
> 
> PS : BTW I was not so "secretly" hoping, because I saw the feature was 
> already on the wish list, and at some point, a few months ago, I even 
> e-mailed this list to ask whether the implementation was actually 
> planned. Back then, Oliver answered that it was rather tricky to have a 
> "clean" implementation due to the various extension formats from several 
> GPS manufacturers, so I wasn't expecting to see it appear before a few 
> more versions.
> 
> 
> 
> On 23/11/2015 20:45, Christian Eichler wrote:
> > Hi there,
> >
> > the only difference between V.1.5.1 and the previous release V.1.5.0 (which
> > existed for less than two hours) is the fix of the non-working `abort`-Button,
> > caused by a non-connectable signal.
> >
> > As Oliver mentioned we updated the wiki pages for Tracks and Waypoints,
> > therefore I refer to https://bitbucket.org/maproom/qmapshack/wiki/DocGisItemsTrk2
> >
> > Slope data - if available - can be used in plotting, as well as a source for
> > colorizing the track (on the map).
> > The only thing a little bit strange is the fact that plotting only works if
> > you have correct timestamps.
> > That's sth. to be fixed in the near future.
> > If that's what you are struggling with, a simple fix would be using the
> > filter `Change speed`.
> > This adds a timestamp to every trackpoint (and drops any existing timestamps).
> >
> >
> > By the way: "secretly hoping" for a specific feature to be implemented is not
> > the best way to go - feel free to propose new features via
> > https://bitbucket.org/maproom/qmapshack/issues?status=new&status=open
> >
> > -chris
> >
> >
> > On Mon, 23 Nov 2015 19:50:12 +0100
> > Pierre Baldensperger <ba...@li...> wrote:
> >  
> >> Fantastic news,
> >>
> >> I was secretly hoping for the extensions support to grow so the last
> >> couple of versions have greatly increased my enthousiasm. Big thanks to
> >> the developers, this software rocks.
> >>
> >> About the latest 1.5.x versions : I first installed 1.5.0 and played
> >> with it, and I seem to remember it was computing slopes (at least the
> >> slope was available in the list of auxiliary track data). But since I
> >> upgraded to 1.5.1 the slopes data don't seem show up any more (or maybe
> >> I'm looking in the wrong place). Am I missing something ?
> >>
> >> Thanks,
> >> -Pierre.
> >>  
> 
> 
> ------------------------------------------------------------------------------
> Go from Idea to Many App Stores Faster with Intel(R) XDK
> Give your users amazing mobile app experiences with Intel(R) XDK.
> Use one codebase in this all-in-one HTML5 development environment.
> Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
> http://pubads.g.doubleclick.net/gampad/clk?id=254741551&iu=/4140
> _______________________________________________
> Qlandkartegt-users mailing list
> Qla...@li...
> https://lists.sourceforge.net/lists/listinfo/qlandkartegt-users