Live data from Hacker News

GPS

ciechanow.ski

181–190 of 296 posts

Re: GPS

#181

It's so depressing that – at some point in the future – I'm going to want a really clear and precise explanation of how GPS works and the likelihood that an internet search directs me to this excellent, clean, and ad-free blog is essentially nil.

I searched for an excellent, clear and precise explanation of GPS that is clean and ad-free, and landed on your comment.

Re: GPS

#182

Earlier quoted context omitted.

Then you’d have a Stratum 0 source for a stratum 1 NTP server!

Which is what Google did to have a quality time-source for synchronized time for their global database: https://www.wired.com/2012/11/google-spanner-time/

> ... quality time-source ...

Except they decided to "smear" leap seconds [0], instead of handling them appropriately.

For that reason, if you "require correct timestamps for legal purposes" [1], you may want to make sure that you aren't using Google's NTP servers.

(N.B.: Amazon (AWS) too, FWIW.)

---

[0]: https://developers.google.com/time/smear

[1]: https://docs.ntpsec.org/latest/leapsmear.html

Re: GPS

#183

It's so depressing that – at some point in the future – I'm going to want a really clear and precise explanation of how GPS works and the likelihood that an internet search directs me to this excellent, clean, and ad-free blog is essentially nil.

I searched for an excellent, clear and precise explanation of GPS that is clean and ad-free, and landed on your comment.

  I know not by what tools Web 3.0 content will be found, but Web 4.0 will be searched using hn comment breadcrumbs.

Re: GPS

#184

There's a lot of really great info in here. One random things I learned from this: > As that angle increases, the signal from a satellite travels more sideways and its larger portion gets affected by the atmosphere. To account for this, GPS receivers ignore ranges measured from satellites at very low elevation angles. ... atmospheric effects are primary source of GPS inaccuracies. (I know GPS has inaccuracies, but I…

Something not mentioned: the "new" L5 signal at 1176Mhz, combined with the existing L1 signal at 1575Mhz, allows the receiver to estimate the atmospheric effects and reduce the uncertainty, allowing for a much better position fix. Think centimeters instead of meters. One more thing I've wondered: the system depends on the sattelites knowing and broadcasting their exact position, but how do you determine this position…

Look up GPS operation control segment (OCX). Currently it's mostly Airforce and JPL, transitioning to Space Force. Lots of details published.

Re: GPS

#185

It's so depressing that – at some point in the future – I'm going to want a really clear and precise explanation of how GPS works and the likelihood that an internet search directs me to this excellent, clean, and ad-free blog is essentially nil.

I searched for an excellent, clear and precise explanation of GPS that is clean and ad-free, and landed on your comment.

You may be on to something here. With GPT-3 you could improve the quality of the responses by starting with a prompt like, "You're a well-educated and very helpful individual".

Maybe internet searches can be improved by changing the search from "how gps works" to "excellent, clear, and precise explanation of gps"?

Re: GPS

#186

From the toy model it seems like if in addition to distance you could also get your angle to the landmark then you could get your position from a single landmark. Is that something which is practical? Knowing which angle a radio signal came from? It seems like if you had several receivers you could use the timings of when they receive a message to determine the approximate direction of the satellite in the sky. Given…

Assisted GPS in phones can augment GPS data with information coming from cell towers nearby. From a quick search, some are omni-directional while others operate in a specific direction. Depending on reported signal strength, you could get some hints on the angle as well.

Re: GPS

#187
post #163
post #124

Earlier quoted context omitted.

I agree with the meta interview concept, but I don't think that applies here because of the OP's last sentence: >Amazing that even engineers don't understand that GPS receivers don't talk to the satellites. They're amazed at the lack of knowledge, not that a candidate wasn't able to talk it out, or that they bs-ed through it. That tells me the question is asked in bad faith.

Again, that's not necessarily how that's intended. The observation on its own is just an observation, it doesn't indicate anything about how interview performance was evaluated. For example when I interview, I have a question related to chess, which requires a basic understanding of how the pieces move. I was amazed that even engineers don't understand the basic movement rules of chess. However as far as the intervie…

As an interviewer, where there's a huge power imbalance, why even stray into the territory where candidate can easily perceive a disadvantage for not having totally unrelated knowledge? A candidate will feel like their lack of chess knowledge, or GPS knowledge, hurt them if they didn't perform well. Why not just ask questions that are relevant to the work they will be doing? Maybe you don't realize just how stressful interviews are to some people, and how much they have to prepare, only to be asked to reverse engineer how GPS works.

Re: GPS

#188
post #130

Earlier quoted context omitted.

Do you have experience interviewing or seeing interview questions in those fields?

Yes, you will be asked to showcase 2-3 side-projects such as houses, bridges and tunnels you built & designed in your backyard and discuss your design decisions on a whiteboard.

Maybe a take-home exercise, like a small viaduct or a dome.

Re: GPS

#189
post #28

If all of the teaching materials would be so good... I've encountered first GPS devices back 1997.i remember when my coulegues were explaining them to me. At that time you wouldn't get precise measurements right away. You had to wait for correction factors or something like that. The GPS signal was scrambled at that time.

That's post-processing, and it's still done. Here's why:

The satellites only know their own position to a certain precision, and there are only so many bits to express it in the data packet. More bits wouldn't make sense because the measurements aren't that good in the first place.

So what you get "live" is naturally limited by both of those things. Single-frequency unassisted solutions are usually good to a few meters, dual-frequency to a meter or so.

But ground stations can determine, after observing the satellites for a long time, where they _were_ to a much higher accuracy. It's a complicated process involving a whole network of ground stations, whose own positions are precisely surveyed, etc.

The product of that network is known as "precise ephemeris", and it's available in an "ultra-rapid" (3-9 hours later), "rapid" (24 hours later), and "final" (13 days later) version. With these data, the initial observation can be post-processed to get very good solutions. Down into the millimeters.

The RTKLIB manual has a lot more detail if you're curious.

Re: GPS

#190

One of the things I love about GPS is: Since you know your exact position, you can pick a good GPS satellite (one of the satellite's you're using to calculate your position), look at the timestamp from that satellite, and use it as a highly-accurate time source! Purpose-built GPS time servers (like those from Meinberg) give you an option to enter the length of the coax cable connecting the receiver and the antenna, s…

It's a bit more complex than this, the entire GPS fix is 4D since position depends on time and vice versa. The time reported by a GPS receiver, once fix is attained, is not just the time from one of the satellites but the time resulting from the 4D fix in space and time. This eliminates (to within a certain precision) the latency. A lot of discrete GPS receivers have some nonvolatile storage where they "cache" fixes…

Yup, that's covered by the functions on Pages 20 and 21, which let you either completely wipe all stored state, or update it to account for being moved a long distance (while still retaining satellite data).
Post reply on HN