[postgis-users] Coordinates and SRID - bound overflow, ST_Equals

[Doug_Newcomb at fws.gov]

Balint
Would using the geography data type be more suitable to what you are 
trying to accomplish?

http://postgis.refractions.net/docs/ch04.html#PostGIS_GeographyVSGeometry
Doug Newcomb 
USFWS
Raleigh, NC
919-856-4520 ext. 14 doug_newcomb at fws.gov
---------------------------------------------------------------------------------------------------------
The opinions I express are my own and are not representative of the 
official policy of the U.S.Fish and Wildlife Service or Dept. of the 
Interior.   Life is too short for undocumented, proprietary data formats.



Balint Persics <persicsb at gmail.com> 
Sent by: postgis-users-bounces at postgis.refractions.net
01/20/2011 06:30 AM
Please respond to
PostGIS Users Discussion <postgis-users at postgis.refractions.net>


To
postgis-users at postgis.refractions.net
cc

Subject
[postgis-users] Coordinates and SRID - bound overflow, ST_Equals






Hi,

I have a very interesting problem, but I think some of you may have a
solution for that.

When I try to model Russia with EPSG:4326 coordinates, I "run out of
the bounds", e.g.  Russia's extent is so wide, it overlaps the
-180/+180 coordinate range of EPSG:4326, so the most
eastern part is in the western Hemisphere. When inserting points to
the geometry column, PostGIS allows me to insert both (186,45) and
(-174,45) (the former is out of the bounds of the reference, the
latter is okay). When I query the database whether these two points
are equal with ST_Equals, I get a false result , but in reality, they
are the same. I think there should be a version of ST_Equals which
compares the geometries taking into account their SRID.

Thanks,
Balint

-- 
Persics Balint
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/postgis-users/attachments/20110120/c6c64469/attachment.html>