doaaron said:
I think that the clock signal that the reference frame receives from the GPS satellite will still be different depending on where he is on Earth due to the difference in relative velocities.
The frequency of the radio signal received from the GPS satellite by the Earth receiver will be different, yes. (Note that this frequency is not just affected by relative speed--it's also affected by the passage of the signal through the Earth's ionosphere, which contains charged particles that do various things to radio signals passing through.) But that frequency is not the "clock signal". The "clock signal" is a digital message encoded in the radio signal; it is the same message regardless of the frequency of the signal. The only thing the frequency change affects is what bandwidth the antenna has to have in order to be sure of receiving the signal.
doaaron said:
I'm also not quite convinced by this argument.
Then I strongly suggest that you actually look at the math instead of trying to make arguments based on your intuitive understanding.
doaaron said:
Just taking a hypothetical example, suppose we have 3 clocks, and A is taken as the rest frame, B is moving in the -x direction with speed v, and C is moving in the +x direction with speed v.
Speed is only one thing that affects time dilation in the gravitational field of a static, massive body like the Earth; the other is altitude. You need to take that into account.
Also, you need to be careful to distinguish "clock rate" and "clock synchronization". They are not necessarily the same. See below.
doaaron said:
My point is that even if two clocks appear to be synchronized (the one at the equator and the one at the pole), it doesn't mean that a third clock moving in a different frame will show the same time wrt those two clocks.
This is true in general; but the specific application I think you intend here is not correct.
Consider three clocks: clock A at the North Pole, clock B at the equator at 0 degrees longitude, and clock C at the equator at 180 degrees longitude. Relative to an inertial frame centered on the Earth, these three clocks all have different speeds: clock A is at rest, clock B is moving at about +450 m/s (call this speed ##v##), and clock C is moving at about -450 m/s (i.e., ##-v##). Also, clock A is at altitude ##R## (the polar radius of the Earth), while clocks B and C are at altitudes ##R + h## (where ##h## is the height of the Earth's equatorial bulge).
Let me first give the correct GR formula for the rates of these clocks. In an inertial frame centered on the Earth (i.e., not rotating), the rate of a clock at altitude ##r## (distance from the center of the Earth) and with speed ##v## is
$$
\frac{d\tau}{dt} = \sqrt{ 1 - \frac{2 G M}{c^2 r} - \frac{v^2}{c^2}}
$$
where a clock rate of ##1## corresponds to an observer at rest at infinity (i.e., very far away from the Earth, so the effect of the Earth's gravity is negligible). If you plug in values for the three clocks, A, B, and C, you will see that they all give the same answer for ##d\tau / dt## to a good approximation--the effect of the increase in ##r## for clocks B and C is compensated for by the effect of the nonzero ##v##. (A better approximation would apply a correction for the Earth's quadrupole moment, but we won't go into that here.) So all three clocks have the same clock rate, relative to an inertial frame centered on the Earth.
The GPS system actually applies a correction to the Earth-centered inertial frame I described just now. The correction is to rescale all clock rates so that a clock rate of ##1## corresponds to the clock rate of an observer at rest on Earth at sea level. That is, clock rates are rescaled so that clocks A, B, and C all have clock rates of ##1##, and thus the clock rate of an observer at rest at infinity is now greater than ##1##--it is the reciprocal of the (less than ##1##) rate for clocks A, B, and C calculated from the above formula. So the "GPS clock rate" of a given clock is ##d\tau / dt## for that clock, calculated from the above formula, divided by ##d\tau / dt## for the reference clock (clock A, B, or C--they're all the same). The clocks on all the GPS satellites have their rates adjusted so that they effectively tick at the same rate as the reference clock; i.e., their adjusted GPS clock rates are all ##1##.
However, having the same clock rate is not sufficient for clock synchronization. Consider clocks A, B, and C again. Each of these clocks is at rest in a different inertial frame (and for clocks B and C, which inertial frame they are at rest in changes as the Earth rotates). So even if they are all running at the same rate, they don't all have the same "natural" simultaneity convention--that is, the inertial frames in which they are at rest do not agree on which events happen "at the same time". So in order to fully synchronize these clocks, we have to agree on a single simultaneity convention that they all will share (even if it is not the "natural" simultaneity convention for the inertial frame in which they are at rest). The convention that used for GPS is that of the Earth-centered inertial frame (which is the same as the "natural" simultaneity convention of clock A). All GPS clocks have their definition of what events happen "at the same time" (which basically means what time counts as "time zero" for the clock) adjusted to be the same as that of the reference clock.
So the sense in which the GPS clocks are "synchronized" is, if you want to look at it that way, "artificial"--both the rates and the simultaneity conventions of GPS clocks are changed from their "natural" ones, in order to impose a common convention on all of them. There is nothing wrong with this: it has to be done as a practical matter in order for GPS to work. But it does mean that you can't just apply your intuitions about the "natural" rates of clocks in various states of motion (or even at various altitudes) if you want to understand how timing in the GPS system works.