Hi Ian and Andrea,
thanks for your input and recommendations. I'll try to create a
community extension (using flatgeobuf and others as a starting point /
boilerplate). I'm using Eclipse and still struggling with Maven.
However, things are moving...
I will also have a look at the flatgeobuf format.
Still not sure whether subclassing requires changes in the existing
GeoJSON producer (and which). I guess, with no changes I'll lose support
for JSONP, unless I'm also overriding the write method (using my own
jsonp field). Likely removing the final modifier from the jsonp field in
existing GeoJSON producer whould be helpful.
Cheers
Carsten
On Tue, Sep 13, 2022 at 2:20 PM Andrea Aime wrote:
Agreed, it should start as a community module. Happy to review changes
to make subclassing the existing GeoJSON
producer easier. Or you can just copy and modify, if you like, to get
prototyping moving on faster.
If you are interested in a ready made compact and efficient format
instead, I suggest looking into flatgeobuf
<https://github.com/flatgeobuf/flatgeobuf>, it already
has a Javascript reader library and GeoServer has a community module to
generate it as a WFS output format.
Cheers
Andrea
On Tue, Sep 13, 2022 at 1:54 PM Ian Turton <ijtur...@gmail.com
<mailto:ijtur...@gmail.com>> wrote:
Sorry hit send too soon!
I would also prefer it if it was an extension rather than part of
the core GeoServer.
Ian
On Tue, 13 Sept 2022 at 12:52, Ian Turton <ijtur...@gmail.com
<mailto:ijtur...@gmail.com>> wrote:
I would suggest calling it something other than GeoJSON since if
it strays too far from the spec clients will become confused.
Ian
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
