I'm working on a database that has been generated as an ArcSDE database
on top of PostgreSQL and PostGIS. The database was built from a PostGIS
template and the featureclasses in the database use the PostGIS geometry
type.
On the database end, everything seems to be working fine. Queries like
/SELECT ST_asText(shape) as WKT, geometrytype(shape) as TYPE from
sde.azwellheaders
/... work just fine. The public.geometry_columns table is populated
correctly, including records for the shape fields from all the
featureclasses. I did notice that the public.geometry_columns.type field
just says "GEOMETRY", instead giving a specific geometry type, but I
think that's valid, right?
I tried building layers in Geoserver from a few of these featureclasses.
The UI correctly detects the SRID and can correctly compute the bounds
from the data. However, once the layer is published and I look at the
Layer Preview, click on GML for my new layer, I get the following WFS
response:
<ServiceException>
error:Translator error Translator error Error reading Features
org.geotools.data.DataSourceException: An exception occurred while
parsing WKB data An exception occurred while parsing WKB data Unknown
WKB type 93
</ServiceException>
I'm using Geoserver 2.1.2 and PostgreSQL 8.3.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure
contains a definitive record of customers, application performance,
security threats, fraudulent activity, and more. Splunk takes this
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
