m******g
发帖数: 516 | 1 My regular training route is a 8 mile somewhat hilly circle. When using 305,
it reports the elevation gain/loss from 500 feet to 1000 feet. Once it
showed me falling down a 50 feet cliff, and jumped out in next few steps.
Since I usually stop very close to where I start, the starting and ending
points elevations look OK, Distance wise, it is also within range of error.
Any one has the same experience, or it is just me unfortunate to have a
defect product? | j*********g
发帖数: 3826 | 2 GPS应该是周期性打点，计算本次和前次的距离，这样细小误差总是存在的，而且万一遇
上树林什么的没有信号，中间的一段就乱了。
305,
.
【在 m******g 的大作中提到】
: My regular training route is a 8 mile somewhat hilly circle. When using 305,
: it reports the elevation gain/loss from 500 feet to 1000 feet. Once it
: showed me falling down a 50 feet cliff, and jumped out in next few steps.
: Since I usually stop very close to where I start, the starting and ending
: points elevations look OK, Distance wise, it is also within range of error.
: Any one has the same experience, or it is just me unfortunate to have a
: defect product?
| l***h
发帖数: 9308 | 3 你把默认的smart recording （4秒记录一次）改成每秒计一次，有可能减少误差。不
过，后者电池只能撑3个半小时，前者能维持10小时。
305,
.
【在 m******g 的大作中提到】
: My regular training route is a 8 mile somewhat hilly circle. When using 305,
: it reports the elevation gain/loss from 500 feet to 1000 feet. Once it
: showed me falling down a 50 feet cliff, and jumped out in next few steps.
: Since I usually stop very close to where I start, the starting and ending
: points elevations look OK, Distance wise, it is also within range of error.
: Any one has the same experience, or it is just me unfortunate to have a
: defect product?
| l***h
发帖数: 9308 | 4 搭车问一下，在305自带的软件traning center里面，pace全程最大最小相差2分半左右
，但实际显示总是近乎于一条水平直线，很不舒服，因为Y轴最大值到龟速70min/mile。
有什么办法把这些巨长的spike干掉？让pace曲线看起来更好些
一遇
【在 j*********g 的大作中提到】
: GPS应该是周期性打点，计算本次和前次的距离，这样细小误差总是存在的，而且万一遇
: 上树林什么的没有信号，中间的一段就乱了。
:
: 305,
: .
| j*********g
发帖数: 3826 | 5 问错人了，我没有garmin啊。
mile。
【在 l***h 的大作中提到】
: 搭车问一下，在305自带的软件traning center里面，pace全程最大最小相差2分半左右
: ，但实际显示总是近乎于一条水平直线，很不舒服，因为Y轴最大值到龟速70min/mile。
: 有什么办法把这些巨长的spike干掉？让pace曲线看起来更好些
:
: 一遇
| b***i
发帖数: 10018 | 6 runningahead里面的graph可以smooth out data.
mile。
【在 l***h 的大作中提到】
: 搭车问一下，在305自带的软件traning center里面，pace全程最大最小相差2分半左右
: ，但实际显示总是近乎于一条水平直线，很不舒服，因为Y轴最大值到龟速70min/mile。
: 有什么办法把这些巨长的spike干掉？让pace曲线看起来更好些
:
: 一遇
| b***i
发帖数: 10018 | 7 yes, garmin 305 is very inaccurate at elevation data...
305,
.
【在 m******g 的大作中提到】
: My regular training route is a 8 mile somewhat hilly circle. When using 305,
: it reports the elevation gain/loss from 500 feet to 1000 feet. Once it
: showed me falling down a 50 feet cliff, and jumped out in next few steps.
: Since I usually stop very close to where I start, the starting and ending
: points elevations look OK, Distance wise, it is also within range of error.
: Any one has the same experience, or it is just me unfortunate to have a
: defect product?
| l***h
发帖数: 9308 | 8 runingahead的平滑曲线稍微好一点。但是Y轴PACE的范围也不小，从0-15min/mile，就
分3大格，如果每个大格再分5个小格就清楚了。难道就不能根据数据内容，把pace 5以
下，12以上的空白去掉？
【在 b***i 的大作中提到】
: runningahead里面的graph可以smooth out data.
:
: mile。
|
|
