[postgis-users] Unique Constraint on Spatial Point violated
Sairam Krishnamurthy
kmsram420 at gmail.com
Fri Apr 22 12:10:43 PDT 2011
All,
I am loading a table from a file. The file is really big and has
millions of rows. Table structure is described below:
lat : double precision (primary key)
lon: double precision (primary key)
spatialPoint: geometry (unique)
The file has lines of lat and lon: (lat,lon)
Since I am loading from a file I cannot load the spatialPoint
directly. I have a trigger to call the following function BEFORE
INSERT OR UPDATE:
BEGIN
NEW."spatialPoint" := ST_SetSRID(ST_MakePoint(NEW.lon, NEW.lat), 4326);
RETURN new;
END
When I load the table I get unique key constraint on the filed
spatialPoint. This happens when I try to load the point
"-3.751046|-51.359041". But when I grep for the point in the file only
one row exists.
I am not sure if this is a precision problem in calculting the spatial
points from the lat.lon value.
Can someone help me with this?
Thanks,
Sairam Krishnamurthy
+1 612 859 8161
More information about the postgis-users
mailing list