<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>http://flysight.ca/wiki/index.php?action=history&amp;feed=atom&amp;title=Data_models</id>
		<title>Data models - Revision history</title>
		<link rel="self" type="application/atom+xml" href="http://flysight.ca/wiki/index.php?action=history&amp;feed=atom&amp;title=Data_models"/>
		<link rel="alternate" type="text/html" href="http://flysight.ca/wiki/index.php?title=Data_models&amp;action=history"/>
		<updated>2026-08-20T01:02:35Z</updated>
		<subtitle>Revision history for this page on the wiki</subtitle>
		<generator>MediaWiki 1.29.1</generator>

	<entry>
		<id>http://flysight.ca/wiki/index.php?title=Data_models&amp;diff=15&amp;oldid=prev</id>
		<title>WikiSysop: Created page with &quot;Several sources of error make raw GPS measurements inaccurate. To make up for this, consumer GPS receivers use a &quot;model&quot; to help determine what part of the measurement is erro...&quot;</title>
		<link rel="alternate" type="text/html" href="http://flysight.ca/wiki/index.php?title=Data_models&amp;diff=15&amp;oldid=prev"/>
				<updated>2016-02-08T07:28:43Z</updated>
		
		<summary type="html">&lt;p&gt;Created page with &amp;quot;Several sources of error make raw GPS measurements inaccurate. To make up for this, consumer GPS receivers use a &amp;quot;model&amp;quot; to help determine what part of the measurement is erro...&amp;quot;&lt;/p&gt;
&lt;p&gt;&lt;b&gt;New page&lt;/b&gt;&lt;/p&gt;&lt;div&gt;Several sources of error make raw GPS measurements inaccurate. To make up for this, consumer GPS receivers use a &amp;quot;model&amp;quot; to help determine what part of the measurement is error. Basically, the model tells the receiver what kind of motion it can expect. If a measurement indicates motion that doesn't fit the model, then the receiver assumes it must be noise, and ignores it.&lt;br /&gt;
&lt;br /&gt;
In many consumer GPS receivers, the model is presented as a choice between &amp;quot;car&amp;quot; and &amp;quot;pedestrian&amp;quot; modes. In the FlySight, a few more choices are available, and it's not too hard to guess what kind of motion each might assume:&lt;br /&gt;
&lt;br /&gt;
{|border=&amp;quot;1&amp;quot; cellpadding=&amp;quot;3&amp;quot; cellspacing=&amp;quot;0&amp;quot; align=&amp;quot;center&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
|'''Model'''&lt;br /&gt;
|'''Expected motion'''&lt;br /&gt;
|-&lt;br /&gt;
|Portable&lt;br /&gt;
|Unknown&lt;br /&gt;
|-&lt;br /&gt;
|Stationary&lt;br /&gt;
|No motion&lt;br /&gt;
|-&lt;br /&gt;
|Pedestrian&lt;br /&gt;
|Slow, mostly horizontal motion&lt;br /&gt;
|-&lt;br /&gt;
|Automotive&lt;br /&gt;
|Fast, mostly horizontal motion&lt;br /&gt;
|-&lt;br /&gt;
|Sea&lt;br /&gt;
|Entirely horizontal motion&lt;br /&gt;
|-&lt;br /&gt;
|Airborne&lt;br /&gt;
|3D motion with limited acceleration&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
It's important to understand the role the model plays. For example, if you set the FlySight to use the &amp;quot;Pedestrian&amp;quot; model, and then you jump from a plane, it will try to reconcile your rapid descent with its idea of how a pedestrian moves.&lt;br /&gt;
&lt;br /&gt;
Less obviously, if you tell the FlySight to use the &amp;quot;Airborne &amp;lt; 1G&amp;quot; model, and then you perform a maneuver which results in more than 1G acceleration, the FlySight will &amp;quot;overshoot&amp;quot;, because it chalks some of that acceleration up to noise.&lt;br /&gt;
&lt;br /&gt;
When flying a wingsuit, we recommend the &amp;quot;Airborne &amp;lt; 1G&amp;quot; model. For swoopers, we recommend the &amp;quot;Airborne &amp;lt; 2G&amp;quot; model&amp;quot;, since high performance landings can generate more than 1G acceleration.&lt;/div&gt;</summary>
		<author><name>WikiSysop</name></author>	</entry>

	</feed>