Brent Fraser wrote:
Is your PLSS data lines (yikes!) or areas (hopefully)? And the
shapefiles have the same attributes (or can be made that way prior to
loading into PostGIS)? Are the mining claims represented by points or
areas? If they are areas, I guess you could use the centroid in th
samclemmens wrote:
I dropped the db and recreated it...and this time it worked. I get the
following, which, I'm assuming, means I'm good to go...?
testdb1=# SELECT postgis_full_version();
postgis_full_version
I dropped the db and recreated it...and this time it worked. I get the
following, which, I'm assuming, means I'm good to go...?
testdb1=# SELECT postgis_full_version();
postgis_full_version
-
samclemmens wrote:
I ran make install after make check, and received the output below. There
was no confirmation that it installed properly or not. I tried creating
another spatial database using the same commands, but to no avail. ---Same
issue.
The "make install" output looks good. Are yo
Hi Bill,
I have not done much like you describe, but am working with Postgis tables with
around 155,000,000 polygons in them, & have got very reasonable performance out
of it.
General comments, some probably obvious, but here anyway...
I'm running a quad core AMD 965 with 16Gb memory & my db
Bill,
Is your PLSS data lines (yikes!) or areas (hopefully)? And the shapefiles
have the same attributes (or can be made that way prior to loading into
PostGIS)? Are the mining claims represented by points or areas? If they are
areas, I guess you could use the centroid in the query.
I ran make install after make check, and received the output below. There
was no confirmation that it installed properly or not. I tried creating
another spatial database using the same commands, but to no avail. ---Same
issue.
[r...@ip-10-224-82-127 postgis-1.5.0SVN]# make install
make -C lib
samclemmens wrote:
Unfortunately, I get the following:
postgres=# SELECT postgis_full_version();
ERROR: function postgis_full_version() does not exist
LINE 1: SELECT postgis_full_version();
^
HINT: No function matches the given name and argument types. You might need
to add exp
Unfortunately, I get the following:
postgres=# SELECT postgis_full_version();
ERROR: function postgis_full_version() does not exist
LINE 1: SELECT postgis_full_version();
^
HINT: No function matches the given name and argument types. You might need
to add explicit type casts.
samclemmens wrote:
Sorry; I inadvertently posted my previous response twice... The line is:
psql:postgis/postgis.sql:80: ERROR: type "spheroid" already exists
So, does this mean that my spatial database was successfully created the
first time around despite the "notices" that the spatial fu
I've got a database of Public Land Survey System (PLSS) data for most
of the contiguous United States, and I need to make it accessible to
spatial queries using PostgreSQL and PostGIS. My basic question is how
to physically configure it so that queries over any area are as
efficient as possib
Sorry; I inadvertently posted my previous response twice... The line is:
psql:postgis/postgis.sql:80: ERROR: type "spheroid" already exists
So, does this mean that my spatial database was successfully created the
first time around despite the "notices" that the spatial functions (e.g.,
st_max
Here’s what I get immediately after trying to create a spatial database:
[r...@ip-10-224-82-127 postgis-1.5.0SVN]# sudo -u postgres createdb testdb
[r...@ip-10-224-82-127 postgis-1.5.0SVN]# sudo -u postgres createlang
plpgsql testdb
[r...@ip-10-224-82-127 postgis-1.5.0SVN]# sudo -u postgres psql
13 matches
Mail list logo
