Old 01-19-23, 09:45 AM
  #6  
Steve B.
Senior Member
 
Join Date: Jul 2007
Location: South shore, L.I., NY
Posts: 6,890

Bikes: Flyxii FR322, Cannondale Topstone, Miyata City Liner, Specialized Chisel, Specialized Epic Evo

Mentioned: 18 Post(s)
Tagged: 0 Thread(s)
Quoted: 3243 Post(s)
Liked 2,091 Times in 1,183 Posts
Originally Posted by NoWhammies
I use my watch every day and the GPS gets used at least three times a week. Regarding the barometric sensor, that is a good question. I do not know. I will have to do some googling around.

I did find something out that was interesting the other night though. I also run with a running dynamics pod to capture running dynamics. Sometimes the watch recognizes the pod right away and sometimes not. Anyway. Last night the running pod was recognized at the start of the run. And wouldn't you know it? There was no sudden jump in elevation. I am starting to wonder if the running dynamics pod, which captures ground contact time, is having some sort of impact on the elevation profile readings. I will do some more experimenting with the running pod to see it the pod is having any impact.
Does the running pod generate its own elevation data ?. Maybe that data sometimes gets sent to the watch as accurate data, and on occasion if the pod is not connected, the watch generates its own incorrect data ?. Do some runs with no pod, see what the elevation info looks like, if its incorrect, work to fix that.
Steve B. is offline