Location: the receiver, the clock and the region
A satellite receiver is a small radio that listens to navigation satellites and works out, from the timing of their signals, where it is and what time it is. Most desktop systems and many laptops carry no receiver at all, so where they appear to be is worked out some other way: from the address their connection comes from, or from the wireless networks around them. Websites ask the browser for a location and are answered only if the visitor agrees, installed software reads the sensor and the system settings directly, and a virtual machine has neither an antenna nor a sky.
What a location source is
A PC can know where it is in only a few ways. A receiver hears navigation satellites, measures how long each signal took to arrive, and derives from that both a position and a precise time; it needs a clear view of the sky, and it reports how good its result is. A network lookup takes the address the connection comes from, or the wireless networks the system can hear, and matches them against a catalog of known places. A location can also be set by hand. Around all of this sit values that are not a location but travel with it everywhere: the time zone the system keeps, whatever sets its clock, the country it is configured for and the languages it prefers.
How websites see it
A page cannot reach a receiver, and it cannot ask the operating system anything. It asks the browser for a location, the browser asks the visitor, and unless the visitor agrees no coordinates are handed over. An answer, when it comes, is a position with a radius of accuracy around it and nothing about its origin: the page is not told whether a receiver produced it or a lookup did. What a page sees without asking matters more. The address the connection comes from arrives with the request; the time zone the system is set to, its offset from universal time and the languages the browser prefers are all readable from a script, as is the system clock, which a page can compare against its own. So a page that never asks for a location still places its visitor in a region, and notices when those signals point at different ones.
How installed software sees it
A program on the system is not limited to what the browser chooses to expose. Through the operating system it can find out whether a location sensor is present at all and read it when it is: the position, the accuracy, the satellites in view and the strength of their signals. It reads the system location settings, the configured time zone, whether the clock is kept in step with a time service, the country the system is set to and the keyboard layouts a person can type with. Absence speaks too: a system that presents itself as a portable one, with no location sensor and no wireless networks in earshot, has already said something.
Why it matters for a virtual machine
A virtual machine has no antenna and no view of the sky, so there is no sensor to read. Everything it can say about where it is comes from settings, and the settings come from the image it was built from: a time zone chosen when that image was made, a region and languages put in with it, and a clock often kept in step with the host underneath — one that was paused and resumed can come back with a clock that jumped. Its connection, meanwhile, arrives from wherever the host sits. Nothing makes these agree, and when they disagree it is the plainest mismatch in the whole tour: a connection from one part of the world, a time zone set to another, a region and a language belonging to a third. This is why location belongs to the hardware identity the environment shown in this tour presents as a whole: clock, zone and region telling one story, and that story matching the network the PC is on.
What this stop of the tour shows
In this scene the camera leaves the PC and looks up, and the location fields open as a readable card: where a fix would come from, how tight it would be, what sets the clock, and which zone and region the system keeps. The card is drawn on the page rather than painted into the video, so it stays legible in every language and can be read without the animation. The next stop moves to the wired network adapter.
| Field | What it says |
|---|---|
| Fix source | Where a reported position came from: a receiver, a lookup against the network the system is on, or a value set by hand. A page is given the position, not the source. |
| Accuracy | The radius the position is reported within. A receiver under open sky gives a tight one; a lookup against the address a connection comes from can be no better than the city. |
| Satellites in view | Which navigation satellites the receiver can hear and how strong each signal is. Only a real receiver has anything to report here, and only through the operating system. |
| Time source | What the clock is set from: a time service on the network, a receiver that takes its time from the satellite signals, or, inside a virtual machine, the host underneath. |
| Time zone | The zone the system is set to, as a region name and an offset from universal time. Any page reads it without asking. |
| Region | The country the system is configured for and what follows from it: the order of date parts, the decimal mark, the units, the languages and the keyboard layouts. |