|
|
|
|
|
|
by thatcherc
1295 days ago
|
|
|
Section 2.1 in their linked paper (https://agupubs.onlinelibrary.wiley.com/doi/full/10.1029/201...) gives some clues. I think this is what's going on: GPS receivers work by figuring out how far away they are from a number (>3) of GPS satellites. The receiver knows where the GPS satellites are (since the satellites broadcast their orbit parameters) so if a receiver knows how far it is from several satellites it can work out where it is itself. Now, as the GPS satellite signals travel through Earth's atmosphere, they can be slowed down by different atmospheric effects. A slower signal will cause the receiver to think it's farther away from a satellite than it really is, so the receiver might estimate that it's position has changed a little bit. However, if you know the receiver's position hasn't change (maybe it's fixed in place to a big rock), then you can attribute the receiver's measured "change in position" to a change in atmosphere characteristics. In this paper, they seem to have lots of fixed GPS receivers all over the place. By looking at all of them together, they can make a sort of map of the atmosphere characters in a part of the sky that's affected by rocket launches. The authors see these big ripples emanating from a Falcon Heavy launch in the US and this tweet shows those same ripples emanating from a launch site in North Korea. |
|
|
For made up simplified example, assume you have a moving GPS in an airplane or something, and there's exactly four sats N S W E. All four sats relatively agree you're flying the plane normally in a straight ish line as usual. Suddenly, the data from the S sat gets wildly distorted, but the other three sats remain normal. I suppose the S sat could have malfunctioned but more likely something is in between your plane and the S sat. So your navigation chip tosses the data from the S sat and marks its SNR way down and generally ignores that sat... However, if you were to log that "bad" data from the sat to the south... then compare to someone flying a plane a hundred miles to your south, and their GPS reports data suddenly was trash to their north, then you know something flew between your two planes. Maybe an ICBM, maybe a thunderstorm, maybe a GPS jammer weapon, a lot of "it depends". Sometimes its the data thats tossed out thats the most interesting.
I've been fooling around with something a LOT cruder at home WRT tracking thunderstorms. Its not rocket surgery to know that severe rain attenuation can impair GPS signals. One of the standard NMEA output lines contains each sats SNR, so if I know from my "vast" database that in normal weather satellite #43 at az 45 degrees elevation 45 degrees reports a SNR of made up number -10 plus or minus 2 over the past few years, then if it reports -20 today that would imply either the sat just burned out (unlikely) or there's a rain cloud causing "about 10 dB attenuation" at az 45 degrees elevation 45 degrees relative to my house. The linked project in the article is enormously fancier of course than merely logging SNR fluctuations.
I'm amused at the idea of crowdsourcing a "large amount" of forest hiking data over time to evaluate the health of the tree canopy in forests. Where I live the leaves are all down now so GPS signals should be very strong for hikers in forests.
As the Air Force discovered decades ago, for various EE and trigonometry reasons, bistatic radar works best overhead its kind of the opposite of what you want for an early warning radar so you can see why bistatic radar never went much of anywhere compared to traditional radar for the usual Air Force mission purposes. Although there are interesting modern "IoT" distributed sensor applications, at least if you have unimpeded fast communications systems, etc.