G'Day all,

Sorry, rank noob queries here: just trying to get a default install of 
GeoServer (2.5) connected to a default install of PostgreSQL (9.1/Debian 
wheezy) (with PostGIS extensions).

So the fist challenge is just getting the workspace set up effectively. 
PostGIS is running on our remote server, and port 5432 is locked down to 
local connections only. I am not a command line warrior, so my 
(PostgreSQL Admin capacity) = (whatever I can do in phpPGAdmin).

I have phpPGAdmin set up, connected to the remote server, and have an 
empty default database as well as one I created to test.

Ok, with PostgreSQL waiting for action, I turn now to GeoServer. In the 
Data Stores there is no existing PostGIS-connected store.

So we start with the docs at: 
http://docs.geoserver.org/stable/en/user/data/database/postgis.html

Right away I'm in trouble: the docs say to "navigate to Stores ‣ Add a 
new store ‣ PostGIS NG" This is not an option. We only have options for 
PostGIS and PostGIS JNDI The screenshot in the docs shows a form element 
"dbtype" and it's filled in with postgisng. We don't have the option to 
specify dbtype.

(1) Why doesn't our install match the docos and/or is it important?

Further down the form we need to specify a user and password to connect 
with PostGIS.

(2) What's best practice? Should I use the PostgreSQL superuser account 
(doesn't seem right) or should I create a new user with limited 
privileges to run each database?

Our workflow typically involves researchers sending us shapefiles or 
tabular data. We want to serve this from a PostGIS data store. But how 
to get our hodgepodge of contributed data into the remote PostGIS 
efficiently? It appears that we need to first set up a local PostGIS 
instance and use combination of utilities to import tables. With the 
data now sitting in a local db, we can export to a psql file. This can 
be manually ftp'ed up to the webserver. Then we need to use a command 
line tool to ingest that data file to PostGIS, and finally we can come 
back through GeoServer and declare a new store, set up layers, etc.

(3) Have I got that right? It seems like a very long pipeline with a lot 
of admin overhead. For data that changes regularly, I wonder how updates 
could be streamlined?

Sorry again for some of the broad, context-setting questions: these are 
often the hardest things to locate documentation for and a few wise 
words from more experienced hands would be much appreciated.

Kind regards,

JB

-- 
John Brisbin
Managing Director, BoaB interactive Pty Ltd
POB 248, MT Molloy QLD 4871

E: [email protected]
M: 0407 471 565 | P: 07 4094 2172
Skype: boabjohn | Twitter: @boabjohn


------------------------------------------------------------------------------
"Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
Instantly run your Selenium tests across 300+ browser/OS combos.
Get unparalleled scalability from the best Selenium testing platform available
Simple to use. Nothing to install. Get started now for free."
http://p.sf.net/sfu/SauceLabs
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to