Your arguably reasonable recoding of the geo uri&#39;s of your example illustrates an issue on which so much metadata is silent: provenance. Once exposed, it is probably impossible for someone to know how the uncertainty (or any other data that might be the subject of opinion or estimate) was determined and whether the data is fit for some particular purpose, e.g. that the species were observed near each other. <div>
<br></div><div>BTW, the IETF geo proposal was adopted in 2010, in the final form given at <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://tools.ietf.org/html/rfc5870">http://tools.ietf.org/html/rfc5870</a> . One interesting point is <meta http-equiv="content-type" content="text/html; charset=utf-8"><a href="http://tools.ietf.org/html/rfc5870#section-3.4.3">http://tools.ietf.org/html/rfc5870#section-3.4.3</a> which says </div>
<div>  &quot;<span class="Apple-style-span" style="white-space: pre; "><font class="Apple-style-span" face="arial, helvetica, sans-serif">Note: The number of digits of the values in &lt;coordinates&gt; MUST NOT be</font></span><span class="Apple-style-span" style="font-family: arial, helvetica, sans-serif; white-space: pre; "> interpreted as an indication to the level of uncertainty.&quot;  The section following is also interesting, albeit irrelevant for your procedure. It implies that when uncertainty is omitted (and therefore unknown), then &quot;</span>geo:41.53000000,-70.67000000&quot;  and &quot;geo:41.53,-70.67&quot;  identify  the same geo resource.</div>
<meta http-equiv="content-type" content="text/html; charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div><br></div><div><br></div><div>Bob Morris</div><div><br><div class="gmail_quote">On Wed, Feb 23, 2011 at 4:56 PM, Peter DeVries <span dir="ltr">&lt;<a href="mailto:pete.devries@gmail.com">pete.devries@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><br clear="all">[...]<br>
<div><br></div><div>5) I added in my proposed &quot;area&quot; so that it is easy to see what species were observed near each other. Since there was no measure of radius in these longitude and latitudes I made the radius 100 meters.</div>

<div>    Normally I would estimate the radius for a GPS reading to be within 10 meters but some of these observations were made where the GPS reading was taken and the readings were given only to two decimals.</div><div>
<br>
</div><div>Area = long, lat; radius in meters following the ietf proposal but with the precision of the long and lat standardized example &quot;geo:41.53000000,-70.67000000;u=100&quot;</div><div><br></div><div>[...]</div>
</blockquote></div>-- <br>Robert A. Morris<br>Emeritus Professor  of Computer Science<br>UMASS-Boston<br>100 Morrissey Blvd<br>Boston, MA 02125-3390<br>Associate, Harvard University Herbaria<br>email: <a href="mailto:morris.bob@gmail.com" target="_blank">morris.bob@gmail.com</a><br>
web: <a href="http://efg.cs.umb.edu/" target="_blank">http://efg.cs.umb.edu/</a><br>web: <a href="http://etaxonomy.org/mw/FilteredPush" target="_blank">http://etaxonomy.org/mw/FilteredPush</a><br><a href="http://www.cs.umb.edu/~ram" target="_blank">http://www.cs.umb.edu/~ram</a><br>
phone (+1) 857 222 7992 (mobile)<br><br>
</div>