In my last post, I gave a quick and dirty explanation of the principles of precise GPS positioning. In it, I mentioned the double differenced dual-frequency phases as the main observations behind RTK positioning. However, that wasn’t very informative for those out there who have little knowledge of such terminology. So hopefully, the next few blogs will elucidate my ramblings for those out there who may actually be interested :).

A couple of FYI’s before I begin.

1. I’ll be using the same notation as Wellenhof et al., and I recommend it for anyone interested in the principles of GPS…IMHO it’s the best book out there on the subject.

2. If you would like to test your own code, you’re more than welcome to use the test datasets which I’ve used.For the purposes of this study, I use observations from two Continuously Operating Reference Stations (CORS) in Ohio, which are located Southeast of Cleveland.The first site is OHLO, the second is ZOB1, and they are located ~1 km apart from each other, which is a typical baseline length for cm level positioning.

http://www.ngs.noaa.gov/cgi-cors/corsage.prl?site=OHLO

http://www.ngs.noaa.gov/cgi-cors/corsage.prl?site=ZOB1

If you click on “Standard Files”, you will be directed to the following NGS site (http://www.ngs.noaa.gov/CORS/standard1.shtml).The RINEX files can be downloaded for each observation site for a given date.

* Note, you will need the navigation files as well, which describe the position of the GPS satellites at different measurement epochs.

**If you can’t figure it out, send me a message and I’ll be glad to email the necessary files.

**Okay, lets begin.**

One of the most important factors in precise positioning applications is baseline length, i.e. the geometric distance between the two GPS receivers. With short baselines, certain simplifications/assumptions can be made due in notation, due to similarities in the ionospheric and tropospheric path that both signals had to pass through as they traveled towards earth. As the baseline length increases, these simplifications are no longer valid, but for our purposes (short baseline), they are sufficient.

The double difference observation for short baselines is given in the following notation.

Where

is the wavelength of the frequency L1 or L2 frequency.

is the *double-differenced* phase measurement from two satellites (j,k) and two receivers (A,B).

is the double-differenced geometric distance between the satellites in space and the receivers on the ground.

is the double-differenced integer ambiguity of the phase measurements. It **must** be an integer! (e.g. 1, 3, 21, etc.)

Note that for dual frequency receivers, we could form this operation on *both* frequencies, i.e. L1 and L2.Often, authors will refer to as the *geometry term*. As we will see in later posts, we need to know the geometry term to a certain degree of accuracy in order to resolve the integer ambiguities.

Assuming we correctly read in the observations from the RINEX file, what do we do next? Well, we must first compute an approximate location for the roving receiver, because this location is embedded in the geometry term of the above equation. For starters, we could use the known position of the base station. Remember that we assume one of the receivers to be located at a known position (base station), because we will need to hold that position fixed in order to estimate the location of the other receiver(rover). With an approximate location of the rover estimated, and a sufficient amount of observations, we can solve for our unknowns via a least squares solution (LSS). Because the equation above is non-linear, we linearize it about the approximate receiver location, and solve for the unknowns, which are

as well as for each n-1 satellite combination, where n is the number of satellites. The reason there is n-1 integer combinations is because we use a pivot satellite for each double-differenced phase observation, thus the j in would remain fixed to the pivot satellite, leaving n-1 integer combinations.

Assuming we have done everything correctly, we will have what is known as a *float solution*. Because least squares doesn’t know any better, it estimates the integer ambiguities to be real-valued numbers, which we know to be untrue. The accuracy of the float solution is shown below for 100 epochs of data.

Looking at the figure above, we can see the accuracy of the float solution is generally on the order of 0.5-2m, a significant improvement from absolute positioning. However, its not 2-5 cm accuracy we expect from survey grade GPS receivers! So how do we improve the float solution so that we can achieve higher accuracies(such as the plot below)?

**Stay tuned!**

Very well explained. Any difficulties/problems you had in computing the float solution?

Lots of difficulties, mainly due to coding blunders, or wrong signage :). In theory however, the LSS is pretty straightforward.

Could you explain what GPS float is?

Yuan,

“GPS Float” refers to a common least squares solution for GPS/GLONASS positioning. In order to do high accuracy positioning (cm level), we must resolve the correct integer amount of carrier phase (L1 and/or L2) cycles between the reference satellite and our GPS receiver. This unknown integer amount of cycles is referred to as the

integer ambiguityin typical textbooks. There is only one true integer, and we must know what it is for each satellite in order to get cm level accuracy.The GPS float solution is often used as the first step towards finding the true integer. Once you’ve computed the GPS float solution, you can use the estimated integer ambiguities and their associated covariance matrices in a program like LAMBDA to find the true integers.

To recap, using the psuedorange and carrier phase measurements (which ive described in my post), we estimate the unknown integers and position in a least squares solution. However, the least squares solution doesn’t estimate the integer ambiguity as an integer, rather as a real number. For example, if the correct integer amount of carrier phase cycles was 24, the GPS float solution might estimate the integer as 23.873, a real valued number. The position accuracy of the GPS float solution is ~.5 meters, which may be good enough for your particular task. However, if you would like cm level accuracy, you will have to correctly resolve the integer ambiguities.