[Taxacom] Inappropriate accuracy of locality data
taxacom3 at achapman.org
Tue Nov 30 15:49:57 CST 2010
Good to see this issue raised again
A lot of the points your raise, Bob are covered in the booklet by John
Wieczorek and myself that was done as part of the BioGeomancer project.
The reference is below.
Chapman, A.D.and Wieczorek, J. (eds). (2006). /Guide to Best Practices
for Georeferencing/. BioGeomancer Consortium. Copenhagen: Global
Biodiversity Information Facility. 90pp. ISBN: 87-92020-00-3.
It is available on line, and we would appreciate any feedback as we are
discussing the possibility of doing a new version. We wish to cover
uncertainty in more depth, especially the possibility of using
foot-printed uncertainty rather than just the point-radius method most
are using now. This would use polygons and include things like
buffering, roads, etc. if you know it was collected along the river, or
the road, it doesn't make much sense to then make the uncertainty a
large circle for which parts are no where near the river/road etc.
Another example, may be where a collection is made along the coast with
500 meter uncertainty, but the point-radius method will give you a big
circle, part of which is out to sea. Clipping to a buffer of the coast
line (depending on scale of the coast line) will give a much more
realistic picture of the uncertainty.
For Google Earth, I tend to use a conservative uncertainty of about 100
meters (sometimes greater), although I know that in most cases it is a
good bit better than that; depending on the area, and the accuracy for
which you can determine the location - not easy where there are no roads!
Arthur D. Chapman*
On 1/12/2010 4:00 AM, taxacom-request at mailman.nhm.ku.edu wrote:
> Message: 3
> Date: Tue, 30 Nov 2010 07:06:06 +1100
> From: Bob Mesibov<mesibov at southcom.com.au>
> Subject: Re: [Taxacom] Inappropriate accuracy of locality data
> To: TAXACOM<taxacom at mailman.nhm.ku.edu>
> Message-ID:<20101130070606.09bb0c0c.mesibov at southcom.com.au>
> Content-Type: text/plain; charset=US-ASCII
> Many thanks for the on- and off-list comments.
> A separate issue to the one I posted about is the best way to record or report the spatial uncertainty around a locality. No matter how you write a lat/long, it's still a point - a mathematical point with no horizontal spread at all.
> In real life there's a spread. Some of it derives from the uncertainty of the GPS reading, but often there's another element: perhaps you collected 3 specimens over ca 0.25 ha, or your bottom-grabber was some distance from your boat, or you couldn't get a reading in the forest so you walked to a nearby road, got a GPS reading there and estimated an offset.
> Best practice is to record a locality plus an uncertainty. In museum databases I have seen this as a field named 'Accuracy', 'Precision', 'Reliability' or 'Uncertainty'. Darwin Core calls it UncertaintyInMetres and defines it as:
> "The horizontal distance (in meters) from the given decimalLatitude and decimalLongitude describing the smallest circle containing the whole of the Location. Leave the value empty if the uncertainty is unknown, cannot be estimated, or is not applicable (because there are no coordinates). Zero is not a valid value for this term."
> with this comment:
> "Example: "30" (reasonable lower limit of a GPS reading under good conditions if the actual precision was not recorded at the time), "71" (uncertainty for a UTM coordinate having 100 meter precision and a known spatial reference system)."
> I have been recording uncertainty in my own collecting-events databases for many years, but I was only brave enough to start publishing them as part of locality data in 2009. No reviewer or editor has complained so far...
> You might be using Google Earth, as I do, for estimating locations where your GPS couldn't get a good position reading. Please be aware that Google Earth imagery is not always spot-on, and can be offset by ca 20 m or more from the correct location. A workaround is to get a GPS reading from a nearby landmark which can be clearly seen in the satellite image, to 'calibrate' your Google Earth estimate of the sampling site location.
> -- Dr Robert Mesibov Honorary Research Associate Queen Victoria Museum
> and Art Gallery, and School of Zoology, University of Tasmania Home
> contact: PO Box 101, Penguin, Tasmania, Australia 7316 Ph: (03)
> 64371195; 61 3 64371195 Webpage:
More information about the Taxacom