Skip to content

WWSK 0.4.0

Pre-release
Pre-release
Compare
Choose a tag to compare
@emxsys emxsys released this 22 Aug 23:45
· 370 commits to develop since this release
v0.4.0
9a1346d

Date

22-AUG-2017

Release Summary

The WWSK v0.4.0 includes the following new features and bug fixes:

  • An About WWSK page that displays the WWSK version number
  • An Export GeoPackage page that displays a form to issue a WPS request to export a layer to a GeoPackage
  • A fix that allows GeoPackages with hyphens in the table names.

The new Export GeoPackage feature allows layers to be exported at full-fidelity, as compared to the Layer Preview, which will — in a future release — constrain the size of a GeoPackage, which may limit the number of levels of resolution. The Export GeoPackage also provides for more granular control of the GeoPackage contents. The Export GeoPackage is a secured page. You must be logged in for it to be available.

Time constraints for this release precluded a fully-featured Export GeoPackage. Functionality planned for a future release includes:

  • Using the bounds of another layer to set the bounds of the exported GeoPackage
  • Setting the background color
  • A style selection component
  • Input validations
  • An improved download link page
  • Exporting vector layers as vector GeoPackages

In previous versions of WWSK the Layer Preview | GeoPackage export imposed a constraint on the number of levels exported (4). This constraint prevented GeoPackage exports from taxing the server with lots of WMS requests needed the for higher zoom levels. With this constraint removed, higher resolution levels can be generated, but it introduces the liability of overloading the server with an enormous number of tile requests.

To mitigate against this risk, consider enabling MIME type checking in the WMS Service settings and do not include the application/x-gpkg in the list of allowed MIME types.

Note: The constraint on the number of levels generated in the Layer Preview / WMS export could be reimposed in a future release. The WPS export is not affected by this constraint

Associated GitHub Issues

No. Description Type
#82 Export a layer as a GeoPackage enhancement
#72 Cannot add a layer from a GeoPackage containing a hyphen in the table name bug
#69 Add "About WWSK" to GeoServer new feature

Known issues

No. Description Type
#89 Reestablish WMS constraint on GeoPackage size task

Impacts to other development teams/compatibility

A new module was added to the WWSK maven project:

Versions

Component Version Previous
GeoServer 2.11.1
GeoTools 17.1
GeoWebCache 1.11.0
ImageIO-Ext 1.1.17
JAI-Ext 1.0.13
Jetty 9.2.13.v20150730

End User impact/User facing changes

A new WWSK menu category was added to the GeoServer web administration interface. Under the WWSK menu category are the About WWSK and Export GeoPackage links. The Export GeoPackage link is not visible if you are not logged in.

The About WWSK shows the version number of the WorldWind Server Kit and manifests links to NASA WorldWind resources.

The Export GeoPackage link manifests a new form for issuing a request to export a layer to a GeoPackage via a WPS. The form will pre-fill many of the fields upon the selection of a layer. After completing the form, click the Execute button to issue the request. When the execute request is finished, a popup window displays a link to download the prepared GeoPackage. Note, there is a timeout on the link, you must download it before it expires. The form also allows you to generate the XML for a request so that can copy and paste it into a cURL request or other client.

Reminder: Exporting to a GeoPackage via the Layer Preview is a user facing feature that does not require a login. To mitigate the risk of an overburdened server, consider enabling MIME type checking in the WMS Service settings.

Documentation

See the README, GeoServer, GeoPackage and GDAL Image Formats documentation.

Logs

Location of all log files and any special documentation regarding the logging for this component.

Test Tools

Location of any test tools and any brief instructions on how to use them.

Install/Update/Removal

Install

WWSK is installed by simply unzipping a platform specific distribution to a folder on a target computer.

Removal

WWSK is removed by simply deleting the folder in which it was installed. If a wwsk.service has been created (Linux), it should be stopped, disabled and removed.

Update

The recommended practice for updating WWSK is to:

  1. Install a new version of WWSK alongside an older version,
  2. (Optionally) copy/move data and workspaces from the old version to the new version,
  3. Remove the old version.

Updating WWSK by unzipping a distribution into an existing WWSK instance has not been tested and is not recommended.

Notes

Additional notes, links, and information goes here.

Assets 7
Loading