[postgis-devel] GBOXF
    Sandro Santilli 
    strk at keybit.net
       
    Mon Nov 28 10:02:27 PST 2011
    
    
  
On Mon, Nov 28, 2011 at 09:53:33AM -0800, Paul Ramsey wrote:
> OK, so it sounds like the way forward is to basically keep what we
> have now, which is a double GBOX, but with care taken that we populate
> it it with float-rounded versions of the bounds, so that
> demand-generated boxes match cached boxes. This will need to be
> documented, but if we move to doing bbox access via an accessor
> instead of directly referencing the object the number of pain points
> should go down hopefully.
> 
> I will move forward with new bbox work on the above basis, and abandon
> the doublebox experiment.
Sounds good to me. 
Of course a new type will still pose the "float or double" question.
As well as it was posed (they tell me) by ST_Extent.
--strk;
  ()   Free GIS & Flash consultant/developer
  /\   http://strk.keybit.net/services.html
    
    
More information about the postgis-devel
mailing list