[postgis-users] ERROR: Operation on twoGEOMETRIES withdifferentSRIDs

[Mark Cave-Ayland]

Hi Ezequias,

 

You should be able to find this information in the PostgreSQL documentation
for ALTER TABLE at
http://www.postgresql.org/docs/8.1/interactive/sql-altertable.html.

 

 

Kind regards,

 

Mark.

------------------------
WebBased Ltd
17 Research Way
Plymouth
PL6 8BT

T: +44 (0)1752 797131
F: +44 (0)1752 791023

http://www.webbased.co.uk  
http://www.infomapper.com
http://www.swtc.co.uk 

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.

  _____  

From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Ezequias
Rodrigues da Rocha
Sent: 14 July 2006 14:51
To: PostGIS Users Discussion
Subject: Re: [postgis-users] ERROR: Operation on twoGEOMETRIES
withdifferentSRIDs

 

Something like this ?

update mul.lotes set geometry = setsrid(geometry, 29185); 

where geometry is the geometry field of my geographic table. ;-) 

It works for me but I do not know how to recreate the constraint I must
delete.

Can anyone help me :

CONSTRAINT enforce_srid_geometry CHECK (srid(geometry) = 29185)

Regards.
Ezequias

Mark Cave-Ayland escreveu: 

-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net [mailto:postgis-users-
bounces at postgis.refractions.net] On Behalf Of Johan V
Sent: 14 July 2006 12:46
To: postgis-users at postgis.refractions.net
Subject: Re: [postgis-users] ERROR: Operation on two GEOMETRIES
withdifferentSRIDs
 
Hi Mark and others,
 
Yes the geometry created on the fly is -1, but this same sql statement
(with the on the fly created geometry) does work on another table with
SRID=103300, but not on this one.
 
I need this specific sql statement because it is a statement that is
issued by a software product that makes a WFS/WMS service (GIS Service
over the internet) of this table.
 
So do I have to change or check some thing in the table to be able to
use this kind of sql statement:
 
SELECT the_geom FROM table_x WHERE ((the_geom && 'POLYGON((...))')).
 
Greetz,
Johan.
    

 
 
Hi Johan,
 
Hmmm that makes it a bit more tricky. Unfortunately the SQL being issued is
relying on the implicit cast in PostgreSQL rather than using
GeomFromText()/setSRID() as documented and so its behaviour may change
across PostgreSQL/PostGIS versions - if you do get a chance to update the
SQL in your client software, I would highly recommend it.
 
As for the symptoms you are seeing, I am slightly baffled - can you post the
output of \d <table> for one of your tables that works and your new one that
doesn't, the exact SELECT queries being executed on each table, and can you
confirm that both tables are in the same database running the same version
of PostGIS?
 
 
Kind regards,
 
Mark.
 
------------------------
WebBased Ltd
17 Research Way
Plymouth
PL6 8BT
 
T: +44 (0)1752 797131
F: +44 (0)1752 791023
 
http://www.webbased.co.uk   
http://www.infomapper.com
http://www.swtc.co.uk  
 
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.
 
 
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
 
  





-- 
Ezequias Rodrigues da Rocha
http://ezequiasrocha.blogspot.com
msn:ezequias at hotmail.com
"the worst of democracies is still better than the best of dictatorship"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20060714/a0e361da/attachment.html>