Hello Marco,
Thanks for clearing this up. I have made a PR
https://github.com/geotools/geotools/pull/4016
Cheers
Niels
On 13/09/2022 08:10, Marco Volpini wrote:
Dear Niels,
thanks for your point. I think that the block can indeed be removed. I
don't remember why I've added that but I did s
Hello everyone,
I found a bug in app-schema that was recently introduced by
https://osgeo-org.atlassian.net/browse/GEOT-7214, a patch by Marco
Volpini, but I am a bit confused about the changes and would like to
know to what extent they are intentional. Bug logged at:
https://osgeo-org.atlass
..
Cheers
Andrea
On Sat, Apr 2, 2022 at 2:42 PM Niels Charlier via GeoTools-Devel
wrote:
Hello Brad,
I do not recall why the test was ignored. It actually seems to
work when
I try so I wouldn't personally remove it.
I have to say I don't remember much about this modu
Hello Brad,
I do not recall why the test was ignored. It actually seems to work when
I try so I wouldn't personally remove it.
I have to say I don't remember much about this module any more, and I do
not use it. Since it is a plugin I suppose someone is maintaining it?
Kind Regards
Niels
Hello everyone,
Thanks for your comments. I suggest then that I implement the behaviour
as it was suggested in the example of WFS 2.0 specs, since this is also
the least invasive for the geotools/geoserver code, and there don't
appear to be any particular objections against it. I suggest also
On Mon, Oct 11, 2021 at 3:21 PM Niels Charlier via GeoTools-Devel
<mailto:geotools-devel@lists.sourceforge.net>> wrote:
2) allow reprojection 3D->2D and only prevent 2D->3D reprojection
(Andrea's suggestion).
Before this gets out of hand, my suggestion is limited to th
Hello Jukka,
Thanks for your answer. I guess I wanted to ask the opinion of the
community on how to proceed. I see at this point two options:
1) stick with the suggestion of the standard, and do not project 3D->2D.
(The easiest solution, what I already have).
2) allow reprojection 3D->2D an
Hello Everyone,
I am sending this email to both geotools and geoserver lists because the
matter concerns both.
I recently made a PR to improve geotools/geoserver behaviour with
respect to multiple geometries that have different CRS.
(https://github.com/geotools/geotools/pull/3642) One of the
I guess I sent this to the wrong ML
Forwarded Message
Subject:[Geoserver-devel] powermock for unit tests in app-schema
Date: Mon, 8 Mar 2021 13:01:23 +0100
From: Niels Charlier via Geoserver-devel
Reply-To: Niels Charlier
To: Geoserver-devel
Hello,
x27;t be pretty :-D
Cheers
Andrea
On Thu, Sep 3, 2020 at 1:14 PM Niels Charlier via
GeoTools-Devel mailto:geotools-devel@lists.sourceforge.net>> wrote:
Hello,
Is it correct that there is currently no possibility to
read ma
els
On 03/09/2020 14:33, Andrea Aime wrote:
Hi Niels,
the mbtiles store can read vector tiles stored in a sqlite
database. For map rendering usage only,
don't try to use that thing for WFS, won't be pretty :-D
Cheers
Andrea
On Thu, Sep 3, 2020 at 1:
vector tiles stored in a sqlite database.
For map rendering usage only,
don't try to use that thing for WFS, won't be pretty :-D
Cheers
Andrea
On Thu, Sep 3, 2020 at 1:14 PM Niels Charlier via GeoTools-Devel
<mailto:geotools-devel@lists.sourceforge.net>> wrote:
Hello,
Hello,
Is it correct that there is currently no possibility to read mapbox
binary vector tiles with geotools (PBF files).
There is a mapbox style parser, but I don't see anything there that can
be done with PBF sources specified inside it.
Geoserver has MB vector tiles output format (an old
There is "Expression/NIL".
But it is not a literal, it's a property :/ A pseudo-property I'd say.
See org.geotools.filter.expression.NullPropertyAccessorFactory
It definitely has uses, it's used in both app-schema and CSW mappings.
A literal would be more appropriate.
Regards
Niels
On 15/0
14 matches
Mail list logo