The American Surveyor

Surveyors Report: More on Relative Positional Accuracy

A 81Kb PDF of this article as it appeared in the magazine—complete with images—is available by clicking HERE

There continues to be a great deal of misunderstanding and confusion over the definition and application of Relative Positional Accuracy in the ALTA/ACSM standards.

The following question was recently posed: "Can the standard error ellipse obtained from a least squares adjustment be used to estimate the Relative Positional Accuracy for points located as part of an ALTA/ACSM Land Title Survey? In other words, if the ellipses are smaller than 0.07 ft + 50 ppm does the survey meet the standard?"

According to the standards, "Relative Positional Accuracy may be tested by… the results of a minimally constrained, correctly weighted least square adjustment of the survey."

Assuming a least squares adjustment takes into account the primary sources of random, accidental error ­ which, for an angle measured with a total station, are instrument centering, target centering, pointing and reading (DIN), and which, for an EDM distance are instrument centering, target centering and reading ­ the adjustment will (hopefully) be "corrected weighted," and will result in logical error ellipses for each point on the survey.

The definition of Relative Positional Accuracy (RPA) given in the ALTA/ ACS M standards, however, is "…the value expressed in feet or meters that represents the uncertainty due to random errors in measurements in the location of any point on a survey relative to any other point on the same survey at the 95 percent confidence level."

So, it is not the error ellipse of an individual point, but rather the relative error ellipse between any two specified points that defines RPA (keeping in mind, this is at two standard deviations, not one). This means, among other things, that there is not a single Relative Positional Accuracy for the overall survey, but rather an RPA (and a respective "allowable" RPA) for every two-point combination on the survey.

Of course, on a large survey, it would be time-consuming and unnecessary to check every single combination of points, so looking for the potential worst cases would be a logical approach. In a simple survey, that might be the two most distant points on the survey, although depending on if, where, and how redundant measurements were made, those points might not result in the worst case. Those points separated by some combination of the most observations with the lowest confidence in those observations will probably result in the highest RPAs.

Recently, we have been asked how to make RPA meaningful to the layperson: "0.07 feet plus 50 ppm" does not communicate anything comprehensible to most people. Perhaps determining the worst case RPA (e.g., as suggested

"…it is not the error ellipse of an individual point, but rather the relative error ellipse between any two specified points that defines RPA…" above) in feet, assuring that it does not exceed the allowable 0.07 feet plus 50 ppm, and then stating that the Relative Positional Accuracy does not exceed that amount on the survey (with 95% confidence) is one way it could be expressed (understanding that the result will be the worst case, and that in most cases, the RPA will likely be significantly less than the worst case).

Expressing RPA in such a way is not a requirement of the ALTA/ACSM standards; the standards merely require that it be addressed in the certificate. But it is a requirement in some states, and some surveyors are being asked by attorneys and title people for a simplified explanation of what 0.07 feet and 50 ppm means on a given survey.

Gary Kent is Director, Integrated Services at The Schneider Corporation in Indianapolis. He is past-president of ACSM and chairs the ALTA/ACSM Committee for NSPS and the Liaison Committee for ALTA. He is on the Indiana Board of Registration and lectures both locally and nationally.

A 81Kb PDF of this article as it appeared in the magazine—complete with images—is available by clicking HERE

Exit mobile version