Why is it a ~10 seconds delay/lag for Pace and Speed data fields in Run activity but only 2-3 seconds in Bike activity?

yes and hard to do intervals 

Yes, i discovered that after the first post in this thread. Very frustrating.

AndersB said:

Advices?

Buy a foot pod.

You consider only one situation, but there are other users that have other demands. There is only one running activity available. So it must be made a trade-off between:
1. workouts, e.g. slow running, fast running, track running on oval, intervals, sprints, ...
2. environments, e.g. open surface, dense trees, urban canyon, tunnel, multipath, ...
3. GNSS satellite conditions, e.g. GPS/GLONASS/GALILEO, number of satellites, GDOP
4. weather, e.g. clear sky, cloudy, rain, ...
5. smooth charts vs. oscillating charts

In addition, during running the arm with the GPS receiver moves forward and backward. It's a highly complex dynamic system with movement of the receiver in different directions in every step. Therefore the smoothing time interval must be a bit longer. OK, F6 isn't suitable for Usain Bolt's 100m, because when he has finished the run, instant pace still shows 00:00 ;D

Furthermore, the main problem is, that the max. position error is nearly constant (3m, 95%). So, for lower speed the influence of the error is larger, than for higher speed.

In contrast at biking the receiver moves only in the forward direction. Therefore the smoothing time interval can be a bit shorter.

I have stryd and the same situation 

I believe in this case issue is with software, because in my case stryd shoud show me current speed without delay 

I understand that there is a lot of different conditions.

If Garmin added a custom setting for the smothering/delay in the activity settings everyone would be happy regarding this.

For example:

Setting "Speed/pace smothering delay" and options "None", "3 seconds", "5 seconds" and "10 seconds". Then we can choose by ourselves which setting fits us best. Default can be set to todays setting so it doesnt affect already happy users.

AndersB said:

Setting "Speed/pace smothering delay" and options "None", "3 seconds", "5 seconds" and "10 seconds". Then we can choose by ourselves which setting fits us best.

You can do this by coding your own app with CIQ. It's possible to get the lat/lon's from the GPS sensor. Then you may calculate the distances using the haversine formula and perform your own smoothing.

Try it.

I don't have time to develop Garmin apps for the moment. Busy with other backend development. And, I still think that Garmin should fix this issue.

Jan502 said:

I believe in this case issue is with software, because in my case stryd shoud show me current speed without delay 

If you use a stryd, it doesn't use GPS. The delay is due to filtering and smoothing of pace/speed from GPS measurements. But I'm not sure whether for simplicity the same algorithm is used also for stryd, although these are different input metrics.