Changes between Initial Version and Version 1 of Ticket #894


Ignore:
Timestamp:
03/31/11 11:30:32 (14 years ago)
Author:
robe
Comment:

Oops I was incorrect in the second part of my assumptions. I guess it is the expansion of 0 0 that is problematic because if I switch the expand it works. But notice the geography expand output is still wrong in both.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #894 – Description

    initial v1  
    2424
    2525However watch this:
     26-- This returns true in both --
     27{{{
     28
     29SELECT _ST_EXPAND('LINESTRING(1 2, 3 4)'::geography, 1000) && 'POINT(3 3)'::geography);
     30}}}
     31
     32--- This returns true in PostGIS 1.5 and false in PostGIS 2.0 --
    2633
    2734{{{
     35SELECT 'POINT(-20 -10)'::geography && _ST_Expand(ST_GeogFromText('POINT(0 0)'),3000000);
    2836
    29 SELECT _ST_EXPAND(ST_GeogFromText('LINESTRING(1 2, 3 4)'), 1000) && ST_GeogFromText('POINT(3 3)');
    3037}}}
    3138
    32 On 1.5 the above returns true, but on our new 2.0 after Paul's changing the switch to make gserialized live, it now returns false.
     39-- This works in both --
    3340
    34 So PostGIS 2.0 is more or less more or less broken than 1.5. It's just that 1.5 is covering its tracks in ways we usually check.
     41{{{
     42SELECT _ST_Expand('POINT(-20 -10)'::geography,3000000) && ST_GeogFromText('POINT(0 0)');
     43}}}
     44
     45So perhaps its expanding 0 0 that is at fault, but both are still producing erroneous geography output from _ST_Expand which doesn't agree with what is happening.