Indeed, nice job. I guess the "segment" feature that Strava has proven attractive for people. .. But for some reason it shows my fastest Tomin No Mori time, 12/12/2010 at 1:41.57, whereas actually it was something like 1:10 or 1:11. ... even though when I go to view the specific ride it does show a "Tomin no Mori" segment and the correct time. Still a work in progress?
The time posted here is your total duration, including stopped time. The time posted on the trip view page is the moving time (which needs to be changed). I'll have to dig into the code to determine why your moving time is less than the total duration on that section, because it look like your speed was > 6mph the entire time. I believe we use 2mph as the cutoff for stopped/moving.
Thanks Cullen. As you note, this includes my resting time at the top .... For now I'll need to remember to turn off the recording once I get through a segment.
That won't fix it this rare edgecase, since when you start recording again, we may pick up that first point if it's closer to the end of the segment than when you stopped. It's something I'll address, you dont need to worry about start/stopping at the right place, aside from finishing all the way through the segment ;)
When I've saved segments, I've tried to be careful about placing the starting and ending points just a little away from where people would actually stop. As an example in this segment you'll see that I put the end point just a little before the actual rest stop area.
Mar 20, 2012 at 11:38 am
Nice job Takaaki!
Mar 21, 2012 at 01:21 am
Indeed, nice job. I guess the "segment" feature that Strava has proven attractive for people. .. But for some reason it shows my fastest Tomin No Mori time, 12/12/2010 at 1:41.57, whereas actually it was something like 1:10 or 1:11. ... even though when I go to view the specific ride it does show a "Tomin no Mori" segment and the correct time. Still a work in progress?
Mar 21, 2012 at 01:26 am
The time posted here is your total duration, including stopped time. The time posted on the trip view page is the moving time (which needs to be changed). I'll have to dig into the code to determine why your moving time is less than the total duration on that section, because it look like your speed was > 6mph the entire time. I believe we use 2mph as the cutoff for stopped/moving.
Mar 21, 2012 at 01:59 am
Thanks Cullen. As you note, this includes my resting time at the top .... For now I'll need to remember to turn off the recording once I get through a segment.
Mar 21, 2012 at 02:09 am
That won't fix it this rare edgecase, since when you start recording
again, we may pick up that first point if it's closer to the end of the
segment than when you stopped. It's something I'll address, you dont
need to worry about start/stopping at the right place, aside from
finishing all the way through the segment ;)
On 03/20/2012 06:59 PM, Ride with GPS wrote:
May 28, 2012 at 07:23 am
When I've saved segments, I've tried to be careful about placing the starting and ending points just a little away from where people would actually stop. As an example in this segment you'll see that I put the end point just a little before the actual rest stop area.
Aug 5, 2012 at 07:57 am
Nice job, Tim!