<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: How GPS Receivers Work &#8211; Trilateration vs Triangulation	</title>
	<atom:link href="https://gisgeography.com/trilateration-triangulation-gps/feed/" rel="self" type="application/rss+xml" />
	<link>https://gisgeography.com/trilateration-triangulation-gps/</link>
	<description>Geographic Information Systems</description>
	<lastBuildDate>Thu, 19 Jun 2025 20:34:46 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.8.3</generator>
	<item>
		<title>
		By: Robbbbb		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-395387</link>

		<dc:creator><![CDATA[Robbbbb]]></dc:creator>
		<pubDate>Thu, 19 Jun 2025 20:34:46 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-395387</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://gisgeography.com/trilateration-triangulation-gps/#comment-360564&quot;&gt;S. McBride&lt;/a&gt;.

Hi Lazer, I couldn&#039;t reply to your actual comment, so I&#039;ll reply to S. McBride and hope you see it!

The time difference is computed by autocorrelation. Very basically,
The first bit from signal one is multiplied by the first bit of signal two. For example, if the first bits from the two signals both have values −1, then the result is (−1) × (−1) = +1. Similarly, if both bits have values +1, then the result is +1. On the other hand, if the two bits disagree, the result is (+1) × (−1) = −1. This process is repeated for the second pair of bits, and so on. The result can be written as a sequence of +1 (where the bits agree) and -1 (where the bits disagree). This sequence is then summed, and divided by the total number of bits in each signal. For example, if signal A can be written (+1, −1, −1, +1, −1), and signal B can be written (+1, +1, −1, −1, +1), then multiplication gives (+1, −1, +1, −1, −1); the sum of which gives −1; then dividing by the number of bits (5) gives −0.2.

When the two signals are not properly matched in time, the result of autocorrelation gives an answer close to zero; if the signals are matched in time, the result is close to +1 (but not exactly, since a real signal also has noise, so some bits are incorrect). One can see that the larger the number of bits that are compared, the better the resolution. This is because the random bits will average to zero better, the more bits we compare.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://gisgeography.com/trilateration-triangulation-gps/#comment-360564">S. McBride</a>.</p>
<p>Hi Lazer, I couldn&#8217;t reply to your actual comment, so I&#8217;ll reply to S. McBride and hope you see it!</p>
<p>The time difference is computed by autocorrelation. Very basically,<br />
The first bit from signal one is multiplied by the first bit of signal two. For example, if the first bits from the two signals both have values −1, then the result is (−1) × (−1) = +1. Similarly, if both bits have values +1, then the result is +1. On the other hand, if the two bits disagree, the result is (+1) × (−1) = −1. This process is repeated for the second pair of bits, and so on. The result can be written as a sequence of +1 (where the bits agree) and -1 (where the bits disagree). This sequence is then summed, and divided by the total number of bits in each signal. For example, if signal A can be written (+1, −1, −1, +1, −1), and signal B can be written (+1, +1, −1, −1, +1), then multiplication gives (+1, −1, +1, −1, −1); the sum of which gives −1; then dividing by the number of bits (5) gives −0.2.</p>
<p>When the two signals are not properly matched in time, the result of autocorrelation gives an answer close to zero; if the signals are matched in time, the result is close to +1 (but not exactly, since a real signal also has noise, so some bits are incorrect). One can see that the larger the number of bits that are compared, the better the resolution. This is because the random bits will average to zero better, the more bits we compare.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Lazer		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-381716</link>

		<dc:creator><![CDATA[Lazer]]></dc:creator>
		<pubDate>Thu, 17 Apr 2025 21:00:22 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-381716</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://gisgeography.com/trilateration-triangulation-gps/#comment-360564&quot;&gt;S. McBride&lt;/a&gt;.

Hi, thanks for your explanation. If I understand correctly, the receiver knows what the satellite&#039;s time was when the message was sent by the satellite, as well as what its own time is when it receives the message. But if his time and the satellite&#039;s aren&#039;t synchronized, it can&#039;t just compute dt = my_time - satellite_time.

I thought devices regularly kept themselves synchronized with the satellites&#039; time. If not, can you explain how dt is computed ?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://gisgeography.com/trilateration-triangulation-gps/#comment-360564">S. McBride</a>.</p>
<p>Hi, thanks for your explanation. If I understand correctly, the receiver knows what the satellite&#8217;s time was when the message was sent by the satellite, as well as what its own time is when it receives the message. But if his time and the satellite&#8217;s aren&#8217;t synchronized, it can&#8217;t just compute dt = my_time &#8211; satellite_time.</p>
<p>I thought devices regularly kept themselves synchronized with the satellites&#8217; time. If not, can you explain how dt is computed ?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: S. McBride		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-360568</link>

		<dc:creator><![CDATA[S. McBride]]></dc:creator>
		<pubDate>Fri, 13 Dec 2024 17:52:14 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-360568</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://gisgeography.com/trilateration-triangulation-gps/#comment-51893&quot;&gt;Stanley Achieno Oguto&lt;/a&gt;.

see my response to Alex earlier today.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://gisgeography.com/trilateration-triangulation-gps/#comment-51893">Stanley Achieno Oguto</a>.</p>
<p>see my response to Alex earlier today.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: S. McBride		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-360567</link>

		<dc:creator><![CDATA[S. McBride]]></dc:creator>
		<pubDate>Fri, 13 Dec 2024 17:46:57 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-360567</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://gisgeography.com/trilateration-triangulation-gps/#comment-31351&quot;&gt;GISGeography&lt;/a&gt;.

One misleading thing I saw is the assertion that we know the distance to each satellite.  We don&#039;t.  We do know the satellite&#039;s location from its broadcast data, but don&#039;t yet know our location (or what time our clock read when each satellite sent its timestamp).  All we can tell from the raw data is the differential distance to the satellites in use.  With four or more satellites, we can solve for our location and could perhaps synchronize our clock to GPS time.  See my response to Alex earlier today.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://gisgeography.com/trilateration-triangulation-gps/#comment-31351">GISGeography</a>.</p>
<p>One misleading thing I saw is the assertion that we know the distance to each satellite.  We don&#8217;t.  We do know the satellite&#8217;s location from its broadcast data, but don&#8217;t yet know our location (or what time our clock read when each satellite sent its timestamp).  All we can tell from the raw data is the differential distance to the satellites in use.  With four or more satellites, we can solve for our location and could perhaps synchronize our clock to GPS time.  See my response to Alex earlier today.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: S. McBride		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-360564</link>

		<dc:creator><![CDATA[S. McBride]]></dc:creator>
		<pubDate>Fri, 13 Dec 2024 16:59:06 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-360564</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://gisgeography.com/trilateration-triangulation-gps/#comment-296501&quot;&gt;Alex Goresin&lt;/a&gt;.

Good question and one that at least most websites do not appear to address correctly.  
If we assume that the receiver&#039;s clock is not synchronized to the satellites, then the data you start with are time difference dt and satellite location Sxyz from each satellite.  
The system of vector equations to solve to find your location Lxyz is &#124;Sxyz - Lxyz&#124; - D0 = c*dt, where D0 is the unknown distance to the arbitrary satellite assigned dt=0 and c is the speed of light.  That has four unknowns Lxyz and D0, so at least four satellites are needed.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://gisgeography.com/trilateration-triangulation-gps/#comment-296501">Alex Goresin</a>.</p>
<p>Good question and one that at least most websites do not appear to address correctly.<br />
If we assume that the receiver&#8217;s clock is not synchronized to the satellites, then the data you start with are time difference dt and satellite location Sxyz from each satellite.<br />
The system of vector equations to solve to find your location Lxyz is |Sxyz &#8211; Lxyz| &#8211; D0 = c*dt, where D0 is the unknown distance to the arbitrary satellite assigned dt=0 and c is the speed of light.  That has four unknowns Lxyz and D0, so at least four satellites are needed.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Michael		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-333654</link>

		<dc:creator><![CDATA[Michael]]></dc:creator>
		<pubDate>Fri, 24 May 2024 17:01:59 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-333654</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://gisgeography.com/trilateration-triangulation-gps/#comment-52287&quot;&gt;GISGeography&lt;/a&gt;.

You just stated the reason. Could you explain it?]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://gisgeography.com/trilateration-triangulation-gps/#comment-52287">GISGeography</a>.</p>
<p>You just stated the reason. Could you explain it?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Alex Goresin		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-296501</link>

		<dc:creator><![CDATA[Alex Goresin]]></dc:creator>
		<pubDate>Mon, 19 Jun 2023 11:05:04 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-296501</guid>

					<description><![CDATA[Hi, great explanation, one small part I&#039;m not clear on. Could you possibly explain how a GPS devices calculates the distance to a satellite?]]></description>
			<content:encoded><![CDATA[<p>Hi, great explanation, one small part I&#8217;m not clear on. Could you possibly explain how a GPS devices calculates the distance to a satellite?</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Rutabaga		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-289597</link>

		<dc:creator><![CDATA[Rutabaga]]></dc:creator>
		<pubDate>Thu, 09 Mar 2023 08:32:49 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-289597</guid>

					<description><![CDATA[Joe, no you just need a receiver that can make some calculations. The position of the satellite is known because it&#039;s floating in the vacuum of space in a very stable orbit. So using this information, you only need a small device to receive the clock signal from the satellite, and perhaps do some math accounting for the Doppler effect. From there you can calculate the origin of the spheres very accurately, and extrude them until they intersect with the spheres of the other satellites.]]></description>
			<content:encoded><![CDATA[<p>Joe, no you just need a receiver that can make some calculations. The position of the satellite is known because it&#8217;s floating in the vacuum of space in a very stable orbit. So using this information, you only need a small device to receive the clock signal from the satellite, and perhaps do some math accounting for the Doppler effect. From there you can calculate the origin of the spheres very accurately, and extrude them until they intersect with the spheres of the other satellites.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dave		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-262873</link>

		<dc:creator><![CDATA[Dave]]></dc:creator>
		<pubDate>Wed, 13 Apr 2022 23:30:24 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-262873</guid>

					<description><![CDATA[Using 3 satellites you can narrow down your GPS location to TWO points, to prove this, draw three circles that intersect each other, not touching the edges of each other. You&#039;ll see that there are 2 intersecting points, adding a forth satellite will give you your true location and correct timing errors. The National Ocean Service U.S. Department of Commerce has a great explanation with pictures explaining this.
https://oceanservice.noaa.gov/education/tutorial_geodesy/geo09_gps.html]]></description>
			<content:encoded><![CDATA[<p>Using 3 satellites you can narrow down your GPS location to TWO points, to prove this, draw three circles that intersect each other, not touching the edges of each other. You&#8217;ll see that there are 2 intersecting points, adding a forth satellite will give you your true location and correct timing errors. The National Ocean Service U.S. Department of Commerce has a great explanation with pictures explaining this.<br />
<a href="https://oceanservice.noaa.gov/education/tutorial_geodesy/geo09_gps.html" rel="nofollow ugc">https://oceanservice.noaa.gov/education/tutorial_geodesy/geo09_gps.html</a></p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: James		</title>
		<link>https://gisgeography.com/trilateration-triangulation-gps/#comment-183866</link>

		<dc:creator><![CDATA[James]]></dc:creator>
		<pubDate>Mon, 22 Mar 2021 16:13:41 +0000</pubDate>
		<guid isPermaLink="false">http://gisgeography.com/?p=12601#comment-183866</guid>

					<description><![CDATA[Very interesting.  How can I find the WGS84 of a particular place?  For instance an airport?  Is there a database to search?  Thanks for any help.]]></description>
			<content:encoded><![CDATA[<p>Very interesting.  How can I find the WGS84 of a particular place?  For instance an airport?  Is there a database to search?  Thanks for any help.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
