Well, the Coast Guard wrote the spec
(see link below). The spec calls for 1500 bits of data transmitted at 50 bits per second.... Interestingly enough, the satellite actually tells the receiver how many 1.5 second epochs "have occurred since the transition from the previous week".And it actually does this every 6 seconds (at the beginning of each of the 5 subframes) so a receiver could update its location every 6 seconds.Anything it does faster than 6 seconds it is doing internally - such as updating distance to a waypoint - mine does that in hundredths of a mile at ranges less than 10 miles. But that has to be using the velocity data derived from the most recent time cut from the satellite.For accuracy, I should point out that the full 'navigation message' requires 25 cycles X 30 seconds, because sub-frames 4 & 5, which contain the almanac data and other stuff which isn't needed all the time, are sent over 25 cycles.And since this thread has to do with accuracy, with a GPS up to 50 meters is reasonable, so if I am sailing at 5 knots, in 6 seconds I have traveled1852 meters * 5 miles/hour * 1/600 hour = 15 metersOK, even if the GPS is accurate to 5 meters (which is sometimes is, but you and it don't know when that is unless you and it are standing on a benchmark) that still gives an accuracy of +/- 33%So for moving objects, I think the full 30 seconds would be appropriate. That gives75 meters traveled and 5 meters accuracy =+/- 7%Hmmm, that Cheeto isn't looking toooooo bad in the accuracy game ;DFor a stationary object, one might hope that repeated satellite fixes would increase accuracy, but I don't think so - the receiver doesn't have any way to know which is a more accurate position and which isn't, so I would expect only a modest 'learning' curve, if in fact the receiver trys to 'learn' and doesn't just display the current value.Cheers,Bobs/v X SAIL R 8