Page Comparison

...

The details and direct links to the releases are available at:

• release-2.6.txt

Additionally, there is a newer download site available that provides links to the latest stable releases. It is hosted in the cloud to provide for faster downloads.

2.6.4

Enhancements

• Weave Hub
  • A new third party application integration library to replace Weave Link and provide integration in browsers other than Internet Explorer. Currently supports Authority, Pathway, Proclaim and Trim integration.
• New Redline Tools
  • Edit coordinates of geometry
  • Upload geometry from a file
• New Spatial Edit tools
  • Edit coordinate of geometry
  • Upload geometry from a file
• GDA2020
  • Initial support for using the GDA2020 projection
• Metrics
  • Added metrics support so Weave can be monitored externally, currently supports Prometheus, InfluxDB and Datadog.
  • Note this will not be installed/enabled when updating an existing instance, so as to not add the overhead to sites that do not wan it, so to install it for an existing instance re-run the 2.6.4 installer pointing it to the newly updated 2.6.4 instance and disable everything but the metrics component.
• Help
  • The default help content is now provided as part of the installation
  • Note this will not be installed when updating an existing instance, so as to not overwrite any customisations that may have been applied, so to install it for an existing instance re-run the 2.6.4 installer pointing it to the newly updated 2.6.4 instance and disable everything but the help component.
• Zip'n'ship
  • Supports exporting to GeoPackage
  • Data sets can be grouped into folders
• Tiled map engines
  • Tiled map engines can now be configured for performance or quality when re-projecting the tiles and they can be configured to fetch multiple tiles in parallel
• Stitching dynamic map engine
  • If a back end map service only supports generating images up to a certain width and height, looking at you ArcGIS, you can now create a wrapper "stitching" map engine that can be configured with the maximum width and height that the back end map service supports and the stitching map engine will make multiple requests to the back end map service to so that it only requests image of the size the map service supports and it will then stitch the images back together to make a single image of the originally requested size. This is particularly important for BIRT reports when large embedded map components, so now you can for example generate an A0 size report even if the map service in use only supports generating images 1000x1000 pixels

Fixes

...