Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Version History

« Previous Version 114 Next »

2.4.26

Pending Release
The following updates are available as a hotfix for 2.4.25.
Download .jar hotfix 2.4.25.2
Download .zip hotfix 2.4.25.2

Enhancements

  • WMS scale adjustments.
    • Some WMS services report their scale ranges based on a more rigid interpretation of the WMS specification, if you set adjustWmsScales to true in a server side map engine configuration it will take this into account when reporting the scale ranges to the client. This can be an issue because most WMS services seem to assume 96DPI when reporting scales ranges, but the spec says that it should be 90.7DPI, so if your client tool used to set the scale range is running an 96DPI and you set the scale to 10,000, the WMS server may tell Weave that the scale is actually 9447.916 (90.7/96*10000), so Weave need to undo this conversion to get back to the original value. So far Carmenta WMS server is the only one we've found with this issue.

Fixes

  • 'pressed' not working for map tips.
    • If 'pressed' is set to true in the map tips configuration the button is pressed but the map tips don't appear, if you turn the button off then on they then work correctly.
  • ToC issues.
    • Some minor issues with the client ToC code when things were mis-configured would stop the client from working.
  • Uploaded files wouldn't re-project.
    • File uploaded in a different projection would not be re-projected on the fly to the current map extent.
  • Index search issue.
    • The default wildcard search wasn't working properly, it would perform a fuzzy search instead, which could results not being returned when they should be.
  • MIF driver fix.
    • The MIF file driver was not handling geometry collections correctly.
  • BIRT redline issue.
    • Redlines were not drawn on a map embedded in a data set.
  • No labels