That is great news, thank you!
Cheers
Andrea
On Fri, May 7, 2021 at 4:07 PM Matthijs Laan via GeoTools-Devel <
geotools-devel@lists.sourceforge.net> wrote:
>
> As it is the simplest of all the GML parsers maintenance wouldn't be a
> problem for me.
>
> To bring the functionality up-to-par with g
As it is the simplest of all the GML parsers maintenance wouldn't be a
problem for me.
To bring the functionality up-to-par with gt-xsd-gml3 the code from the
bindings can be ported over without much trouble. I intend to do that as
mentioned for some elements I currently need, but will look
Hi Mark,
I agree with the sentiment in general, that code has been left there
rotting, making it more visible
might spur some interest in it.
However there lies the issue... it's getting moved from a module that's
officially unsupported, to
one that is, and while it's still incomplete in functional
On 06-05-2021 10:55, Matthijs Laan via GeoTools-Devel wrote:
The internal StAX GML parser from the wfs-ng module would be useful as a
public API as it is much simpler and faster than the GTXML parsers,
although the latter supports more GML elements.
Beside the GTXML parsers there is also a S
The internal StAX GML parser from the wfs-ng module would be useful as a
public API as it is much simpler and faster than the GTXML parsers,
although the latter supports more GML elements.
Beside the GTXML parsers there is also a SAX GML parser in gt-xml,
package org.geotools.gml.
Would it
