[postgis-users] RE: postgis-users Digest, Vol 62, Issue 12
Gerry James
gerry.james at carteryx.com
Thu Dec 13 15:31:42 PST 2007
I figured out the error of my ways in Topic 21 (. I was trying to use a
single quote (') when I needed to put double quotes into the command string
using chr(34). I replaced all of my single quotes and it works like a
charm.
Cheers
Gerry
<hr>
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
postgis-users-request at postgis.refractions.net
Sent: Thursday, December 13, 2007 12:00 PM
To: postgis-users at postgis.refractions.net
Subject: postgis-users Digest, Vol 62, Issue 12
Send postgis-users mailing list submissions to
postgis-users at postgis.refractions.net
To subscribe or unsubscribe via the World Wide Web, visit
http://postgis.refractions.net/mailman/listinfo/postgis-users
or, via email, send a message with subject or body 'help' to
postgis-users-request at postgis.refractions.net
You can reach the person managing the list at
postgis-users-owner at postgis.refractions.net
When replying, please edit your Subject line so it is more specific
than "Re: Contents of postgis-users digest..."
Today's Topics:
1. RE: drop geometry_columns (Bruce Rindahl)
2. shp2pgsql problem (Willy-Bas Loos)
3. Loading data with ogr2ogr (P?l Kristensen)
4. Problem to update PostGIS to new version (Ralf Klammer)
5. Re: shp2pgsql problem (Willy-Bas Loos)
6. RE: Loading data with ogr2ogr (Obe, Regina)
7. Change projection in select? (Runesson Magnus)
8. Re: Change projection in select? ( Rodrigo Mart?n L?PEZ GREGORIO )
9. RE: Change projection in select? (Obe, Regina)
10. SV: [postgis-users] Change projection in select? (Runesson Magnus)
11. RE: Change projection in select? (Obe, Regina)
12. No Space left on device. (Richard Heimann [C])
13. Re: Loading data with ogr2ogr (Frank Warmerdam)
14. GiST index on Geometry Column (Kyle Wilcox)
15. Re: No Space left on device. (Paul Ramsey)
16. RE: No Space left on device. (Richard Heimann [C])
17. Re: shp2pgsql problem (Tom Glancy)
18. Re: No Space left on device. (Chander Ganesan)
19. Re: GiST index on Geometry Column (Paul Ramsey)
20. Re: GiST index on Geometry Column (Mark Cave-Ayland)
21. ogr2ogr in ASP (Gerry James)
22. Re: GiST index on Geometry Column (Kyle Wilcox)
23. Re: GiST index on Geometry Column (Kyle Wilcox)
----------------------------------------------------------------------
Message: 1
Date: Wed, 12 Dec 2007 13:14:55 -0700
From: "Bruce Rindahl" <rindahl at lrcwe.com>
Subject: RE: [postgis-users] drop geometry_columns
To: "'PostGIS Users Discussion'"
<postgis-users at postgis.refractions.net>
Message-ID: <001701c83cfb$a943f480$df00a8c0 at Bruce>
Content-Type: text/plain; charset="us-ascii"
Try this.
SELECT probe_geometry_columns()
Bruce
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Travis
Kirstine
Sent: Wednesday, December 12, 2007 12:09 PM
To: PostGIS Users Discussion
Subject: [postgis-users] drop geometry_columns
Hi,
I am new to postgis and mistakenly dropped my geometry_columns table.
Is there anyway to recreate the table (so things work again
Geoserver)? or do I have to reload all my datasets (and add the
table).
CREATE TABLE geometry_columns (
f_table_catalog VARRCHAR(256) NOT NULL,
f_table_schema VARCHAR(256) NOT NULL,
f_table_nam VARCHAR(256) NOT NULL,
f_geometry_column VARCHAR(256) NOT NULL,
coord_dimension INTEGER NOT NULL,
srid INTEGER NOT NULL,
type VARCHAR(30) NOT NULL
)
--
Travis K.
Toronto, Canada
------------------------------------------------------------
"She knows there's no success like failure
And that failure's no success at all."
-Bob Dylan-
------------------------------------------------------------
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------
Message: 2
Date: Thu, 13 Dec 2007 11:04:58 +0100
From: "Willy-Bas Loos" <willybas at gmail.com>
Subject: [postgis-users] shp2pgsql problem
To: postgis-users at postgis.refractions.net
Message-ID:
<1dd6057e0712130204n75d482eaj722927537316b045 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Skipped content of type multipart/alternative-------------- next part
--------------
A non-text attachment was scrubbed...
Name: bool1rec.dbf
Type: application/x-dbase
Size: 1554 bytes
Desc: not available
Url :
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/50
5c5cad/bool1rec-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bool1rec.copy
Type: application/octet-stream
Size: 1972 bytes
Desc: not available
Url :
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/50
5c5cad/bool1rec.obj
------------------------------
Message: 3
Date: Thu, 13 Dec 2007 03:16:52 -0800 (PST)
From: P?l Kristensen <pal.kristensen at statkart.no>
Subject: [postgis-users] Loading data with ogr2ogr
To: postgis-users at postgis.refractions.net
Message-ID: <14313629.post at talk.nabble.com>
Content-Type: text/plain; charset=UTF-8
Hi!
I have loaded some data from ArcSDE 9.1 to PostGIS using the ogr2ogr
utility. The load statements typically looks like this:
ogr2ogr -nlt LINESTRING -nln n50_begrensningskurve -lco
GEOMETRY_NAME=the_geom -a_srs EPSG:32633 -f PostgreSQL PG:"dbname=kartdata
user=**** host=***.***.***.***"
SDE:***.***.***.***,5157,,sde_user,sde_password,n50.begrensningskurve
The problem is that the resulting table in PostGIS has a SRID value of 1,
but it should be 32633. I have tried to include the s_srs option to override
the source projection, which by the way is 32633, but that did not do any
difference.
I have used the UpdateGeometrySRID function to change the SRID after
loading, but that seems like a workaround that really not should be
necessary.
Is there something I've missed that causes this behavior? Any ideas?
Regards,
PC%l Kristensen
--
View this message in context:
http://www.nabble.com/Loading-data-with-ogr2ogr-tp14313629p14313629.html
Sent from the PostGIS - User mailing list archive at Nabble.com.
------------------------------
Message: 4
Date: Thu, 13 Dec 2007 12:41:17 +0100
From: "Ralf Klammer" <milkbread at gmx.de>
Subject: [postgis-users] Problem to update PostGIS to new version
To: postgis-users at postgis.refractions.net
Message-ID: <20071213114117.59550 at gmx.net>
Content-Type: text/plain; charset="iso-8859-1"
Hi,
I've got a problem while updating PostGIS to version 1.3.2.
My Postgre version is: 1.6.3
I am able to install PostGIS but the installation always aborts when the
tool wants to install a new spatial database.
The expected mistake is now that the user or the password are not correct,
because the installation-tool is not able to connect to Postgre. But I have
tried every possibility...proofed the password...used a new password...made
sure I spell my password right...nothing helps!
Maybe anybody had the same problem and knows what I'm making wrong?!?
Any hint would help!
Ciao
Ralf
--
Psssst! Schon vom neuen GMX MultiMessenger gehvrt?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
------------------------------
Message: 5
Date: Thu, 13 Dec 2007 13:15:55 +0100
From: "Willy-Bas Loos" <willybas at gmail.com>
Subject: Re: [postgis-users] shp2pgsql problem
To: postgis-users at postgis.refractions.net
Message-ID:
<1dd6057e0712130415re98372eu9252b2621111a165 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Skipped content of type multipart/alternative-------------- next part
--------------
A non-text attachment was scrubbed...
Name: bool1rec.shp
Type: application/octet-stream
Size: 380 bytes
Desc: not available
Url :
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/07
75e7b9/bool1rec-0002.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bool1rec.shx
Type: application/octet-stream
Size: 108 bytes
Desc: not available
Url :
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/07
75e7b9/bool1rec-0002.dll
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bool1rec.sbn
Type: application/octet-stream
Size: 132 bytes
Desc: not available
Url :
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/07
75e7b9/bool1rec-0003.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bool1rec.sbx
Type: application/octet-stream
Size: 116 bytes
Desc: not available
Url :
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/07
75e7b9/bool1rec-0003.dll
------------------------------
Message: 6
Date: Thu, 13 Dec 2007 07:17:59 -0500
From: "Obe, Regina" <robe.dnd at cityofboston.gov>
Subject: RE: [postgis-users] Loading data with ogr2ogr
To: "PostGIS Users Discussion" <postgis-users at postgis.refractions.net>
Message-ID:
<53F9CF533E1AA14EA1F8C5C08ABC08D202EAD2F2 at ZDND.DND.boston.cob>
Content-Type: text/plain; charset="iso-8859-1"
Not sure if it makes a difference, but I usually quote the "EPSG:32633",
but I've never imported from SDE so could be a totally different issue.
Hope that helps,
Regina
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Pel
Kristensen
Sent: Thursday, December 13, 2007 6:17 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Loading data with ogr2ogr
Hi!
I have loaded some data from ArcSDE 9.1 to PostGIS using the ogr2ogr
utility. The load statements typically looks like this:
ogr2ogr -nlt LINESTRING -nln n50_begrensningskurve -lco
GEOMETRY_NAME=the_geom -a_srs EPSG:32633 -f PostgreSQL PG:"dbname=kartdata
user=**** host=***.***.***.***"
SDE:***.***.***.***,5157,,sde_user,sde_password,n50.begrensningskurve
The problem is that the resulting table in PostGIS has a SRID value of 1,
but it should be 32633. I have tried to include the s_srs option to override
the source projection, which by the way is 32633, but that did not do any
difference.
I have used the UpdateGeometrySRID function to change the SRID after
loading, but that seems like a workaround that really not should be
necessary.
Is there something I've missed that causes this behavior? Any ideas?
Regards,
Pel Kristensen
--
View this message in context:
http://www.nabble.com/Loading-data-with-ogr2ogr-tp14313629p14313629.html
Sent from the PostGIS - User mailing list archive at Nabble.com.
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
------------------------------
Message: 7
Date: Thu, 13 Dec 2007 14:22:11 +0100
From: "Runesson Magnus" <Magnus.Runesson at smhi.se>
Subject: [postgis-users] Change projection in select?
To: <postgis-users at postgis.refractions.net>
Message-ID: <F42F7DB5458FA048BE4213ADA6A36D655EDE6E at CORRE.ad.smhi.se>
Content-Type: text/plain; charset="us-ascii"
I have a table where my geometries are saved in SRID 4326. To get my
result in text I do:
SELECT asText(geom) FROM myTable;
Sometimes I want to get my results from the select in 3021 instead. Can
I do that? How do I do that?
Regards,
/Magnus, SMHI
------------------------------
Message: 8
Date: Thu, 13 Dec 2007 13:27:27 +0000
From: " Rodrigo Mart?n L?PEZ GREGORIO " <rodrigomlg at gmail.com>
Subject: Re: [postgis-users] Change projection in select?
To: "PostGIS Users Discussion" <postgis-users at postgis.refractions.net>
Message-ID:
<10cf58b30712130527q1ca88ceo9ab245e807159ce1 at mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"
Hi Magnus
Try this:
*SELECT AsText(Transform(geom,3021)) from myTable;*
Rodrigo.
On Dec 13, 2007 1:22 PM, Runesson Magnus <Magnus.Runesson at smhi.se> wrote:
> I have a table where my geometries are saved in SRID 4326. To get my
> result in text I do:
> SELECT asText(geom) FROM myTable;
>
> Sometimes I want to get my results from the select in 3021 instead. Can
> I do that? How do I do that?
>
> Regards,
> /Magnus, SMHI
>
> _______________________________________________
> 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.refractions.net/pipermail/postgis-users/attachments/20071213/11
3c8ede/attachment-0001.html
------------------------------
Message: 9
Date: Thu, 13 Dec 2007 08:29:00 -0500
From: "Obe, Regina" <robe.dnd at cityofboston.gov>
Subject: RE: [postgis-users] Change projection in select?
To: "PostGIS Users Discussion" <postgis-users at postgis.refractions.net>
Message-ID:
<53F9CF533E1AA14EA1F8C5C08ABC08D202EAD316 at ZDND.DND.boston.cob>
Content-Type: text/plain; charset="us-ascii"
SELECT AsText(ST_Transform(geom, 3021)) FROM mytable
If you are using a pre-1.2 install of PostGIS you may need to use
transform(geom,3021) instead of st_transform(geom,3021)
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
Runesson Magnus
Sent: Thursday, December 13, 2007 8:22 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Change projection in select?
I have a table where my geometries are saved in SRID 4326. To get my
result in text I do:
SELECT asText(geom) FROM myTable;
Sometimes I want to get my results from the select in 3021 instead. Can
I do that? How do I do that?
Regards,
/Magnus, SMHI
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
------------------------------
Message: 10
Date: Thu, 13 Dec 2007 14:45:01 +0100
From: "Runesson Magnus" <Magnus.Runesson at smhi.se>
Subject: SV: [postgis-users] Change projection in select?
To: "PostGIS Users Discussion" <postgis-users at postgis.refractions.net>
Message-ID: <F42F7DB5458FA048BE4213ADA6A36D655EDE75 at CORRE.ad.smhi.se>
Content-Type: text/plain; charset="iso-8859-1"
Thanks!
What is the difference between st_transform and transform?
I notice that both are wotking for me.
Regards,
/Magnus, SMHI
-----Ursprungligt meddelande-----
Fren: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] Fvr Obe, Regina
Skickat: den 13 december 2007 14:29
Till: PostGIS Users Discussion
Dmne: RE: [postgis-users] Change projection in select?
SELECT AsText(ST_Transform(geom, 3021)) FROM mytable
If you are using a pre-1.2 install of PostGIS you may need to use
transform(geom,3021) instead of st_transform(geom,3021)
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
Runesson Magnus
Sent: Thursday, December 13, 2007 8:22 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Change projection in select?
I have a table where my geometries are saved in SRID 4326. To get my
result in text I do:
SELECT asText(geom) FROM myTable;
Sometimes I want to get my results from the select in 3021 instead. Can
I do that? How do I do that?
Regards,
/Magnus, SMHI
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------
Message: 11
Date: Thu, 13 Dec 2007 08:48:39 -0500
From: "Obe, Regina" <robe.dnd at cityofboston.gov>
Subject: RE: [postgis-users] Change projection in select?
To: "PostGIS Users Discussion" <postgis-users at postgis.refractions.net>
Message-ID:
<53F9CF533E1AA14EA1F8C5C08ABC08D202EAD332 at ZDND.DND.boston.cob>
Content-Type: text/plain; charset="iso-8859-1"
Just a name difference currently. St_transform name was put in place to be
more in line with OGC naming. Moving forward there might be a difference as
transform is deprecated and may not be improved on and will eventually be
removed.
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of Runesson
Magnus
Sent: Thursday, December 13, 2007 8:45 AM
To: PostGIS Users Discussion
Subject: SV: [postgis-users] Change projection in select?
Thanks!
What is the difference between st_transform and transform?
I notice that both are wotking for me.
Regards,
/Magnus, SMHI
-----Ursprungligt meddelande-----
Fren: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] Fvr Obe, Regina
Skickat: den 13 december 2007 14:29
Till: PostGIS Users Discussion
Dmne: RE: [postgis-users] Change projection in select?
SELECT AsText(ST_Transform(geom, 3021)) FROM mytable
If you are using a pre-1.2 install of PostGIS you may need to use
transform(geom,3021) instead of st_transform(geom,3021)
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
Runesson Magnus
Sent: Thursday, December 13, 2007 8:22 AM
To: postgis-users at postgis.refractions.net
Subject: [postgis-users] Change projection in select?
I have a table where my geometries are saved in SRID 4326. To get my
result in text I do:
SELECT asText(geom) FROM myTable;
Sometimes I want to get my results from the select in 3021 instead. Can
I do that? How do I do that?
Regards,
/Magnus, SMHI
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
-----------------------------------------
The substance of this message, including any attachments, may be
confidential, legally privileged and/or exempt from disclosure
pursuant to Massachusetts law. It is intended
solely for the addressee. If you received this in error, please
contact the sender and delete the material from any computer.
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------
Message: 12
Date: Thu, 13 Dec 2007 10:37:36 -0500
From: "Richard Heimann [C]" <heimann at ait.nrl.navy.mil>
Subject: [postgis-users] No Space left on device.
To: "'PostGIS Users Discussion'"
<postgis-users at postgis.refractions.net>
Message-ID: <002101c83d9e$1612ff50$3b81fa84 at aitgis>
Content-Type: text/plain; charset="us-ascii"
This question is more to do with PostgreSQL then PostGIS but I've always
gotten good response on this forum and so I'm going back to the well.
After a recent load, I received the following error, ".No space left on
device SQL State 53100 Hint: Check free Disk Space." This error is fairly
self-explanatory but I don't know how to approach the problem. In SQL server
I would simple stop autogrowth on a file group, create a new file group on a
larger partition and be done or alternately attached/detach the database
onto new partition and begin work again. My point is there are several ways
but Im new to PostrgeSQL and Im curious - what's the best practice. I
believe all the data is in the installation directory <data> folder. Can I
simply move this folder and somehow reattach? Thanks in advance, Rich
_____
From: Gregory Williamson [mailto:Gregory.Williamson at digitalglobe.com]
Sent: Tuesday, December 11, 2007 7:48 PM
To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion; Michael
Smedberg; Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
Subject: RE: [postgis-users] HELP adding spatial field to table
I think it is rare that you'd want corrupt data. My usual approach has been
to load my data set into a temporary table (only lasts for the session (or
transaction)) and then apply sanity checks and either delete offending rows
or modify them if you know sane values to set them to.
Then create the geometries from the data set and insert it into my real
table, possibly with something like
INSERT INTO some_real_table SELECT gid,label_name,the_geom FROM foo WHERE
IsValid(the_geom);
HTH,
Greg W.
(sorry for top-posting, challenged reader and pressed for time)
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net on behalf of Richard
Heimann [C]
Sent: Tue 12/11/2007 4:57 PM
To: 'Michael Smedberg'; Richard.Heimann at nrl.navy.mil; 'PostGIS Users
Discussion'
Subject: RE: [postgis-users] HELP adding spatial field to table
Thanks for the prompt response. And youre right there are some such values.
Is there a work around?
Rich
-----Original Message-----
From: Michael Smedberg [mailto:Michael.Smedberg at redfin.com]
Sent: Tuesday, December 11, 2007 6:55 PM
To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
Subject: RE: [postgis-users] HELP adding spatial field to table
Are you sure that x and y always have legit values? If one were null or
the zero-length string, I think you'd get an error like that.
-----Original Message-----
From: postgis-users-bounces at postgis.refractions.net
[mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
Richard Heimann [C]
Sent: Tuesday, December 11, 2007 3:44 PM
To: 'PostGIS Users Discussion'
Subject: [postgis-users] HELP adding spatial field to table
All,
Im getting some strange behavior that I cant explain and sadly know its
likely trivial. My pursuit is simple, add a spatial filed to a table
containing x,y.
First. AddGeometryColumn
SELECT AddGeometryColumn( 'crimetest', 'geom', 4326, 'POINT', 2)
Next (and where the trouble lies)
UPDATE crimetest
SET geom = PointFromText('POINT(' || x || ' ' || y || ')', 4326)
This is the error I receive.
ERROR: Invalid OGC WKT (too short)
SQL state: XX000
Context: SQL function "geomfromtext" statement 1
SQL function "pointfromtext" statement 1
Can anyone shed some light on this?
Thanks
Rich
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
_______________________________________________
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.refractions.net/pipermail/postgis-users/attachments/20071213/54
6a694d/attachment-0001.html
------------------------------
Message: 13
Date: Thu, 13 Dec 2007 10:58:01 -0500
From: Frank Warmerdam <warmerdam at pobox.com>
Subject: Re: [postgis-users] Loading data with ogr2ogr
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Message-ID: <47615689.6010100 at pobox.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
PC%l Kristensen wrote:
> Hi!
>
> I have loaded some data from ArcSDE 9.1 to PostGIS using the ogr2ogr
> utility. The load statements typically looks like this:
>
> ogr2ogr -nlt LINESTRING -nln n50_begrensningskurve -lco
> GEOMETRY_NAME=the_geom -a_srs EPSG:32633 -f PostgreSQL PG:"dbname=kartdata
> user=**** host=***.***.***.***"
> SDE:***.***.***.***,5157,,sde_user,sde_password,n50.begrensningskurve
>
> The problem is that the resulting table in PostGIS has a SRID value of 1,
> but it should be 32633. I have tried to include the s_srs option to
override
> the source projection, which by the way is 32633, but that did not do any
> difference.
>
> I have used the UpdateGeometrySRID function to change the SRID after
> loading, but that seems like a workaround that really not should be
> necessary.
>
> Is there something I've missed that causes this behavior? Any ideas?
PC%l,
Can you confirm that the spatial_ref_sys table is populated? Normally
ogr2ogr attempts to find an exact match for the coordinate system in
spatial_ref_sys (based on comparing the WKT strings) and if one is not
found it should try and create a new spatial_ref_sys entry with the SRID
being one higher than the highest currently used value.
The fact that it selected "1" suggests to me that the table might be
empty.
Note that OGR does not, and will not, make the assumption that SRIDs
map 1:1 to EPSG codes. The trick really is to ensure that the WKT
matches something exactly in the spatial_ref_sys. So for the -s_srs
(or -a_srs) you should use the exact string from the spatial_ref_sys.
This can be stored in a file.
I'd like to have a layer creation option to select a particular SRID
by SRID number for the PG driver, but that hasn't been implemented yet.
Should my assumptions about the spatial_ref_sys table be wrong, please
consider filing a bug against GDAL/OGR promptly. We have only a few
days before the 1.5.0 release to fix any serious problems in the
postgis driver.
Best regards,
--
---------------------------------------+------------------------------------
--
I set the clouds in motion - turn up | Frank Warmerdam,
warmerdam at pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush | President OSGeo, http://osgeo.org
------------------------------
Message: 14
Date: Thu, 13 Dec 2007 11:14:50 -0500
From: Kyle Wilcox <Kyle.Wilcox at noaa.gov>
Subject: [postgis-users] GiST index on Geometry Column
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Message-ID: <47615A7A.7010000 at Noaa.gov>
Content-Type: text/plain; charset=UTF-8
I am having trouble creating a GiST index on a MULTIPOLYGON column.
When the table is empty, the indexes will be created without errors, but
inserts will fail with the error. When the table has entries in it, the
creation of the index will fail with the same error. The index creation
only fails on the poly_geom column and works in both conditions for the
point_geom column.
ERROR: function 60821C60 returned NULL
PostgreSQL: 8.2.4 on Windows
The table is set up as follows:
CREATE TABLE model.grid
(
gid serial primary key,
mid integer,
landmask boolean
);
SELECT AddGeometryColumn('model','grid','point_geom',4326,'POINT',2);
SELECT AddGeometryColumn('model','grid','poly_geom',4326,'MULTIPOLYGON',2);
ALTER TABLE model.grid ADD CONSTRAINT "Upoint" UNIQUE(mid, point_geom);
ALTER TABLE model.grid ADD CONSTRAINT "Upoly" UNIQUE(mid, poly_geom);
CREATE INDEX point_gist ON model.grid USING gist (point_geom);
CREATE INDEX poly_gist ON model.grid USING gist (poly_geom);
Any ideas?
--
Kyle Wilcox
NOAA Chesapeake Bay Office
410 Severn Avenue
Suite 107A
Annapolis, MD 21403
office: (410) 295-3151
Kyle.Wilcox at noaa.gov
"It is from the wellspring of our despair and the places
that we are broken that we come to repair the world."
- Murray Waas
------------------------------
Message: 15
Date: Thu, 13 Dec 2007 08:23:28 -0800
From: Paul Ramsey <pramsey at refractions.net>
Subject: Re: [postgis-users] No Space left on device.
To: Richard.Heimann at nrl.navy.mil, PostGIS Users Discussion
<postgis-users at postgis.refractions.net>
Message-ID: <23B2BB03-581C-49E8-87D0-0A19F9FCB639 at refractions.net>
Content-Type: text/plain; charset=WINDOWS-1252; delsp=yes;
format=flowed
Richard,
Move the "data" directory to a new device, and then in
postgresql.conf, alter the location of the default data space to that
location.
P
On 13-Dec-07, at 7:37 AM, Richard Heimann [C] wrote:
> This question is more to do with PostgreSQL then PostGIS but Ive
> always gotten good response on this forum and so Im going back to
> the well.
>
>
> After a recent load, I received the following error, No space
> left on device SQL State 53100 Hint: Check free Disk Space. This
> error is fairly self-explanatory but I dont know how to approach
> the problem. In SQL server I would simple stop autogrowth on a file
> group, create a new file group on a larger partition and be done or
> alternately attached/detach the database onto new partition and
> begin work again. My point is there are several ways but Im new to
> PostrgeSQL and Im curious - whats the best practice. I believe all
> the data is in the installation directory <data> folder. Can I
> simply move this folder and somehow reattach? Thanks in advance, Rich
>
>
>
>
> From: Gregory Williamson [mailto:Gregory.Williamson at digitalglobe.com]
> Sent: Tuesday, December 11, 2007 7:48 PM
> To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion; Michael
> Smedberg; Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
> Subject: RE: [postgis-users] HELP adding spatial field to table
>
>
> I think it is rare that you'd want corrupt data. My usual approach
> has been to load my data set into a temporary table (only lasts for
> the session (or transaction)) and then apply sanity checks and
> either delete offending rows or modify them if you know sane values
> to set them to.
>
> Then create the geometries from the data set and insert it into my
> real table, possibly with something like
> INSERT INTO some_real_table SELECT gid,label_name,the_geom FROM
> foo WHERE IsValid(the_geom);
>
> HTH,
>
> Greg W.
> (sorry for top-posting, challenged reader and pressed for time)
>
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net on behalf of
> Richard Heimann [C]
> Sent: Tue 12/11/2007 4:57 PM
> To: 'Michael Smedberg'; Richard.Heimann at nrl.navy.mil; 'PostGIS
> Users Discussion'
> Subject: RE: [postgis-users] HELP adding spatial field to table
>
> Thanks for the prompt response. And youre right there are some such
> values.
> Is there a work around?
>
> Rich
>
>
> -----Original Message-----
> From: Michael Smedberg [mailto:Michael.Smedberg at redfin.com]
> Sent: Tuesday, December 11, 2007 6:55 PM
> To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
> Subject: RE: [postgis-users] HELP adding spatial field to table
>
> Are you sure that x and y always have legit values? If one were
> null or
> the zero-length string, I think you'd get an error like that.
>
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net
> [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
> Richard Heimann [C]
> Sent: Tuesday, December 11, 2007 3:44 PM
> To: 'PostGIS Users Discussion'
> Subject: [postgis-users] HELP adding spatial field to table
>
> All,
>
> Im getting some strange behavior that I cant explain and sadly know
> its
> likely trivial. My pursuit is simple, add a spatial filed to a table
> containing x,y.
>
> First. AddGeometryColumn
>
> SELECT AddGeometryColumn( 'crimetest', 'geom', 4326,
> 'POINT', 2)
>
> Next (and where the trouble lies)
>
> UPDATE crimetest
> SET geom = PointFromText('POINT(' || x || ' ' || y || ')',
> 4326)
>
> This is the error I receive.
>
> ERROR: Invalid OGC WKT (too short)
> SQL state: XX000
> Context: SQL function "geomfromtext" statement 1
> SQL function "pointfromtext" statement 1
>
> Can anyone shed some light on this?
>
>
> Thanks
> Rich
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------
Message: 16
Date: Thu, 13 Dec 2007 11:31:13 -0500
From: "Richard Heimann [C]" <heimann at ait.nrl.navy.mil>
Subject: RE: [postgis-users] No Space left on device.
To: "'Paul Ramsey'" <pramsey at refractions.net>,
<Richard.Heimann at nrl.navy.mil>, "'PostGIS Users Discussion'"
<postgis-users at postgis.refractions.net>
Message-ID: <002c01c83da5$93da8910$3b81fa84 at aitgis>
Content-Type: text/plain; charset="us-ascii"
Too easy!! Thanks again Paul.
-----Original Message-----
From: Paul Ramsey [mailto:pramsey at refractions.net]
Sent: Thursday, December 13, 2007 11:23 AM
To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
Subject: Re: [postgis-users] No Space left on device.
Richard,
Move the "data" directory to a new device, and then in
postgresql.conf, alter the location of the default data space to that
location.
P
On 13-Dec-07, at 7:37 AM, Richard Heimann [C] wrote:
> This question is more to do with PostgreSQL then PostGIS but I've
> always gotten good response on this forum and so I'm going back to
> the well.
>
>
> After a recent load, I received the following error, ".No space
> left on device SQL State 53100 Hint: Check free Disk Space." This
> error is fairly self-explanatory but I don't know how to approach
> the problem. In SQL server I would simple stop autogrowth on a file
> group, create a new file group on a larger partition and be done or
> alternately attached/detach the database onto new partition and
> begin work again. My point is there are several ways but Im new to
> PostrgeSQL and Im curious - what's the best practice. I believe all
> the data is in the installation directory <data> folder. Can I
> simply move this folder and somehow reattach? Thanks in advance, Rich
>
>
>
>
> From: Gregory Williamson [mailto:Gregory.Williamson at digitalglobe.com]
> Sent: Tuesday, December 11, 2007 7:48 PM
> To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion; Michael
> Smedberg; Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
> Subject: RE: [postgis-users] HELP adding spatial field to table
>
>
> I think it is rare that you'd want corrupt data. My usual approach
> has been to load my data set into a temporary table (only lasts for
> the session (or transaction)) and then apply sanity checks and
> either delete offending rows or modify them if you know sane values
> to set them to.
>
> Then create the geometries from the data set and insert it into my
> real table, possibly with something like
> INSERT INTO some_real_table SELECT gid,label_name,the_geom FROM
> foo WHERE IsValid(the_geom);
>
> HTH,
>
> Greg W.
> (sorry for top-posting, challenged reader and pressed for time)
>
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net on behalf of
> Richard Heimann [C]
> Sent: Tue 12/11/2007 4:57 PM
> To: 'Michael Smedberg'; Richard.Heimann at nrl.navy.mil; 'PostGIS
> Users Discussion'
> Subject: RE: [postgis-users] HELP adding spatial field to table
>
> Thanks for the prompt response. And youre right there are some such
> values.
> Is there a work around?
>
> Rich
>
>
> -----Original Message-----
> From: Michael Smedberg [mailto:Michael.Smedberg at redfin.com]
> Sent: Tuesday, December 11, 2007 6:55 PM
> To: Richard.Heimann at nrl.navy.mil; PostGIS Users Discussion
> Subject: RE: [postgis-users] HELP adding spatial field to table
>
> Are you sure that x and y always have legit values? If one were
> null or
> the zero-length string, I think you'd get an error like that.
>
> -----Original Message-----
> From: postgis-users-bounces at postgis.refractions.net
> [mailto:postgis-users-bounces at postgis.refractions.net] On Behalf Of
> Richard Heimann [C]
> Sent: Tuesday, December 11, 2007 3:44 PM
> To: 'PostGIS Users Discussion'
> Subject: [postgis-users] HELP adding spatial field to table
>
> All,
>
> Im getting some strange behavior that I cant explain and sadly know
> its
> likely trivial. My pursuit is simple, add a spatial filed to a table
> containing x,y.
>
> First. AddGeometryColumn
>
> SELECT AddGeometryColumn( 'crimetest', 'geom', 4326,
> 'POINT', 2)
>
> Next (and where the trouble lies)
>
> UPDATE crimetest
> SET geom = PointFromText('POINT(' || x || ' ' || y || ')',
> 4326)
>
> This is the error I receive.
>
> ERROR: Invalid OGC WKT (too short)
> SQL state: XX000
> Context: SQL function "geomfromtext" statement 1
> SQL function "pointfromtext" statement 1
>
> Can anyone shed some light on this?
>
>
> Thanks
> Rich
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
>
>
>
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
>
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------
Message: 17
Date: Thu, 13 Dec 2007 11:17:30 -0600
From: "Tom Glancy" <Tom.Glancy at dnr.state.mn.us>
Subject: Re: [postgis-users] shp2pgsql problem
To: <postgis-users at postgis.refractions.net>
Message-ID: <476114C9.A3F3.00E2.0 at dnr.state.mn.us>
Content-Type: text/plain; charset="us-ascii"
Your dbf file contains spaces (0x20) in the "microrelie" boolean and
"macrorelie" boolean fields. The representation of NULL in boolean fields is
a question mark (0x3f). Allowable characters in a boolean field are
Y,y,N,n,T,t,F,f,?
It looks like your dbf is broken.
Regards,
Tom
>>> "Willy-Bas Loos" <willybas at gmail.com> 12/13/2007 6:15 AM >>>
here's the rest of the shapefile (still one record, attached).
On Dec 13, 2007 11:04 AM, Willy-Bas Loos <willybas at gmail.com> wrote:
Hi,
I have a small problem wit shp2pgsql, it doesn't convert my colleague's
shapefile correctly.
I've attached the 1rec shapefile and the shp2pgsql result in this mail, hope
that works.
I'm using this version: RCSID: $Id: shp2pgsql.c,v 1.88.2.7 2005/08/29
22:36:14 strk Exp $
on windows XP.
The problem is in two of the boolean fields: "microrelie" boolean and
"macrorelie" boolean.
They are both created, but their values don't make it into the INSERT
statement. They turn up as empty strings, which is illegal SQL.
There are lots (37) of fields in the shapefile.
12 other boolean fields are handled correctly.
The "bad" fields are the 24th and the 25th field.
is this some bug?
WBL
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/d5
c248b8/attachment-0001.html
------------------------------
Message: 18
Date: Thu, 13 Dec 2007 12:28:43 -0500
From: Chander Ganesan <chander at otg-nc.com>
Subject: Re: [postgis-users] No Space left on device.
To: Richard.Heimann at nrl.navy.mil, PostGIS Users Discussion
<postgis-users at postgis.refractions.net>
Message-ID: <47616BCB.7060804 at otg-nc.com>
Content-Type: text/plain; charset="iso-8859-1"
Richard Heimann [C] wrote:
>
> This question is more to do with PostgreSQL then PostGIS but I've
> always gotten good response on this forum and so I'm going back to the
> well.
>
>
>
> After a recent load, I received the following error, "...No space left
> on device SQL State 53100 Hint: Check free Disk Space." This error is
> fairly self-explanatory but I don't know how to approach the problem.
> In SQL server I would simple stop autogrowth on a file group, create a
> new file group on a larger partition and be done or alternately
> attached/detach the database onto new partition and begin work again.
> My point is there are several ways but Im new to PostrgeSQL and Im
> curious - what's the best practice. I believe all the data is in the
> installation directory <data> folder. Can I simply move this folder
> and somehow reattach? Thanks in advance, Rich
>
You have two "good" options to correct this problem:
- Use Paul's suggestion (what you mention above) to move your entire
database to a different drive/partition. This solution is good until
that partition runs out of space, then you have to move it again ;-) I
would recommend not changing your postgresql.conf file to reflect the
new directory - rather - modify your startup scripts so pg_ctl is called
with the appropriate directory argument...
- Use PostgreSQL's Tablespace mechanism to spread your data across
multiple partitions. This is generally the preferred method, since it
allows you to leverage multiple drives/partitions for the storage of
data. The URL below describes how to do this:
http://www.postgresql.org/docs/8.2/static/manage-ag-tablespaces.html
Tablespaces were introduced in PostgreSQL 8.0. If you are using an
older version of PostgreSQL then you'd have to resort to some different
techniques to achieve a similar result.
--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC 27560
919-463-0999/877-258-8987
http://www.otg-nc.com
Expert PostgreSQL Training
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.refractions.net/pipermail/postgis-users/attachments/20071213/c4
d55f03/attachment-0001.html
------------------------------
Message: 19
Date: Thu, 13 Dec 2007 08:23:40 -0800
From: Paul Ramsey <pramsey at refractions.net>
Subject: Re: [postgis-users] GiST index on Geometry Column
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Message-ID: <F5708334-CC64-44CB-BBFB-A272A4E4F35D at refractions.net>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Try without the constraints... just a guess, but it might be the
combination of the index and the unique constraint on geometry.
On 13-Dec-07, at 8:14 AM, Kyle Wilcox wrote:
> I am having trouble creating a GiST index on a MULTIPOLYGON column.
> When the table is empty, the indexes will be created without
> errors, but
> inserts will fail with the error. When the table has entries in
> it, the
> creation of the index will fail with the same error. The index
> creation
> only fails on the poly_geom column and works in both conditions for
> the
> point_geom column.
>
> ERROR: function 60821C60 returned NULL
>
> PostgreSQL: 8.2.4 on Windows
>
> The table is set up as follows:
>
> CREATE TABLE model.grid
> (
> gid serial primary key,
> mid integer,
> landmask boolean
> );
>
> SELECT AddGeometryColumn('model','grid','point_geom',4326,'POINT',2);
> SELECT AddGeometryColumn('model','grid','poly_geom',
> 4326,'MULTIPOLYGON',2);
> ALTER TABLE model.grid ADD CONSTRAINT "Upoint" UNIQUE(mid,
> point_geom);
> ALTER TABLE model.grid ADD CONSTRAINT "Upoly" UNIQUE(mid, poly_geom);
> CREATE INDEX point_gist ON model.grid USING gist (point_geom);
> CREATE INDEX poly_gist ON model.grid USING gist (poly_geom);
>
> Any ideas?
>
> --
>
> Kyle Wilcox
> NOAA Chesapeake Bay Office
> 410 Severn Avenue
> Suite 107A
> Annapolis, MD 21403
> office: (410) 295-3151
> Kyle.Wilcox at noaa.gov
>
> "It is from the wellspring of our despair and the places
> that we are broken that we come to repair the world."
> - Murray Waas
> _______________________________________________
> postgis-users mailing list
> postgis-users at postgis.refractions.net
> http://postgis.refractions.net/mailman/listinfo/postgis-users
------------------------------
Message: 20
Date: Thu, 13 Dec 2007 18:26:48 +0000
From: Mark Cave-Ayland <mark.cave-ayland at ilande.co.uk>
Subject: Re: [postgis-users] GiST index on Geometry Column
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Message-ID: <1197570408.5294.3.camel at mca-desktop>
Content-Type: text/plain
On Thu, 2007-12-13 at 11:14 -0500, Kyle Wilcox wrote:
> I am having trouble creating a GiST index on a MULTIPOLYGON column.
> When the table is empty, the indexes will be created without errors, but
> inserts will fail with the error. When the table has entries in it, the
> creation of the index will fail with the same error. The index creation
> only fails on the poly_geom column and works in both conditions for the
> point_geom column.
>
> ERROR: function 60821C60 returned NULL
>
> PostgreSQL: 8.2.4 on Windows
Hi Kyle,
Could this be the indexing bug which caused the release of PostGIS
1.1.7? What does "SELECT postgis_full_version();" and "select * from
pg_proc where proname = 'transform';" return?
Also, have you attempted to upgrade PostGIS from 1.1.6 to 1.1.7 in the
past?
Kind regards,
Mark.
--
ILande - Open Source Consultancy
http://www.ilande.co.uk
------------------------------
Message: 21
Date: Thu, 13 Dec 2007 10:55:20 -0800
From: Gerry James <gerry.james at carteryx.com>
Subject: [postgis-users] ogr2ogr in ASP
To: postgis-users at postgis.refractions.net
Message-ID: <00a601c83db9$b5c156d0$6701a8c0 at roca.local>
Content-Type: text/plain; charset=us-ascii
I am trying to create an ASP page that will convert MapInfo TAB files to PG
on the fly. I have run into a number of problems doing this. I appear to
have overcome the permissions problems I was having, however, I still can't
get the translation to work. I am trying to accomplish all this by envoking
the WScript.Shell object and running ogr2ogr through the FWTools version.
Now I get no errors that I can use to debug the problem. My code revolves
around the following:
set wshell = CreateObject("WScript.Shell")
Set sexec = wshell.exec("C:\Program Files\FWTools2.0.0\setfw.bat")
lne = "ogr2ogr -f 'PostgreSQL' -a_srs 'EPSG:26909' PG:'host=localhost
user=postgres dbname=Foremore password=********' 'c:\tmp\All_Outcrop.TAB'
-nln test_all_outcrop"
Set sexec = wshell.exec(lne)
When I execute the ASP page I get no error and the PostGIS table I am hoping
for is not created. The syntax shown for the variable lne above works just
fine from the FWTools Shell app. Does anyone have any ideas on how I can
make this work?
Thanks
Gerry
------------------------------
Message: 22
Date: Thu, 13 Dec 2007 13:59:33 -0500
From: Kyle Wilcox <Kyle.Wilcox at noaa.gov>
Subject: Re: [postgis-users] GiST index on Geometry Column
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Message-ID: <47618115.5060501 at Noaa.gov>
Content-Type: text/plain; charset=UTF-8
I am indeed running PostGIS 1.1.6.
# select postgis_full_version();
postgis_full_version
----------------------------------------------------------------------------
------
POSTGIS="1.1.6" GEOS="2.2.3-CAPI-1.1.1" PROJ="Rel. 4.5.0, 22 Oct 2006"
USE_STATS
(1 row)
# select * from pg_proc where proname='transform'
proname | pronamespace | proowner | prolang | proisagg | prosecdef |
proisstrict | proretset | provolatile | pronargs | prorettype |
proargtypes | proallargtypes | proargmodes | proargnames | prosrc |
probin | proacl
-----------+--------------+----------+---------+----------+-----------+-----
--------+-----------+-------------+----------+------------+-------------+---
-------------+-------------+-------------+-----------+----------------------
-+--------
transform | 2200 | 10 | 13 | f | f |
t | f | i | 2 | 16426 | 16426
23 | | | | transform |
$libdir/liblwgeom.dll |
(1 row)
I have not attempted to upgrade in the past but I may now take the step
to get rid of the packaged PostGIS that came with Postgres and start
using the Installers from refractions website.
Mark Cave-Ayland wrote:
> On Thu, 2007-12-13 at 11:14 -0500, Kyle Wilcox wrote:
>> I am having trouble creating a GiST index on a MULTIPOLYGON column.
>> When the table is empty, the indexes will be created without errors, but
>> inserts will fail with the error. When the table has entries in it, the
>> creation of the index will fail with the same error. The index creation
>> only fails on the poly_geom column and works in both conditions for the
>> point_geom column.
>>
>> ERROR: function 60821C60 returned NULL
>>
>> PostgreSQL: 8.2.4 on Windows
>
>
> Hi Kyle,
>
> Could this be the indexing bug which caused the release of PostGIS
> 1.1.7? What does "SELECT postgis_full_version();" and "select * from
> pg_proc where proname = 'transform';" return?
>
> Also, have you attempted to upgrade PostGIS from 1.1.6 to 1.1.7 in the
> past?
>
>
> Kind regards,
>
> Mark.
>
--
Kyle Wilcox
NOAA Chesapeake Bay Office
410 Severn Avenue
Suite 107A
Annapolis, MD 21403
office: (410) 295-3151
Kyle.Wilcox at noaa.gov
"It is from the wellspring of our despair and the places
that we are broken that we come to repair the world."
- Murray Waas
------------------------------
Message: 23
Date: Thu, 13 Dec 2007 14:20:16 -0500
From: Kyle Wilcox <Kyle.Wilcox at noaa.gov>
Subject: Re: [postgis-users] GiST index on Geometry Column
To: PostGIS Users Discussion <postgis-users at postgis.refractions.net>
Message-ID: <476185F0.9070502 at Noaa.gov>
Content-Type: text/plain; charset=UTF-8
Updating the PostGIS 1.3.2 solved the problem, thanks Mark.
Upgrading was surprisingly easy.
Kyle Wilcox wrote:
> I am indeed running PostGIS 1.1.6.
>
> # select postgis_full_version();
>
> postgis_full_version
>
----------------------------------------------------------------------------
------
> POSTGIS="1.1.6" GEOS="2.2.3-CAPI-1.1.1" PROJ="Rel. 4.5.0, 22 Oct 2006"
> USE_STATS
> (1 row)
>
>
>
> # select * from pg_proc where proname='transform'
>
> proname | pronamespace | proowner | prolang | proisagg | prosecdef |
> proisstrict | proretset | provolatile | pronargs | prorettype |
> proargtypes | proallargtypes | proargmodes | proargnames | prosrc |
> probin | proacl
>
-----------+--------------+----------+---------+----------+-----------+-----
--------+-----------+-------------+----------+------------+-------------+---
-------------+-------------+-------------+-----------+----------------------
-+--------
> transform | 2200 | 10 | 13 | f | f |
> t | f | i | 2 | 16426 | 16426
> 23 | | | | transform |
> $libdir/liblwgeom.dll |
> (1 row)
>
>
> I have not attempted to upgrade in the past but I may now take the step
> to get rid of the packaged PostGIS that came with Postgres and start
> using the Installers from refractions website.
>
> Mark Cave-Ayland wrote:
>> On Thu, 2007-12-13 at 11:14 -0500, Kyle Wilcox wrote:
>>> I am having trouble creating a GiST index on a MULTIPOLYGON column.
>>> When the table is empty, the indexes will be created without errors, but
>>> inserts will fail with the error. When the table has entries in it, the
>>> creation of the index will fail with the same error. The index creation
>>> only fails on the poly_geom column and works in both conditions for the
>>> point_geom column.
>>>
>>> ERROR: function 60821C60 returned NULL
>>>
>>> PostgreSQL: 8.2.4 on Windows
>>
>> Hi Kyle,
>>
>> Could this be the indexing bug which caused the release of PostGIS
>> 1.1.7? What does "SELECT postgis_full_version();" and "select * from
>> pg_proc where proname = 'transform';" return?
>>
>> Also, have you attempted to upgrade PostGIS from 1.1.6 to 1.1.7 in the
>> past?
>>
>>
>> Kind regards,
>>
>> Mark.
>>
>
--
Kyle Wilcox
NOAA Chesapeake Bay Office
410 Severn Avenue
Suite 107A
Annapolis, MD 21403
office: (410) 295-3151
Kyle.Wilcox at noaa.gov
"It is from the wellspring of our despair and the places
that we are broken that we come to repair the world."
- Murray Waas
------------------------------
_______________________________________________
postgis-users mailing list
postgis-users at postgis.refractions.net
http://postgis.refractions.net/mailman/listinfo/postgis-users
End of postgis-users Digest, Vol 62, Issue 12
*********************************************
More information about the postgis-users
mailing list