Hot answers tagged pgadmin3
If you have a Windows computer, you can use good 'ol CMD.EXE with a few esoteric for-loops. Make sure you do this in a "contained" directory with only the shp/sql files that you need to load. First step, create the SQL loader files (I also assumed you have Lat/Long WGS84 data with 4326 .. update this to your SRS): for %f in (*shp) do shp2pgsql -s 4326 %f ...
If want to stick to a GUI then the newer version of pgAdmin has Shapefile Loader that can be used as a bulk load Experimental; but working well http://www.postgis.org/download/windows/experimental.php
If you want a painless install, you might want to start over and use the OpenGeo Suite version of PostGIS. $sudo wget -qO- http://apt.opengeo.org/gpg.key | apt-key add - $sudo echo "deb http://apt.opengeo.org/ubuntu lucid main" >> /etc/apt/sources.list $sudo apt-get update $apt-cache search opengeo $sudo apt-get install opengeo-postgis Or you could ...
I guess you are a victim of the fact that spatially enabling a PostgreSQL db with PostGIS creates a bunch of functions in the "public" namespace. If you backup the public namespace and then restore it to a PostGIS db these functions will already exist, causing errors. As Paul Ramsey wrote (in a blog post explaining the issue in detail and giving advice): ...
While I have not actually installed it, I had read about the pgAdmin plugin called "PostGIS viewer" referenced here (2010), here (2011), and here (2012). The first request to add something like this (that I found) was ticket #485. The 2012 SQL console for the pgAdmin plugin: PostGIS viewer by German Carrillo uses the QGIS plugin "Fast SQL Layer", and ...
I don't believe the Shapefile loader will work in your case. However, PostGIS comes with a raster loading tool called raster2pgsql. This tool will load any GDAL supported raster format into PostGIS Raster. It is a command-line tool so to execute it you just need to run: raster2pgsql raster_options schema.table_name > output.sql So, the tool will take ...
Yes, absolutely. PostgreSQL is set up to only accept local connections, and GeoServer is set up to use the loopback address i.e. 127.0.0.1 on port 8080. So you can run the standard installers and everything should just work when you type: http://localhost:8080 You'll need to set up GeoServer to see your PostgreSQL database, but that's standard stuff ...
PgAdmin has limits on the largest object it can display in a table cells. Large geometries frequently exceed this limit, which results in an "empty" cell, confusing to new users. If you call ST_NPoint(geom) or ST_GeometryType(geom) you can see that the geometry is in fact there, and does have data in it, you just cannot see it in a PgAdmin cell.
Any table in the instance can be registered with sde. But sde is what has to do that registration. I suggest starting with this Essential Reading for Geodatabases Registering with the database
The easiest would be to setup PostgreSQL user group roles and assign permissions based on those roles. It's a lot easier in PostgreSQL 9.0+ since you can use DEFAULT PRIVILEGES. --this will take care of future tables in a database ALTER DEFAULT PRIVILEGES GRANT ALL ON TABLES TO gisadmins; -- this will take care of existing tables in public schema. As I ...
It looks like the loader you're using is from 1.5 or lower, while the database you're loading to is 2.0. Either (a) move to the latest loader or (b) add the "legacy.sql" file into your postgis database to ensure that all the old function signatures the old loader expects are available to you.
The problem is with "NAME_3" = NULL, since NULL is not "equal to" NULL. This should instead use the proper SQL construct "NAME_3" IS NULL. See the documentation for more details.
Only top voted, non community-wiki answers of a minimum length are eligible