You might consider using layer keywords, which will be persisted in the
layer configuration.
Otherwise, GeoMesa used to have a custom page for configuring a raster
store (not a layer). Not exactly what you were looking for, and it's
several years out of date at this point, but might point you
It would be nice if GeoServer could host SHA hashes and/or GPG
signatures on geoserver.org for each release. That is a fairly standard
practice, and would go a long way to verifying the integrity of
downloaded artifacts.
Thanks,
Emilio
On 10/7/20 10:42 AM, Ian Turton wrote:
The only way
The only way that you could in good conscience claim to have a trusted
build to those standards is to maintain your own clone of the project
locally and build directly from that using the commit number specified in
the GeoTools, GeoWebCache and GeoServer release notes. Obviously, you'll
want to
Hi,
I use and deploy geoserver (through the war file) within a company that has
high (and mostly legitimate) concerns about security.
Currently, geoserver stable / maintenance / .. versions can only be
downloaded through *SourceForge*.
I know that, those latest 4 years, SF made great effort
Also, restart GeoServer, when an exception is thrown many times, the trace
is compressed and part of it is omitted. There is also a JVM flag that can
be set to avoid trace
elision, for reference:
https://dzone.com/articles/missing-stack-traces-repeated
Cheers
Andrea
On Tue, Oct 6, 2020 at 9:36
Morning Christian,
the imagemosaic-jdbc plugin has been moved back to "community" modules.
You will find it in the nightly snapshots download area:
https://build.geoserver.org/geoserver/2.18.x/community-latest/
The direct link:
That module was downgraded to unsupported as it has no maintainer (see
https://geotoolsnews.blogspot.com/2020/09/geotools-240-released.html) so
you will now need to build it yourself,
Ian
On Wed, 7 Oct 2020 at 06:42, Christian Mayer wrote:
> Hi everybody,
>
> I am currently updating my
