[prev in list] [next in list] [prev in thread] [next in thread] 

List:       grass-user
Subject:    Re: [GRASS-user] Forward and backward RMS error.
From:       Markus Metz <markus.metz.giswork () gmail ! com>
Date:       2013-02-27 16:26:54
Message-ID: CAG+h=FFkk0rfZVbFvJA2M0b-HSKj7sBstmEoSFKLzce33L9ShA () mail ! gmail ! com
[Download RAW message or body]

On Wed, Feb 27, 2013 at 3:57 PM, Aldo Clerici <aldo.clerici@unipr.it> wrote:
> Dear GRASS users and developers,
>
>
>
> where can I find an explanation about the meaning of forward and backward
>
> RMS errors in i.points? In the 6.4.3 and 6.5 manuals for i.points a unique
> value for RMS error is reported, but the two values are actually computed.
>
> In 7.0 manual the two values are mentioned but no description of their
> meaning is reported.
>
> How can the two values be used to evaluate accuracy in georectification?
> Which is used to rectify the map?

i.points, i.rectify, etc. calculate transformation equations from
ground control points (GCPs). RMS (root mean square) errors are then
determined by transforming each GCP and calculating the root mean
square from the deviations of the transformed coordinates from the GCP
coordinates. Since you can transform coordinates from source to target
(forward) and from target to source (backward), you can also calculate
two RMS errors. The forward RMS error is probably of more interest and
ideally smaller than the target resolution (sub-pixel transformation
accuracy).

HTH,

Markus M

>
>
>
> Many thanks in advance.
>
>
>
>
>
> Aldo Clerici
>
>
>
> Earth Sciences Dep.
>
>
>
> Parma University
>
>
>
>
> _______________________________________________
> grass-user mailing list
> grass-user@lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/grass-user
>
_______________________________________________
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic