On Thu, May 12, 2011 at 10:35, Sandro Santilli wrote:
> On Thu, May 12, 2011 at 10:24:28AM +0200, Magnus Hagander wrote:
>
>> Like I said - we want the underlying fix, but I do beleive we want the
>> fix in PostGIS *as well*.
>
> We surely want the fix in ST_Translate, or whatever _produced_ the i
On 12/05/11 09:35, Sandro Santilli wrote:
Like I said - we want the underlying fix, but I do beleive we want the
fix in PostGIS *as well*.
We surely want the fix in ST_Translate, or whatever _produced_ the inf
coordinate.
Not sure we want to refuse to accept inf coordinates though,
as long as
On Thu, May 12, 2011 at 10:24:28AM +0200, Magnus Hagander wrote:
> Like I said - we want the underlying fix, but I do beleive we want the
> fix in PostGIS *as well*.
We surely want the fix in ST_Translate, or whatever _produced_ the inf
coordinate.
Not sure we want to refuse to accept inf coordi
On Thu, May 12, 2011 at 10:20, Sandro Santilli wrote:
> On Thu, May 12, 2011 at 09:53:38AM +0200, Magnus Hagander wrote:
>> On Tue, Mar 8, 2011 at 10:16, Magnus Hagander wrote:
>> > On Mon, Feb 28, 2011 at 16:35, Mark Cave-Ayland
>> > wrote:
>> >> On 28/02/11 15:18, Magnus Hagander wrote:
>
>> >
On Thu, May 12, 2011 at 09:53:38AM +0200, Magnus Hagander wrote:
> On Tue, Mar 8, 2011 at 10:16, Magnus Hagander wrote:
> > On Mon, Feb 28, 2011 at 16:35, Mark Cave-Ayland
> > wrote:
> >> On 28/02/11 15:18, Magnus Hagander wrote:
> >>> Running the following query locks up postgis completely (in
