Hi Jakub,
I can't replicate this myself making requests for GetCapabilities
documents. What was the version "number" you were using? Or was it for a
different request type?
On an old 2.7 instance, the following bring back an exception document
of type NoApplicableCode containing the
Kevin,
I expect that this is caused by the feature of interest lacking a
geometry property at the top-level (an attribute in UML-speak). In the
tutorial example, MappedFeature has a geometry property, but
GeologicUnit has only an association with zero or more MappedFeatures
that describe its
Kevin,
a common pattern is to deliver WMS with a simple features profile; for
example, GeoSciML has a bunch of "portrayal" schemas with type names
ending in "View". If you can resolve your property cardinality mapping,
these simple features support WMS just like any other. This can also be
a
Hi,
Layer 'gsml:GeologicUnit' fails the rendering process in WMS because it
doesn't have any defined geometry, maybe the rendering pipeline should
be more explicit about this.
Anyway, if you are interested in WMS I guess is because you want to
actually draw something so a geometry is required
Hello all,
I'm trying to enable WMS support on an app-schema feature per the instructions
here
(http://docs.geoserver.org/latest/en/user/data/app-schema/wms-support.html).
The data is retrievable via WFS 2.0 requests, but when I try to request the
product via WMS the client receives a
Hello Ben,
Thanks for the quick response. I see what you mean about the location of the
spatial element within the XML response structure. Most of our schemas (which
I do not control) bury it a few levels deep so I don't think the app-schema
plugin will work for us unfortunately.
Thanks
On Tue, Nov 29, 2016 at 6:00 AM, 신상희 wrote:
> Dear all,
>
> My team is now facing a similar issue as Andy mentioned[1] a couple of
> month ago. When we tried to load around 9,000 layers from PostGIS using
> GeoServer 2.9.x or 2.10.x, it took almost 1 hour as opposed to 30
Hi All,
We are using WPS in Geoserver 2.8.4 and have noticed that we cannot
retrieve the status of an asynchronous WPS request which has completed
after restarting GeoServer. The final response/outputs are still
available in the resource storage directory as the expiry time has not
elapsed but
Thanks Daniele - delayed also here due to work ‘stuff’.
I just got to setting up a new instance of geoserver (master/latest, deployed
from the nightly war file) for testing. it showed the same errors as my 2.10
attempt - until I removed the GDAL plugin.
So far the imagemosaic part is working
Dear Simone, Dear List,
to recall the problem:
> >> > I am using Geoserver 2.7.5. I want to create a layer out of several
> >> > geotiffs so I created an imagemosaic. The geotiffs are 32bit tifs an I
> >> > want to colorize them using Geoserver Styles. The single tifs overlap at
> >> > the
10 matches
Mail list logo