Hi Ian
Just for clarification, it’s not an issue with the datastore, but differing
output formats for a WFS, ‘text/csv’ as an outputFormat truncates the values,
GeoJSON/GML32 does not. The datastore in question is Postgres, but I don’t
think that is material to this problem.
Thanks
Michael
F
Also, let me sweeten the pot a little bit: if someone steps up and manage
the translations, I'll write a language switcher control :-D
Weblate seems to automate the creation of PRs too, so maybe if an export
from transifex was possible, then the actual amount
of work for the "translation manager" w
Hi Christian,
the imagemosaic-jdbc plugin has been removed from the GeoServer source code,
after years without a dedicated maintainer.
It can be resurrected from the dead: that will require a new maintainer, or
someone
interested in investing in it so that other developers can get familiar
with th
Hi all,
I tried to upgrade our GeoServer instances from 2.19.x to 2.20.x
(wrapped as Docker image, which should not be the point here). For
version 2.19.x I could download the ImageMosaic extension from
https://build.geoserver.org/geoserver/2.19.x/community-latest/geoserver-2.19-SNAPSHOT-imagemosa
On Tue, 2 Nov 2021 at 02:11, Michael Sexton
wrote:
> Another issue, GeoJSON coordinates exhibit the same truncation, even
> though feature properties don’t.
>
>
>
> ·
> *geometry"*: {
>
> o*"type"*: "Point",
>
> o*"coordinates"*: [
>
> § 139,
>
> § -19,
>
> § 212
>
> ]
>
> · },
