Add Geopackage and DXF output format support #542
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
woutergd
force-pushed
the
features/geopkg-dxf-support
branch
from
3ba78ad to
50c5c72
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As discusses in issue #531, there was no reason to include support for geopackage and dxf except that it wasn't implemented yet.
Hereby the implementation that (as far as I can see and test) works. It implements the extensions in a way identical to for instance the flatgeobuf extension, which is a community extension of the regular Geoserver. As I am not familiair enough with the WPS modules in Geoserver Cloud, I did not incorporate the WPS modules in this PR for both formats.