The http://www.geopackage.org standard is now a popular data format, and GeoPackage data source has been included with GeoServer as a data source for some time.
We would like to make the WFS and WMS GeoPackage output formats from the GeoPackage community module available as an extension.
I am in favor of making it an extension to ensure maintenance.
However, I am still not in favor of GeoPKG to become a “supported” output for WMS and WFS unless there is a working solution to prevent (unintentional) denial of service requests. A simple feature or layer count might not be sufficient… What if a user starts the production of a humongous GeoPKG accidentally? There is no way to stop it!? You need something like asynchronous processing …
The http://www.geopackage.org standard is now a popular data format, and GeoPackage data source has been included with GeoServer as a data source for some time.
We would like to make the WFS and WMS GeoPackage output formats from the GeoPackage community module available as an extension.
I have a fix for GEOT-7011 but that is a separate issue and not part of the proposal.
The existing restrictions on WFS output are sufficient to keep a system stable with shapefile or geopackage output.
You can use control flow to place further limitations on a specific output format (indeed this is the module focused on denial of service).
WPS output offers async if required for massive content.
That is great! Could you please alert me once the fix for 7011 is included in a Geoserver build. I am happy to update my code then and run the axis order confusion tests to make sure…
I have a fix for GEOT-7011 but that is a separate issue and not part of the proposal.
The existing restrictions on WFS output are sufficient to keep a system stable with shapefile or geopackage output.
You can use control flow to place further limitations on a specific output format (indeed this is the module focused on denial of service).
WPS output offers async if required for massive content.
–
Jody Garnett
On Sun, 9 Jan 2022 at 23:40, Andreas Matheus / Secure Dimensions <am@anonymised.com> wrote:
Hi Jody,
I am in favor of making it an extension to ensure maintenance.
However, I am still not in favor of GeoPKG to become a “supported” output for WMS and WFS unless there is a working solution to prevent (unintentional) denial of service requests. A simple feature or layer count might not be sufficient… What if a user starts the production of a humongous GeoPKG accidentally? There is no way to stop it!? You need something like asynchronous processing …
The http://www.geopackage.org standard is now a popular data format, and GeoPackage data source has been included with GeoServer as a data source for some time.
We would like to make the WFS and WMS GeoPackage output formats from the GeoPackage community module available as an extension.
On Tue, Jan 11, 2022 at 11:05 PM Andreas Matheus / Secure Dimensions <am@anonymised.com> wrote:
Hi Jody,
That is great! Could you please alert me once the fix for 7011 is included in a Geoserver build. I am happy to update my code then and run the axis order confusion tests to make sure…
I have a fix for GEOT-7011 but that is a separate issue and not part of the proposal.
The existing restrictions on WFS output are sufficient to keep a system stable with shapefile or geopackage output.
You can use control flow to place further limitations on a specific output format (indeed this is the module focused on denial of service).
WPS output offers async if required for massive content.
–
Jody Garnett
On Sun, 9 Jan 2022 at 23:40, Andreas Matheus / Secure Dimensions <am@anonymised.com> wrote:
Hi Jody,
I am in favor of making it an extension to ensure maintenance.
However, I am still not in favor of GeoPKG to become a “supported” output for WMS and WFS unless there is a working solution to prevent (unintentional) denial of service requests. A simple feature or layer count might not be sufficient… What if a user starts the production of a humongous GeoPKG accidentally? There is no way to stop it!? You need something like asynchronous processing …
The http://www.geopackage.org standard is now a popular data format, and GeoPackage data source has been included with GeoServer as a data source for some time.
We would like to make the WFS and WMS GeoPackage output formats from the GeoPackage community module available as an extension.
Medium
