Re: [Geoserver-users] Extension for GML format missing?

It is a java library, you can read the section on xml here: - http://docs.geotools.org/latest/userguide/library/xml/geometry.html If I was doing it I would make an improvement to the geoserver importer parse GML (and create a database table from the result). Looking at the code it appears it is

Re: [Geoserver-users] Compute from SRS bounds/Compute from native bounds/Reload Band definitions using REST api

Here is some docs here: http://docs.geoserver.org/stable/en/user/rest/api/featuretypes.html#rest-api-featuretypes-recalculate I am not sure I see it in the new docs: http://docs.geoserver.org/api/#/1.0.0/featuretypes.yaml -- Jody Garnett On 31 July 2017 at 08:15, Diogo Silva

[Geoserver-users] Extension for GML format missing?

Hi All, I'm looking into getting GML format support in geoserver (preferable for version 2.9.1). According to the documents this can be accomplished by an (currently unmaintained) extension ( http://docs.geoserver.org/stable/en/user/data/vector/gml.html#gml-install). At the download page, under

[Geoserver-users] GeoServer 2.11.2 released

Hi all, the GeoServer developers are pleased to announce the release of GeoServer 2.11.2 See the blog post get details on the release: http://blog.geoserver.org/2017/07/31/geoserver-2-11-2-released/ -- Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit

[Geoserver-users] Compute from SRS bounds/Compute from native bounds/Reload Band definitions using REST api

Hi all, I'm new to using geoserver REST API and i have trying to create a layer using the api. The problem is that when i upload a GeoTiff using the interface i usually compute the srs bounds and the native bounds when defining the layer and i cant seem to achieve this using the API. Is there a

Re: [Geoserver-users] WFS Request Namespace Inconsistency?

Hi Ben, We added the secondary namespace and all is well. Very interesting that it affected GetFeature but not GetPropertyValue. Thanks! -Gavin On Fri, Jul 28, 2017 at 6:14 PM, Ben Caradoc-Davies wrote: > Gavin, > > both of these problems are likely caused by the lack of a

[Geoserver-users] Freemarker Templates empty Response

Dear Geoserver Users, currently we experienced a problem with the freemarker Templates and the GetFeatureRequest. If Geoserver couldn't find any feature and therefore the response of GetFeature is empty, we want to show a "No results" message instead of the empty html. As far as we know only

Re: [Geoserver-users] Trying to connect to a remote WMS that insists on lower case parameter names

Technically that means the server you are connecting to is not a WMS as the spec allows for any casing of the keys (though interestingly not the values), section 6.8.1. So please raise it as a bug with them about this. On a more helpful note, yes GeoTools does use uppercase for key values but it

[Geoserver-users] multiplying number and raster

Dear Geoserver users How can multiply a number in a raster with wps. Regards, Yousef -- View this message in context: http://osgeo-org.1560.x6.nabble.com/multiplying-number-and-raster-tp5329853.html Sent from the GeoServer - User mailing list archive at Nabble.com.

Re: [Geoserver-users] Trying to connect to a remote WMS that insists on lower case parameter names

Yeah, I have pointed out to them that the server isn't compliant. Think they might have put it in the too hard basket. Thanks Andrea... Regards, Duncan On Mon, Jul 31, 2017 at 6:01 PM, Andrea Aime wrote: > Hi Duncan, > the server is not compliant, the OGC specs

Re: [Geoserver-users] Trying to connect to a remote WMS that insists on lower case parameter names

Hi Duncan, the server is not compliant, the OGC specs state clearly that parameter keys are case insensitive, in all protocols with KVP bindings (like WMS). As a result, there is no way to control the parameters key case, because it's not meant to matter (that said, I guess it can be made so with

[Geoserver-users] Trying to connect to a remote WMS that insists on lower case parameter names

Hi all, I'm trying to setup geoserver (2.11.1) to cascade a remote WMS. When I attempt this I get an error: Connection test failed: Server returned HTTP response code: 401 for URL: https:///wms?REQUEST=GetCapabilities=WMSetc. Turns out that the server I'm connecting to insists on lower