[Geoserver-users] N00bish troubles standing up first install...Featuretype problem from PostGIS Datasource

Ok, I'm new to GeoSerer, PostGIS and OpenLayers. I do have some
experiece with the Oracle stack. I'm not sure if I'm hitting a bug
or not doing something in the right order, but I've been butting my head
against this for a week now.

I'm running GeoServer 1.7.2 deployed from the war file on GlassFish on
XP. This is not a local build, I haven't gotten the source as yet. The packaged demos appear to work ok after following the quickstart guide.

I have a shapefile of our local data loaded into PostGIS, in its own
schema and seems to be working ok.

I defined a namespace and a DataSource for the postGIS DB. The DataSource uses the same PostgreSQL user and password that was used to load the local spatial data.

Using the console application, when attempting to define a new feature type, I cannot see my postGIS DataSource.

I decided to poke it with a stick by creating a FeatureType directory and info.xml file. I can see that FeatureType on the drop down list but it doesn't load. The interesting bits from the log are below.

I suspect I've missed something in the info.xml (attached) since it was taken from a shapefile FeatureType.

So, two questions for now:
1. what are the next steps to be able to see the DataSource on the new FeatureType drop down?

2. What am I missing from the info.xml, or does someone have one with all possible attributes commented? I didn't see anything in the documentation explaining how DataSources and FeatureTypes hang together.

All info appreciated.
-Ted

LOG Snippet:
Ignoring feature type: 'SUAs', error occured loading schema: Feature type could not be found for SUAs

2009-02-27 15:41:47,968 INFO [geoserver.catalog] -
org.geotools.data.SchemaNotFoundException: Feature type could not be found for SUAs
  at org.geotools.data.jdbc.fidmapper.DefaultFIDMapperFactory.getPkColumnInfo(DefaultFIDMapperFactory.java:296)

  at org.geotools.data.jdbc.fidmapper.DefaultFIDMapperFactory.getMapper(DefaultFIDMapperFactory.java:114)

  at org.geotools.data.postgis.PostgisDataStore.buildFIDMapper(PostgisDataStore.java:1017)

  at org.geotools.data.jdbc.FeatureTypeHandler.getFIDMapper(FeatureTypeHandler.java:229)

  at org.geotools.data.jdbc.FeatureTypeHandler.getFeatureTypeInfo(FeatureTypeHandler.java:197)

  at org.geotools.data.jdbc.FeatureTypeHandler.getSchema(FeatureTypeHandler.java:166)

  at org.geotools.data.jdbc.JDBC1DataStore.getSchema(JDBC1DataStore.java:336)

  at org.geotools.data.postgis.PostgisDataStore.getSchema(PostgisDataStore.java:1934)

info.xml (965 Bytes)

Ted Scott ha scritto:

Ok, I'm new to GeoSerer, PostGIS and OpenLayers. I do have some
experiece with the Oracle stack. I'm not sure if I'm hitting a bug
or not doing something in the right order, but I've been butting my head
against this for a week now.

I'm running GeoServer 1.7.2 deployed from the war file on GlassFish on
XP. This is not a local build, I haven't gotten the source as yet. The packaged demos appear to work ok after following the quickstart guide.

I have a shapefile of our local data loaded into PostGIS, in its own
schema and seems to be working ok.

I defined a namespace and a DataSource for the postGIS DB. The DataSource uses the same PostgreSQL user and password that was used to load the local spatial data.

Using the console application, when attempting to define a new feature type, I cannot see my postGIS DataSource.

If you cannot configure it by the UI, there's little chance it'll
work with a hand made setup.
The most likely cause of this issue is that GeoServer cannot access
the data due to security limitations. The PostGIS metadata tables,
such as geometry_columns and the like, should be always placed in
the "public" schema and be accessible, at least read only, but
the user you're connecting with.

Cheers
Andrea

--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.