Search Results

WFS is meant to transfer raw data with full geometries and attributes, which a client software (not a human) can then either visualize on its own (try for example QGis as a WFS client), analyze and eventually … edit, saving back the changes via the WFS Transaction call. …

WFS does not have an option to generalize data, there is however a "vec:Simplify" WPS process that can do the job on the fly (at least in the currently supported versions, 2.9.x and above, I cannot remember …

If you have fixed hardware, create a semi-randomized stress test and increase the number of clients until the server either starts mis-behaving or the throughput does not go up any longer. This docume …

I'm afraid this is a very well known bug for which we have no solution at the moment: https://osgeo-org.atlassian.net/browse/GEOS-4773

The WFS protocol is the "previous arrangement", it leaves no space for outputs to have a CRS other than the one requested, and the client doing the request should be aware of it. …

GeoServer is trying to read the shapefile, and finds that the header of the shapefile is not following the specification, but looks like something else. Hyphotesis: The file in question is not reall …

You can do both by writing your own data store: http://docs.geotools.org/latest/userguide/tutorial/datastore/index.html Once it's ready, drop its jar and eventual dependencies inside GeoServer own W …

In GeoServer 2.2.0 you should be able to configure the WFS in a different way for different workspaces, give it a try …

A WFS 2.0 compliant service is only required to support a very small subset of the XPath language, from the Filter 2.0 specification: "This International Standard does not require that a filter expression …

Something like this (might need minor corrections) should work: FeatureTypeInfo info = catalog.getFeatureTypeByName(getLayerId(MockData.BASIC_POLYGONS)); SimpleFeatureSource fs = (SimpleFeatureSource …

You can use the security subsystem to disallow writes on a specific set of layers: http://geoserver.geo-solutions.it/edu/en/security/layer_level.html http://docs.geoserver.org/stable/en/user/security …

user30184 is correct, you should be using CQL_FILTER, some examples here: http://docs.geoserver.org/stable/en/user/tutorials/cql/cql_tutorial.html

It is best to add at the end of the BBOX the SRS of it, as it might not be the same as your data (and WFS defaults to use the SRS of the data if you don't say otherwise). …

Compare this, failing in the same way: http://demo.geo-solutions.it/geoserver/wfs with a valid request returning GeoJSON: http://demo.geo-solutions.it/geoserver/wfs? … service=WFS&version=1.0.0&request=GetFeature&typeName=tiger:giant_polygon&outputFormat=JSON …

WFS has no way to just provide the bounding box of a feature. However, you can install the WPS protocol, it has a process you can use to just extract the bounding box. …