
Neither the 945 nor the Bryton are that great here in relatively benign conditions 945+GALILEO (Green), Edge 530 (red), Bryton Aero 60 (Blue) Same here 945+GALILEO (Green), Edge 530 (red), Bryton Aero 60 (Blue) 945+GALILEO (Green), Edge 530 (red), Bryton Aero 60 (Blue)Īround some low trees and at low speed the 945 is good 945+GALILEO (Green), Edge 530 (red), Bryton Aero 60 (Blue)Īlthough these navigations around a circle/roundabout look bad, I guess all are just about in an acceptable 5m off from where I really was… 945+GALILEO (Green), Edge 530 (red), Bryton Aero 60 (Blue) However, on the left and nearer to larger buildings, the 945 soon becomes more than 5m inaccurate like the other 2 devices. In more open conditions or near these low houses (right of image) the 945 is good. 945+GALILEO (Green), Edge 530 (red), Bryton Aero 60 (Blue) Here the 945 gets a nice track through the tunnel where there is no satellite reception (!) but to the left, it is too inaccurate, straying 10m from the true location. This was generally fine and I’ll highlight some exceptions. Of course, the reality of any given situation is more nuanced and complicated than simply what piece of tech is on your wrist…try this link to see what else can go wrong. Put simply, if you run down the middle of the road today with your 945 then it’s perfectly acceptable for the watch to say you are running on the pavement on either side – that’s true of EVERY OTHER sports watch. The massive improvement in GNSS accuracy is most likely to come from dual-frequency Galileo (frequency E1 and frequency E5a). Thus you can only expect to get +/-5m accuracy BUT enabling GALILEO increases the number of visible satellites and hence GALILEO increases the probability of +/-5m accuracy being achieved. My understanding is that the accuracy of Galileo with a single frequency is similar to the accuracy of GPS with a single frequency. It seems that the new Sony GNSS chips used by Garmin from 2019 onwards can only use the E1 frequency (Galileo) and the L1 frequency (GPS). GPS Accuracy – GLONASS, GALILEO and GNSS Functions
Garmin forerunner update#
One had an elemnt of ‘user error’ to contend with 😉 I’ll update that section in June probably (ping me below in the comments if I haven’t done that)įYI: Garmin also uses the accelerometer in the watch as an input to their pace/distance algorithms. That means you can compare the 945 with the best GPS watches from yesteryear which most of you will know as the Polar V800 and Suunto AMBIT 3. I’ve completed 2.5x 10 mile runs on my standard GPS course and following a set methodology with my normal usage in running and other sports. There are other regional satellite systems too. I’m also looking at the accuracy of using the American GPS satellites and a little bit at augmenting that with the potentially superior European GALILEO satellites and we’ll leave the Russian’s GLONASS system out of it. They probably also misestimate distance by 0.5% or more in tricky, urban conditions. a running watch can’t really tell you how fast you are running. Mostsports devices are not fit for the purpose of giving instant pace but may be alright with your current lap pace. It’s just that when you are running GPS has a tricky job of dealing with the environment and your swinging arm to give you a correct pace and distance. If you want to use GPS to determine your walking and cycling speed then you’ll probably be alright too. I’m looking at FITNESS FOR PURPOSE but what purpose do you want a GPS track for? If it’s a pretty post-run or post-ride/run track of where you’ve been that’s ‘about right’ then most sports watches will be fine for you. This is part of my main Garmin 945 Review and specifically looks at many aspects of GPS accuracy or, more correctly, GNSS accuracy. FTC: Affiliate Disclosure: All links pay commission Reading Time: 10 minutes Garmin 945 (Yellow)
