[GRASS-dev] i.points, i.vpoints now use G_parser()

[Michael Barton]

For total RMS, do I simply combine forward and backward (i.e., like I have
twice as many points)? Or is it better to display separate forward and
backward RMS values? Same with displaying 'g' for individual points--just
display forward or display the average of forward and backward?

Michael
__________________________________________
Michael Barton, Professor of Anthropology
School of Human Evolution & Social Change
Center for Social Dynamics & Complexity
Arizona State University

phone: 480-965-6213
fax: 480-965-7671
www: http://www.public.asu.edu/~cmbarton



> From: Glynn Clements <glynn at gclements.plus.com>
> Date: Mon, 26 Jun 2006 12:19:03 +0100
> To: Hamish <hamish_nospam at yahoo.com>
> Cc: <michael.barton at asu.edu>, <grass-dev at grass.itc.it>
> Subject: Re: [GRASS-dev] i.points, i.vpoints now use G_parser()
> 
> 
> Hamish wrote:
> 
>>>> What information does it return and in what format?
>>> 
>>> Number of active points: %d
>>> Forward:
>>> x[%d] = %.2f
>>> y[%d] = %.2f
>>> g[%d] = %.2f
>>> RMS = %.2f
>> 
>> 
>> %.2f isn't very useful if you are registering a scan of a lat/lon map
>> (eg nautical chart). This has always been a pain in i.[v]points, you
>> only judge to include/exclude a point based on what lines are colored
>> red.
>> 
>> maybe a check?
>>   if(G_projection() == PROJECTION_LL)
>>      %.5f
>> 
>> or G_trim_decimal() ??
> 
> Seems reasonable enough.
> 
> What would be an appropriate precision for the reverse error (i.e.
> distances in X-Y coordinates)?
> 
> -- 
> Glynn Clements <glynn at gclements.plus.com>