<?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: Determining GPS Circular Error Of Probability (CEP)</title>
	<atom:link href="http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/feed" rel="self" type="application/rss+xml" />
	<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep</link>
	<description>Exploring the world of free tools for GIS, GPS, Google Earth, neogeography, and more.</description>
	<lastBuildDate>Thu, 09 Feb 2012 04:48:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Leszek Pawlowicz</title>
		<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/comment-page-1#comment-1500</link>
		<dc:creator>Leszek Pawlowicz</dc:creator>
		<pubDate>Sun, 16 Aug 2009 02:42:31 +0000</pubDate>
		<guid isPermaLink="false">http://freegeographytools.com/?p=3984#comment-1500</guid>
		<description>Tried it again with the Garmin at a random point, with the antenna vertical:

    50% = 0.49
    90% = 0.79
    95% = 0.91
    98% = 1.40

Results are better, but there was still a NW-SE axis to the data. If I get more time and two Garmins, I&#039;ll try to compare horizontal and vertical at the same time.</description>
		<content:encoded><![CDATA[<p>Tried it again with the Garmin at a random point, with the antenna vertical:</p>
<p>    50% = 0.49<br />
    90% = 0.79<br />
    95% = 0.91<br />
    98% = 1.40</p>
<p>Results are better, but there was still a NW-SE axis to the data. If I get more time and two Garmins, I&#8217;ll try to compare horizontal and vertical at the same time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill01</title>
		<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/comment-page-1#comment-1499</link>
		<dc:creator>Bill01</dc:creator>
		<pubDate>Sat, 08 Aug 2009 12:23:45 +0000</pubDate>
		<guid isPermaLink="false">http://freegeographytools.com/?p=3984#comment-1499</guid>
		<description>Standing the Garmin up will make quite a difference as opposed to laying it down, having considerable (daily) time with GPS60, 60CSX, Trimble GeoXH (2008 Series)&amp; GeoExplorer3 w/wo Hurricane &amp; Zephyr antenna setups, Magellan Triton 500 and 1500, DeLorme PN-20 &amp; PN-40, and Ashtech (Thales/Magellan) ProMark 2 &amp; Promark 3 units, over the last 5 years.  The Garmin was meant to be used pointed upward for best acqusition (quadrifillar-helix) versus Holux glorified patch (like the Trimbles) face-up orientation for best acquisition.  Try it again.</description>
		<content:encoded><![CDATA[<p>Standing the Garmin up will make quite a difference as opposed to laying it down, having considerable (daily) time with GPS60, 60CSX, Trimble GeoXH (2008 Series)&amp; GeoExplorer3 w/wo Hurricane &amp; Zephyr antenna setups, Magellan Triton 500 and 1500, DeLorme PN-20 &amp; PN-40, and Ashtech (Thales/Magellan) ProMark 2 &amp; Promark 3 units, over the last 5 years.  The Garmin was meant to be used pointed upward for best acqusition (quadrifillar-helix) versus Holux glorified patch (like the Trimbles) face-up orientation for best acquisition.  Try it again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nick Hopton</title>
		<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/comment-page-1#comment-1498</link>
		<dc:creator>Nick Hopton</dc:creator>
		<pubDate>Thu, 30 Jul 2009 09:36:39 +0000</pubDate>
		<guid isPermaLink="false">http://freegeographytools.com/?p=3984#comment-1498</guid>
		<description>Remember that you&#039;re dealing with GPS data downloaded as WGS84 by DNR Garmin (DNRG) and projected to a local coordinate reference system. DNRG uses Proj4 to do the projecting and I don&#039;t know how accurate this is likely to be in your part of the world. In my neck of the woods, southern England, I get an error of about 1.5 metres when projecting from WGS84 to OSGB using DNRG. It might be worth checking what your conversion errors are.

Regards, N.</description>
		<content:encoded><![CDATA[<p>Remember that you&#8217;re dealing with GPS data downloaded as WGS84 by DNR Garmin (DNRG) and projected to a local coordinate reference system. DNRG uses Proj4 to do the projecting and I don&#8217;t know how accurate this is likely to be in your part of the world. In my neck of the woods, southern England, I get an error of about 1.5 metres when projecting from WGS84 to OSGB using DNRG. It might be worth checking what your conversion errors are.</p>
<p>Regards, N.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Terry</title>
		<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/comment-page-1#comment-1497</link>
		<dc:creator>Terry</dc:creator>
		<pubDate>Wed, 29 Jul 2009 17:38:26 +0000</pubDate>
		<guid isPermaLink="false">http://freegeographytools.com/?p=3984#comment-1497</guid>
		<description>I don&#039;t think it really make a difference if the benchmark was off.  Looking back at your earlier post, I&#039;m inclined to believe that the answer lies in the position plots.  While the Garmin&#039;s plots seem to be widely scattered, they&#039;re widely scattered in pretty much all directions.  The Holux&#039;s points, while having a much tighter grouping, seem to concentrate themselves in three principle directions (generally, East, West and Southwest).  The Holux plots are notably absent Northward and Southeastward.  It just stands to reason that the Garmin would average closer to the center, regardless of where that center actually is.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think it really make a difference if the benchmark was off.  Looking back at your earlier post, I&#8217;m inclined to believe that the answer lies in the position plots.  While the Garmin&#8217;s plots seem to be widely scattered, they&#8217;re widely scattered in pretty much all directions.  The Holux&#8217;s points, while having a much tighter grouping, seem to concentrate themselves in three principle directions (generally, East, West and Southwest).  The Holux plots are notably absent Northward and Southeastward.  It just stands to reason that the Garmin would average closer to the center, regardless of where that center actually is.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PMarc</title>
		<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/comment-page-1#comment-1496</link>
		<dc:creator>PMarc</dc:creator>
		<pubDate>Wed, 29 Jul 2009 13:30:28 +0000</pubDate>
		<guid isPermaLink="false">http://freegeographytools.com/?p=3984#comment-1496</guid>
		<description>I would serioulsy survey that point with a DGPS.

Not that I would doubt the benchmark position, except when known or when the BM has been placed at an obviusly bad place (I&#039;ve seen one put over a landfill). In any case, ask the NGS as to when the BM was last resurveyed.</description>
		<content:encoded><![CDATA[<p>I would serioulsy survey that point with a DGPS.</p>
<p>Not that I would doubt the benchmark position, except when known or when the BM has been placed at an obviusly bad place (I&#8217;ve seen one put over a landfill). In any case, ask the NGS as to when the BM was last resurveyed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Peter Guth</title>
		<link>http://freegeographytools.com/2009/determining-gps-circular-error-of-probability-cep/comment-page-1#comment-1495</link>
		<dc:creator>Peter Guth</dc:creator>
		<pubDate>Wed, 29 Jul 2009 13:06:31 +0000</pubDate>
		<guid isPermaLink="false">http://freegeographytools.com/?p=3984#comment-1495</guid>
		<description>I would seriously consider the accuracy of the benchmark.  I&#039;ve had students do a lab with cheap old Garmin ETREX units to get the location of a tidal benchmark, and we always get differences from the NOAA position about what you&#039;re getting.  I also know that the bench mark in question was physically moved when the pier was refurbished, and cannot get any word from NOAA that they resurveyed it, and the station history does not reflect the move.

The other thing that I would look at is quantization of the positions--with our units you can only get values that are about 1 m apart, and nothing in between (it&#039;s actually 0.01 minute, I think).  I don&#039;t know if newer units change this, or if the method affects the results--we download the tracks.  For most uses the level of accuracy is good enough, and the quantization makes a good student learning point.</description>
		<content:encoded><![CDATA[<p>I would seriously consider the accuracy of the benchmark.  I&#8217;ve had students do a lab with cheap old Garmin ETREX units to get the location of a tidal benchmark, and we always get differences from the NOAA position about what you&#8217;re getting.  I also know that the bench mark in question was physically moved when the pier was refurbished, and cannot get any word from NOAA that they resurveyed it, and the station history does not reflect the move.</p>
<p>The other thing that I would look at is quantization of the positions&#8211;with our units you can only get values that are about 1 m apart, and nothing in between (it&#8217;s actually 0.01 minute, I think).  I don&#8217;t know if newer units change this, or if the method affects the results&#8211;we download the tracks.  For most uses the level of accuracy is good enough, and the quantization makes a good student learning point.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

