[GRASS-dev] Re: [GRASS GIS] #957: v.voronoi has extra lines in output

[GRASS GIS]

#957: v.voronoi has extra lines in output
-----------------------+----------------------------------------------------
 Reporter:  helena     |       Owner:  grass-dev@…              
     Type:  defect     |      Status:  new                      
 Priority:  major      |   Milestone:  6.4.2                    
Component:  Vector     |     Version:  svn-develbranch6         
 Keywords:  v.voronoi  |    Platform:  All                      
      Cpu:  All        |  
-----------------------+----------------------------------------------------

Comment(by hamish):

 > Replying to [comment:11 hamish]:
 > > I'm not sure where the %.14g is coming from, as
 > > lib/gis/wind_format.c writes using %.15g.

 Replying to [comment:14 mmetz]:
 > Not for real projections, at least not for nc_spm_08 with
 > projection: 99 (Lambert Conformal Conic) because full %.15g
 > precision is only used when projection == -1, otherwise %.8f is
 > used. See
 >
 https://trac.osgeo.org/grass/browser/grass/trunk/lib/gis/wind_format.c#L33

 ah, right.. so it's %.8f not %.14g. FWIW I added that -1 for "full"
 precision* in r37725 as some modules were lying to G_format_*() about not
 being lat/lon (when they really were) to get decimal output instead of
 D:M:S, with rather unfortunate results.

 [*] (%.15g doesn't quite show full IEEE double, but the max without
 partial-noise bits)

 assuming that projected coords are either in feet or meters, I'm happy
 enough with 10 nanometer precision. GPS and projection math will take a
 very long time to catch up with that. Even %.15g won't match what's in the
 vector's bbox, and again I wonder out loud if this is worth worrying
 about, or if it should just be declared a feature in the v.voronoi help
 page.

 see also #123.


 Hamish

-- 
Ticket URL: <http://trac.osgeo.org/grass/ticket/957#comment:15>
GRASS GIS <http://grass.osgeo.org>