Patch: JMap 6.5f is now available
The 6.5f patch is now available for download on our website: http://k2geospatial.com/support.
Take note that this patch is only compatible with JMap 6.5 and its patches (a-e). If you are using a version prior to 6.5, your JMap Server must be migrated to version 6.5 before installing this patch. After installing this patch, all deployed applications must be updated in JMap Admin.
For your information, a complete version of JMap 6.5 that contains all released patches is now available for download on our website. That complete version can be installed on all JMap versions starting from JMap 6.0.
Warning: If your organization uses editable SQL Server spatial data sources, please ensure that your data have the same SRID as related spatial data source in JMap. If you have any questions regarding this, please contact the K2 Geospatial's technical support.
Note: JMap 6.5f is compatible with our new version of JMap Web (7.0 preview). It must be installed separately and is available on our web site (http://k2geospatial.com/support).
JMap 6.5f release notes
New features / improvements
- Added a REST service to JMap Server to perform certain operations using a REST API.
- Forms in JMap Web will now have a horizontal scrollbar when they are too wide.
- Added a a section in JMap Admin to enter Route Logistics Service host and client ID.
- Added a REST service for the Route Logistics Service token generation.
- Added an icon for home screen shortcuts on mobile devices for JMap Web.
- Anonymous users can now use public print templates in JMap Pro.
- Added A3 print format in JMap Web.
- Added more robustness when reading DNG files.
- Added attribute query groups in JMap Web.
- Resource caching is now used more efficiently in JMap Web running in Internet Explorer.
- Added automatic redirection to HTTPS in deployed JMap Web applications.
- Updated JMap Web and JMap Mobile to Google Maps version 3.24.
- JMap Server now better handles requests to unregistered extensions.
- JMap Pro window is now maximized by default when running outside of a web browser.
- Added support for the "NAD83 / California zone 2 (ftUS)" projection.
Bug fixes
- Fixed a problem that caused JMap Pro to crash when using a photo component in a subform when using Java 8u91.
- It is now impossible to set heat map intensity higher than 100%.
- If a default print layout was renamed it lost the default flag in JMap Pro.
- Fixed a problem that caused an error when editing data in a JMap Spatial table with a computed column.
- Publishing a personal layer did not make its source table editable in the database.
- Permissions for style templates could not be saved.
- While configuring a WMS layer, the interface froze when trying to add a group of layers that had a title but no name defined. Since this is not valid, the Add button is now disabled in such a case.
- Owner of a new form was set to "Default" instead of the user who created it.
- Some warnings could be displayed when using JMap Pro with Java 8.
- Spatial Data Sources with lower case names appeared at the end of the list.
- Errors could happen when extracting data from a spatial data source with external attributes.
- Moving a layer in the hierarchy using options "before" or "after" did not work correctly in JMap Admin.
- Statistics are now automatically recalculated when using JMap Spatial tables.
- It was impossible to grant "Remote access" permission if the user did not have the "Access JMap Admin" permission.
- Fixed a problem that caused an error when inserting data in a MySQL spatial data source and using existing metadata fields (author, creation time, modification time).
- Fixed a problem that caused a layer name conflict in the GeoWebCache configuration when deploying a JMap Web application.
- Fixed a display problem in the list of deployed extensions for an application in JMap Admin.
- An error could happen when reading elements with empty geometries from Enterprise Geodatabase data sources.
- An error could happen when reading elements with empty geometries from WFS data sources.
- The "Compute statistics" option of GDAL spatial data sources was not included in the configuration exportation and importation.
- Static external attributes were imported as dynamic attributes.
- An error could happen when opening an advanced report on a cloned layer.
- WFS spatial data sources did not support attribute queries.
- It is now impossible to activate proportional symbols and clustering at the same time.
- The "NAD 1983 StatePlane Idaho East FIPS 1101 Feet" projection had an invalid falseX value.
- Added missing icon for layer of complex elements.
- Fixed a problem in JMap Web that could cause selection styles to be invalid.
- The first base layer in the list was always visible by default in JMap Web, ignoring the configuration in JMap Admin.
- Fixed errors related to element selection events in JMap Web.
- Added missing library in JMap Mobile and JMap Web deployment templates.
- Users who are also administrators and owners of layers don't automatically inherit layer editing permissions anymore.
- Fixed a problem that caused layers by reference to have out of synch attribute values.
- JMap Server WMS service can now apply vertical and horizontal scaling of the map, in accordance with the OGC standard.
- Curved polygons extracted from Personal Geodatabase data sources were not displayed properly.
- Fixed a problem when reading TAB files that had "," characters in their data.
- It was not possible to include twice the %param[] syntax when defining the URL of a custom report.
- An exception could occur while using the user management section in JMap Admin.
- When attaching a photo to an element, the photo could sometimes be visible on all elements thereafter in JMap Pro.
- The print scale in now excluded from the saved user parameters. It was useless to save it.
- An error could occur while trying to open a permission report for a user.
- It was impossible to configure a WMS spatial data source if one of the parent layers did not have a CRS defined.
- Fixed a problem that caused all form component entries to be required after updating from JMap 6.0 to JMap 6.5.
- A problem could occur on JMap Server when closing WMS sessions.
- Improved the performance when loading very big complex elements.
- Some SVG symbols could be positioned incorrectly.
- Fixed the WKT encoding of polygons with holes produced by JMap Server.
- The list of permissions on a database form could incorrectly be empty when using a layer by reference.
- An error could occur when using forms to update or delete data with numeric or decimal fields.
--------------------------------------------------
Jean-Robert Desbiens-Haddad
Chief Technology Officer
K2 Geospatial