or for an ad-free Fetcheveryone experience!

New Glasses View - Coming Soon

2 lurkers | 31 watchers
Apr 2014
10:36am, 23 Apr 2014
947 posts
  •  
  • 0
SillyFencer
Duh! Hadn't noticed that.
Apr 2014
10:37am, 23 Apr 2014
73,765 posts
  •  
  • 0
GregP
~points and laughs~
Apr 2014
10:42am, 23 Apr 2014
4,481 posts
  •  
  • 0
paul the builder
So, speaking of axes.... any chance of some numbers on the second / right y-axis? BPM specifically.
Apr 2014
10:52am, 23 Apr 2014
948 posts
  •  
  • 0
SillyFencer
lol, thanks Greg.
Apr 2014
11:21am, 23 Apr 2014
2,022 posts
  •  
  • 0
RevBarbaraG
Not sure if this is the right thread... but have noticed that the splits reported in the split breaker are not the same as the ones in the notes. E.g. my run today, the notes say:

1) 1m - 13:10
2) 1m - 13:00
3) 1m - 13:14
4) 1m - 13:30
5) 1m - 13:15

While according to the splitbreaker it was:
1) 13:28
2) 12:59
3) 13:25
4) 13:39
5) 13:29

Any idea, anyone?
Apr 2014
11:27am, 23 Apr 2014
950 posts
  •  
  • 0
SillyFencer
I asked the same question rev. The first set are what your watch reported and saved. The second set are taken from the GPS data itself.
Apr 2014
5:36pm, 23 Apr 2014
73,768 posts
  •  
  • 0
GregP
Try uploading it to Strava. They use a special algorithm involving tea leaves :)
May 2014
12:57pm, 27 May 2014
1,109 posts
  •  
  • 0
SillyFencer
Hardly a big deal, but a tiny bit annoying. The "reset view" covers the exact bit I want to see on this occasion.

[IMAGE]
May 2014
11:05am, 28 May 2014
4,583 posts
  •  
  • 0
paul the builder
Boing.

So, the axis-label-less graph, then?

1. The elevation (meters) is just a pretty picture unless there's actually some numbers on one of the y-axes.
2. HR (bpm) - just putting 70% and 85% 'zones' on there isn't really enough information to be useful. A line every 5bpm would be.
May 2014
11:27am, 28 May 2014
14,363 posts
  •  
  • 0
fetcheveryone
SF - that's annoying - but hard to know where to put it really :-)

PtB - the potential for so many axes means that it's difficult to find a solution that fits them all in, without eating up space. The tooltip is there when you mouse over the graph, and it gives you accurate readings for all the curves.

About This Thread

Maintained by fetcheveryone
1) the off- and on-able graph lines in the top graph.
2) the split breaker. No longer does it show your split times in hard-to-work-out seconds, and the data table beneath it should also be useful.
3) cadence and power graphs for those that record it
4) a few nods to the different requirements of swim/bike/run - colour coded graphs, no ascent/descent for swims, more appropriate split options for swims.
5) works with no lat/lng data in your file - good for turbo, treadmill, pool swims
6) no automatic saving of route e.g. "Imported from your Toaster - 2014-02-10" - but you can name & save route with one click if it's special. If you play Conquercise or Fetchpoint, you don't have to do ANYTHING differently. Reports of a few bugs in Fetchpoint as a result, I'm working on those.
7) the ground work for changing the top graph into a javascript-based one that will integrate directly with the map slider, and show a tooltip for wherever you are on the graph. Playing with that in dev.
8) reclaiming notes field for notes. Still captures basic split information, but pace/hr bands etc now in their own graphs. Similar updates to user profiles on the cards so you can see how others are training (but expect it to be restrictable by the owner).
9) Some cute little icons for the weather / conditions. If you always leave these options as 'perfect', 'still' and 'none' then you won't see anything. Think of it as a way of capturing conditions that might have had an impact on your run.
10) Little blue (i)'s that give a bit more information about each of the sections.
11) When you import from file, you can now pre-choose sport - and rather than being taken to the 'edit' screen, you're taken to the 'view' aka the 'glasses' view.
12) Some folks were concerned that watch elevation data gets ignored. This is on purpose - GPS-based elevation data is notoriously inaccurate. When you're taken to the glasses view, elevation profile should pop up after a few seconds, and the ascent/descent likewise. If it doesn't happen, try refreshing the page.

REPORTED BUGS:
1) Westmoors - kit reporting 0 miles.
2) Some issues with the information popups being obscured on RHS of browser window.
3) Some lines extend above top of graph, so peaks are missing.
4) Larkim - choice of sport is being ignored.
5) Ascent/descent not showing on 'list view' nor in weekly graphs.

REQUESTS:
1) Indicator of 'amount of flattening' flattening.
2) Option to reduce flattening (without having to go via reset)
3) Remember flattening setting
4) Option to show paceband, HR band graphs etc as table of data rather than graph.

Related Threads

  • traininglog
  • website








Back To Top

Tag A User

To tag a user, start typing their name here:
X

Free training & racing tools for runners, cyclists, swimmers & walkers.

Fetcheveryone lets you analyse your training, find races, plot routes, chat in our forum, get advice, play games - and more! Nothing is behind a paywall, and it'll stay that way thanks to our awesome community!
Get Started
Click here to join 113,937 Fetchies!
Already a Fetchie? Sign in here