[postgis-users] Incorrect results from queries specifying an SRID

[Mark Cave-Ayland]

Hi Corey,

Hmmm..... I can't see why this one doesn't work. All I can think of is
that the BOX3D cast causes the SRID not be set or set incorrectly. I'll
try and have a look at this in the near future, however I'm not sure
exactly when I'll be able to get around to it.


Cheers,

Mark.

---

Mark Cave-Ayland
Webbased Ltd.
Tamar Science Park
Derriford
Plymouth
PL6 8BX
England

Tel: +44 (0)1752 764445
Fax: +44 (0)1752 764446


This email and any attachments are confidential to the intended
recipient and may also be privileged. If you are not the intended
recipient please delete it from your system and notify the sender. You
should not copy it or use it for any purpose nor disclose or distribute
its contents to any other person.

> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net 
> [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of cp
> Sent: 01 June 2004 16:51
> To: Mark Cave-Ayland
> Cc: 'strk'; 'PostGIS Users Discussion'
> Subject: Re: [postgis-users] Incorrect results from queries 
> specifying an SRID
> 
> 
> [Oops...meant to send this to the list as well]
> 
> Mark,
> 
> I just tried what you suggested but I'm getting the same 
> result:  0 rows returned with no error reported.  Is there 
> another fix that needs to be applied to raise the error condition?
> 
> Incidentally although select postgis_version(); reports 0.8 
> I've verified that what I have installed is 0.8.1 (is this a 
> bug in the
> postgis_version() funtion?)
> 
> Thanks for your help,
> Corey
> 
> Mark Cave-Ayland wrote:
> 
> >Hi strk,
> >
> >Yup you're right :) I didn't notice that we didn't use the old files 
> >any more - I guess they're there while people test the new 
> postgis.sql 
> >build process?
> >
> >So in theory this should be solved in the 0.8.2 release. cp, can you 
> >test this for us by doing the following in psql, and seeing 
> whether the 
> >SRID mismatch is caught? Note this is done in a transaction as it 
> >affects the system catalogs and so we can roll it back if it doesn't 
> >work.
> >
> >
> >BEGIN;
> >
> >UPDATE pg_amop SET amopreqcheck = 't' WHERE 
> amopclaid=(SELECT oid FROM 
> >pg_opclass WHERE opcname = 'gist_geometry_ops');
> >
> >(this should update only 8 entries)
> >
> >SELECT * FROM gis
> >WHERE geometry && GeometryFromText('BOX3D(325356 6341280,335614
> >6328019)'::box3d, 26712);
> >
> >
> >If this throws an error on SRID mismatch then you can COMMIT the 
> >transaction to make the behaviour permanent. Otherwise type 
> ABORT and 
> >the change will be rolled back. Please report back to as to whether 
> >this solved the problem for you.
> >
> >
> >Many thanks,
> >
> >Mark.
> >  
> >
> [...]
> 
> _______________________________________________
> postgis-users mailing list postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>