Please give us a hint!
what projection is your map in? your data in? how did you define the axis
order? which version of which standard did you use?
Without that information we are just guessing
Ian
On Thu, 4 Apr 2019 at 17:10, Pablo Schweitzer wrote:
> Hello
> I'm incorporating a layer in
Hi,
I had the same problem. Turns out that one of the layer in the layers group
was causing the error.
We had this message in the log (verbose) :
"Error writing metadata; skipping layer: LAYERNAME"
Verify if you have this message in the log.
Try creating another group, add one layer and check
Hello
I'm incorporating a layer in my geoserver from this service
https://geoservicios.indec.gov.ar/geoserver/ows? but I have problems with
the axes. How is it solved?
[image: image.png]
Thanks!
Pablo
___
Geoserver-users mailing list
Please make sure
Hi,
as far as I know, the WMS standard does not say anything about layer
groups, so not including them in the capabilities document could probably
not be considered a bug in itself. But layer groups are included in the
capabilities document by default (with *.*.r=*). By this logic, shouldn't
they
Hi,
I'm Micho, I work at geomati.co, I am an OSGeo charter member and first of
all my total admiration for your work developing and maintaining GeoServer.
We are using GeoServer maybe in a weird use case, we are publishing geotiff
as granules of an imagemosaic with the time dimension. When we
Hi All,
I've problem with support geometry function in WFS 2.0 when a geometry
attribute is defined in DataType class and not directly in featureType
class. For example: INSPIRE Address application schema 4.0 where
geometry of address type is position:GeographicPosition:geomerty:GM_Point.