On Tue, Aug 7, 2018 at 7:55 PM Kris Johnson wrote:
> I don't think it's a version issue since I'm using version 2.13.1 on Linux.
> It might also be helpful to note that all datasets are being stored in a
> postgis database.
>
Ok. As said before, then please try to find a way to reproduce and
I don't think it's a version issue since I'm using version 2.13.1 on Linux.
It might also be helpful to note that all datasets are being stored in a
postgis database.
On Tue, Aug 7, 2018 at 12:47 PM, Andrea Aime
wrote:
> Ah, I see that you did not report the GeoServer version. If you're using
>
Ah, I see that you did not report the GeoServer version. If you're using an
old version, you might be affected by this one:
https://osgeo-org.atlassian.net/browse/GEOS-8291
Cheers
Andrea
On Tue, Aug 7, 2018 at 7:45 PM Andrea Aime
wrote:
> Hi,
> the generic style is used only when it's not
Hi,
the generic style is used only when it's not possible to determine the type
of geometry in the table
(unless you assigned it manually).
If you have a step by step procedure to reproduce the issue it would be
quite a valuable entry
as a bug report here:
Hello Ian & Co.,
You might be onto something. When I assign a default style to a layer that
was previously broken, it now works.
This is a fine solution for me, but I swear that times that I've used
Geoserver in the past, the "generic" style that Geoserver ships with is
used when a layer doesn't
I'm pretty sure that you need to specify a default style for each layer.
Ian
On Tue, 7 Aug 2018, 18:07 Kris Johnson, wrote:
> Another bit of info to add to this is that the layers that work have a
> default style assigned to them. And the layers that are not working do not
> have a default
Kris,
This might be a bit of a shot in the dark, but that behavior reminds me of when
I had non-XML Safe naming conventions for my layers/stores/data.
Try taking one of those layers that is giving you issues, and putting it into
a path in the data_dir that has no spaces or special characters,
Another bit of info to add to this is that the layers that work have a
default style assigned to them. And the layers that are not working do not
have a default style.
Are layers required to have a default style? I thought they would be given
a generic style in the instances were there was no
Hello,
Some (but not all) of my layers are returning errors when trying to run a
WMS GetMap request on them. This happens using both the openlayers Layer
Preview and running regular HTTP requests from my web application.
Here is the error I see in the logs:
2018-08-07 16:55:08,300 DEBUG
Dear Clifford,
please, read below...
Regards,
Simone Giannecchini
==
GeoServer Professional Services from the experts!
Visit http://goo.gl/it488V for more information.
==
Ing. Simone Giannecchini
@simogeo
Founder/Director
GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
Italy
Hi,
I had misresad your original message, given the other conversations it
would indeed appear to be a network issue
of sorts
Cheers
Andrea
On Tue, Aug 7, 2018 at 4:50 PM Carlock, Brett
wrote:
> Any direction/assistance is more than appreciated.
>
>
>
> I see no indication that Windows is
Any direction/assistance is more than appreciated.
I see no indication that Windows is doing anything untoward with the content of
the data_dir (reverts, etc). Nothing’s going missing, and changes I make
against geoserver’s config seem to stick.
The data are generated mostly by myself
Hello Brett,
thank you for forwarding my previous response to the mailing list :-)
The error shown in the console might or might not be the source of your
problem. According to the current OpenLayers source code, error #25 originates
in the method 'View.fit'
Hi Alessio,
some quick feedback.
About
https://github.com/geoserver/geoserver/wiki/GSIP-169#statusinfo-document
- How do you compute the estimated completion and the next poll? Do they
need a API change in the WPS core?
- The JobId is the id of the execution, while the identifier is the
14 matches
Mail list logo
