|
Cedar Rapids, Iowa | Really? Something doesn't sound right about that. What software and what CORS network?
According to the NTRIP version 1 protocol documentation, the client is allowed to send NMEA strings at any time. The GGA string is the only one that is used to get position data to calculate corrections. Based on my testing against the MN CORS network, there was no drop or delay of data after a GGA string is sent. I haven't actually put the data into a receiver, but the data stream certainly keeps flowing.
From a programming perspective, the 3.8 miles thing is odd. That requires the client doing a distance calculation between the current location and the location when the last GGA string was sent. Aside from 3.8 miles being an odd number, that is a relatively intensive calculation, and for what benefit. Doing something based on time, such as sending a GGA string every 30 or 60 seconds, is much easier. | |
|