RE: [Geoserver-devel] big problem upgrading to geoserver beta3 from beta1 release

Dave,

First, thanks for responding!

I had set the SRIDs in the FeatureTypes and I also tried turning off WKB (set to 'false'). I've tested with a GeoServer beta3 on Windows and another one on Linux, with both versions pointing to the same PostGIS datasource, Postgres version 8.0, PostGIS version 1.0.0rc5. My Java version is 1.4.2_07 on Windows, and 1.4.2_03 on Linux. The PostGIS database is running on the Linux box. By the way, I imported the shape data into PostGIS using the shp2pqsql utility. (We have a guy here who uses ESRI ArcView to generate the shape data.)

With the beta1 release, everything is working great. Somehow I have not been able to get either the beta2 or now the beta3 release to work. If I capture the SQL query being used by GeoServer (beta3) and run it using Postgres psql, it works fine. So I think GeoServer is getting the data, then somehow it is 'losing' the geometry data. The log clearly shows that it's finding all the attributes from PostGIS. I've attached a GeoServer logfile in case you find that helpful.

One other item - I replaced the Postgres JDBC jar files with the ones for Postgres 8.0 and PostGIS 1.0.0. But since this has been working fine for the beta1 release, I don't think it's the source of the problem.

Again, thanks for your help. If I can find a way to get GeoServer working again, that would be great. I really like the product and want to keep using for our project.

Regards,
Bob Cook

-----Original Message-----
From: dblasby@anonymised.com [mailto:dblasby@anonymised.com]
Subject: [Geoserver-devel] big problem upgrading to geoserver beta3 from beta1 release

which version of Postgis and java are you using?

I've been using Postgis and geoserver WMS and WFS quite a bit and I've
had no problems.

Have you set the SRIDs for you layer in the FeatureType editor?

What happens if you turn WKB off - "false" (ie. in the DataStore
editor)?

dave

(attachments)

logfile (107 KB)

Greetings, Robert.

I had set the SRIDs in the FeatureTypes and I also tried turning
off WKB (set to 'false'). I've tested with a GeoServer beta3 on
Windows and another one on Linux, with both versions pointing to the
same PostGIS datasource, Postgres version 8.0, PostGIS version
1.0.0rc5.

As far as I know, the storage format for geometry objects is changed
in postgis 1.0.0. Geometries are now stored in "hexadecimal canonical
representation", i.e. there is a bunch of hex digits in geometry
columns instead of text. I also tried postgis 1.0.0 with GeoServer and
got the same results as you :slight_smile: But as I did this mostly out of
curiosity, I didn't dug into the matter and just rolled back to 0.9.1.
I thought that might be the case that GeoTools doesn't understand
that hexadecimal geometry format, but after you mentioned that all
worked well for GeoServer beta1 I'm no longer sure that this
assumption is correct.

As a quick solution you can temporarily switch to PostGIS 0.9.1 till
the problem is resolved if you don't have any special requirements
for 1.0.0. The former is working with GeoServer 1.3 beta3 (or should
I say, with corresponding GeoTools? :slight_smile:

BTW, looking at your logs I noticed lines with following content:

[SEVERE] org.geotools.renderer.lite.LiteRenderer2$DefaultRenderListener
- expected java.lang.Integer , but got java.lang.String

  I believe that is a consequence of a recent (now-fixed) bug in GeoTools.
I suggest you to get current gt-main.jar from svn, there is the link:
http://svn.refractions.net/geoserver/trunk/geoserver/lib/gt2-main.jar
With this jar's version from beta3 you'll probably run into troubles with
PostGIS datastore even with PostGIS 0.9.1.

--
WBR,
Artie