Hi there,
i just had the same error when trying to output a GeometryCollection in
JSON-outputformat with GeoServer 2.2.5.
I could find and fix the problem in the GeoServer-sourcecode. Maybe you want
to fix it in the main trunk too.
Here is the solution:
It was a just a small problem in writing
Thank you, the nightly build is working for me :-)
Notice: I had to set the "WFS protocol strategy" to "nonstrict" to get it
working.
Regards
Paul
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/possible-regression-in-2-2-4-tp5029429p5036163.html
Sent from the GeoServer
Hey all,
I just had the same error as in the initial post from Raif, when displaying
a layer in GeoServer 2.2.4, which uses the WFS Datastore.
The WFS is a public Service which can be addressed with the following
GetCapabilities-url:
http://www.pegelonline.wsv.de/webservices/gis/aktuell/wfs?ver
Hello,
unfortunately it seems, that nobody can help me.
Could you please tell me how I can compile the OGRDataStore, in order to use
it in GeoServer?
I will try to fix it by myself.
Best regards
Paul
--
View this message in context:
http://osgeo-org.1560.n6.nabble.com/OGR-DataStore-using-G
Thank you all for your answers. Too bad, that you can't use the
pregeneralized features extension with wfs.
I will take a look at the WPS.
Currently as a workaround i have several layers which use different geometry
columns and which are displayed scale dependent using min and maxResolution.
-
Hi there,
currently I'm working on an OpenSource WebGIS, in which a large amount of
line-objects (about 15 000) have to be displayed over the map of Germany.
The data is distributed via GeoServer 2.1.3 WFS and is displayed in an
OpenLayers Client (Version 2.11). The data is stored in a PostGIS-dat
