Weird CIQ currentHeading() Issue

DaveBrillhart said:

The wind is coming from SSW, the bike is heading toward SW.

???

The screen shows the heading of the bicycle as close to N.

The wind direction is coming from SSW going to NNE.

The issue appears to be how the red wind direction arrow is being drawn.

The red arrow should be more like the following.

Thanks. But here is how it works... According to CIQ, the bike is heading to the SW [currentHeading()], and the wind is from the SSW. That means the wind is a head wind, coming from the left/front. The Compass is showing wind relative to the bike's heading. That makes more sense for a rider to see the relative wind direction. If "SW" is dead ahead, that means that NORTH is behind and to the right, as shown by the black DOT. Every time I ride in/around Florida, the black DOT (north) is in the same direction as the arrow in the Garmin Map above. So I see it working correctly all the time. But this screenshot shows that this guy in France, maybe 10% of the time, sees a situation where the black dot does not align with the map's arrow. Makes no sense to me. He really was heading almost due North like the Garmin Map shows. But CIQ's currentHeading() reported 225 degs (SW).

Right, that is my point. He is riding his bike almost due North. The Map Arrow is correct. The issue is that CIQ's "currentHeading()" is reporting about 225 degs (actually radians, but Math.toDegrees() converts). So while CIQ is right all the time for me, and most of the time for Pierre... this screenshot shows an example of when currentHeading() reports a very wrong result. Not sure what might cause that... I would think Garmin's native sense of heading is based on the same function.

DaveBrillhart said:

The wind is coming from SSW, the bike is heading toward SW.

DaveBrillhart said:

He is riding his bike almost due North.

You said the "bike is heading towards SW" and going "almost due north".

DaveBrillhart said:

So there is a 14.5 k/hr headwind about 45 degs from the front/left.

The wind is from SSW and moving (roughly north) in the same direction the bicycle is (a tailwind). But it's a "headwind"?

This is objectively confusing.

===================

I guess your issue is that the orientation of the wind arrow is wrong.

I don't think the issue is "France".

You don't say what unit is being used in France).

Some of the newer units have compasses.

When moving, the heading is determined using GPS orientation.

When stopped, the heading is determined using the compass. This is really "presumed heading" (it's actually orientation).

For units that don't have compasses, the orientation when stopped is not reliable.

The 1030 does not have a compass.

I display heading on my app and on the 1030+ (which has a compass) the reporting heading doesn't seem reliable when stopped.

I reported it as an issue over three years ago.

forums.garmin.com/.../compass

What I'm saying is the bike is actually heading almost due North. So the Garmin Map is correct, the arrow (upper left corner) is correct.

My EDGE 1030 has this arrow as well in the map view. Pierre uses a 1030Plus.

In my datafield, I use the function "currentHeading()". In my case, in Florida, on my EDGE 1030, "currentHeading()" always seems to agree with the Garmin Map's directional arrow. Good!

For Pierre, in France, on his EDGE 1030Plus, it also almost always agrees.

But in this screenshot, CIQ's "currentHeading() returned 225 degs... so CIQ apps think the bike is heading to the SW. Which is wrong. I hope this makes more sense. I appreciate you trying to help me figure this out.

Is the issue occurring when he's stopped?

I display heading on my app and on the 1030+ (which has a compass) the reporting heading doesn't seem reliable when stopped.

I reported it as an issue over three years ago.

forums.garmin.com/.../compass

(I'm still puzzled why you said the bike was going south and that the tailwind was a headwind.)

My data field handles stopped by showing an outline of the wind arrow (rather than filled with RED for a headwind, GREEN for a tailwind, or GREY for a crosswind). So I know in the case of the screenshot shown here, he was moving. I see there are three ways to get heading. Also GPS accuracy (position.quality) might be something I'll look into. So frustrating.

That is counterintuitive... But bike heading is SW and the wind direction is the FROM direction, so the wind is coming FROM the SSW... which is a head wind, which is why the arrow is colored RED. Did I say tailwind? if so, it was a typo. Sorry. But the wind "heading" is the FROM direction, whereas the bike heading is the TO direction. Can be confusing but that is the way they always refer to it.

DaveBrillhart said:

I see there are three ways to get heading.

Three ways? I see two: change in position (from GPS) and compass orientation.

The heading is going to be less accurate moving slowly. But the GPS accuracy would have to be really bad for it to be 180' off (I'd think).