Hi Bob,<div><br></div><div>Yes an estimate of the precision / extent should be recorded by the original observer. </div><div><br></div><div>This has been repeated several times and it is interesting that even TDWG did not incorporate this into their data collection.</div>
<div><br></div><div>What I was proposing was a specific extension to the ietf proposal for occurrence records.</div><div><br></div><div>It adds something very similar to pointRadiusSpatialFit to a latitude and longitude.</div>
<div><br></div><div>
By standardizing on the significant digits we gain something even before there is general software support for this standard.</div><div><br></div><div>That records with <span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">"geo:41.53000000,-70.67000000;u=100" are an equivalent URN, while.</span></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><font face="arial, sans-serif"><span style="border-collapse:collapse"><span style="font-family:arial;border-collapse:separate"> </span></span></font><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">"geo:41.53000000,-70.67000000;u=100" and </span><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">"geo:41.53,-70.67;u=100" are not</span></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><font face="arial, sans-serif"><span style="border-collapse:collapse"><span style="font-family:arial;border-collapse:separate"><span style="border-collapse:collapse;font-family:arial, sans-serif"></span></span>That allows those records to be linked within a triple or quadstore.</span></font></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><font face="arial, sans-serif"><span style="border-collapse:collapse">As in this earlier example:</span></font></div>
<div><font face="arial, sans-serif"><span style="border-collapse:collapse"><br></span></font></div><div><font face="arial, sans-serif"><span style="border-collapse:collapse"><meta charset="utf-8"><span class="Apple-style-span" style="font-size: 13px; "><div>
Here is a browsable view of one of the areas <a href="http://bit.ly/" target="_blank" style="color: rgb(51, 51, 204); ">bit.ly</a> <a href="http://bit.ly/hBtVFL" target="_blank" style="color: rgb(51, 51, 204); ">http://bit.ly/hBtVFL</a></div>
<div><br></div><div> <a href="http://lsd.taxonconcept.org/describe/?url=geo:41.53000000,-70.67000000;u%3D100" target="_blank" style="color: rgb(51, 51, 204); ">http://lsd.taxonconcept.org/describe/?url=geo:41.53000000,-70.67000000;u%3D100</a></div>
</span>
</span></font><div><br></div><div>Without doing anything other than standardizing on the number of digits, occurrences attached to the same GPS reading are linked in both a triple store and a google search.</div><div><br>
</div><div>Where as software needs to be written that interprets <font face="arial, sans-serif"><span style="border-collapse: collapse; "><span style="font-family: arial; border-collapse: separate; "> </span></span></font><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">"geo:41.53000000,-70.67000000;u=100" and </span><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">"geo:41.53,-70.67;u=100" as equivalent.</span></div>
<div><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">Try Googling "geo:44.86294500,-87.23120400;u=10"</span></div>
<div><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><br></span></div><div><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><meta charset="utf-8"><span class="Apple-style-span" style="font-family: arial; font-size: small; border-collapse: separate; "><div>
If the <a href="http://ietf.org">ietf.org</a> standard is supported in future versions of Virtuoso and other tools then we would not need to include the redundant use of geo:lat geo:long for the dynamic maps.</div><div><br>
</div></span></span></div><div><span style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">- Pete</span></div><meta charset="utf-8"><div><br></div><br><div class="gmail_quote">On Sat, Feb 26, 2011 at 1:01 PM, Bob Morris <span dir="ltr"><<a href="mailto:morris.bob@gmail.com" target="_blank">morris.bob@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Your arguably reasonable recoding of the geo uri'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 <a href="http://tools.ietf.org/html/rfc5870" target="_blank">http://tools.ietf.org/html/rfc5870</a> . One interesting point is <a href="http://tools.ietf.org/html/rfc5870#section-3.4.3" target="_blank">http://tools.ietf.org/html/rfc5870#section-3.4.3</a> which says </div>
<div> "<span style="white-space:pre-wrap"><font face="arial, helvetica, sans-serif">Note: The number of digits of the values in <coordinates> MUST NOT be</font></span><span style="font-family:arial, helvetica, sans-serif;white-space:pre-wrap"> interpreted as an indication to the level of uncertainty." The section following is also interesting, albeit irrelevant for your procedure. It implies that when uncertainty is omitted (and therefore unknown), then "</span>geo:41.53000000,-70.67000000" and "geo:41.53,-70.67" identify the same geo resource.</div>
<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"><<a href="mailto:pete.devries@gmail.com" target="_blank">pete.devries@gmail.com</a>></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 "area" 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 "geo:41.53000000,-70.67000000;u=100"</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>
</blockquote></div><br><br clear="all"><br>-- <br>---------------------------------------------------------------<br>Pete DeVries<br>Department of Entomology<br>University of Wisconsin - Madison<br>445 Russell Laboratories<br>
1630 Linden Drive<br>Madison, WI 53706<br><a href="http://www.taxonconcept.org/" target="_blank">TaxonConcept Knowledge Base</a> / <a href="http://lod.geospecies.org/" target="_blank">GeoSpecies Knowledge Base</a><br><a href="http://about.geospecies.org/" target="_blank">About the GeoSpecies Knowledge Base</a><br>
------------------------------------------------------------<br>
</div>