[postgis-devel] Hitting boxes (lack of) again

[Paul Ramsey]

If not, make one, a wiki page preferably, so the final state of requirements is coherent and not randomly spread through comments.

P.

On 2012-09-14, at 1:21 AM, Sandro Santilli <strk at keybit.net> wrote:

> Also, I'd want ST_Width and ST_Height functions for boxes,
> or more general ST_Range(box, dimension) if we plan to support
> multidimensional boxes.
> 
> Did we have a wiki page or ticket to take note of this ?
> 
> --strk;
> 
> On Tue, Sep 11, 2012 at 01:19:50PM +0200, Sandro Santilli wrote:
>> It just happened again: I need a box...
>> 
>> It is to compute the extent of a query _outside_
>> of the database (since the db already performs a first scan
>> so why performing a second one ?), so for each geometry in
>> the result I want to get its bounding box, which I'll parse
>> and expand as necessary.
>> 
>> Now: what's the recommended way to do that ?
>> ST_Envelope will give me a POLYGON, which is harder to parse
>> than a nice BOX.
>> ST_Extent is an aggregate, don't want that, want a _single_
>> value.
>> 
>> What should I do, then ? ::box2d ? ::box3d ? ::box3d_extent ?
>> 
>> It would be very nice to have a single view on the concept.
>> 
>> --strk; 
> 
>> http://www.cartodb.com - Map, analyze and build applications with your data
>> 
>>                                       ~~ http://strk.keybit.net 
> _______________________________________________
> postgis-devel mailing list
> postgis-devel at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-devel