Blog

New releases: Oskari 3.4.0 and hotfix 3.4.1

New releases: Oskari 3.4.0 and hotfix 3.4.1

Oskari 3.4.0. and hotfix 3.4.1. released

Two new Oskari versions have been released!

The updated versions are now available on GitHub and in the Oskari.org Maven repository. The sample application package has been updated on the download link in Oskari.org.

As always you can try out the latest release at https://demo.oskari.org/

From 'myplaces' and 'userlayer' to 'myfeatures'

The biggest news is that the myfeatures functionality is now considered production ready and can be used to replace both 'myplaces' and 'userlayer' functionalities for handling user-generated geographic data. Previously the two allowed user to import features from file and draw/modify features on the map. The new 'myfeatures' will combine the two and add further options.

All three functionalities will be supported by Oskari 3.4.x, but 'myplaces' and 'userlayer' functionalities are considered deprecated and are being dropped from Oskari 4.0. 'myfeatures' combines the functionality of the other two. For existing instances, migrations are provided for data transfer to the new format. For new instances, myfeatures is now the default functionality for handling user-generated data.

The new functionality is much more advanced than myplaces or userlayers. Adding new datasets now allows the user to define which attributes the features will have. This allows much more control for the user but also makes adding features a bit more complicated than it was with a predefined set of attributes. When importing data from files, you can now rename attributes by giving them localized names and hide attributes that you don’t want to show to end users (this has been requested frequently). You can also modify the imported data both on map and for attribute values and format how the attributes will be shown to users (showing an attribute value as a heading without the attribute name, another as an image etc). These changes can also be seen as a negative if the users have become accustomed to how things worked before.

The functionality has been part of the code base for a few releases for preview purposes, and we have also demoed the functionality on multiple occasions. We are still open to any feedback on how to improve user-friendliness of the functionality even further. This is the release where you can fully test the new functionality with your own instance and data and opt-in if you see the benefits or continue using the previous functionalities until they are removed.

There’s still time to improve the new 'myfeatures' before the old bundles ones are removed, so please be active in the community.

Adminstration improvements and other changes

The new version has multiple enhancements for admins. These include:

  • A better layer permission management by grouping system and other roles
  • The layer coverage information is now better presented with user-interface for selecting between coverage from metadata or the layer capabilities
  • The metadata coverage area is immediately updated when saving when metadata id is available.
  • Layer URL-field now has a new "Copy to clipboard" button.
  • RSS feed can be used as annoucement source and can be configured in oskari-ext.properties.

Other changes include

  • Metadata flyout is now resizeable by end-users
  • Search results can now include an url related to that result. The link is now shown to the user when the search result is clicked. The localization can be overridden in an application.
  • An effort for preventing device zoom when pinching with 3 fingers on map
  • Reduced noise in developer console when an embedded maps starts with not all the bells and whistles included
  • User Guide functionality migrated to React
  • Added publiccode.yml

As per usual, library updates continue as well as the migrating old jQuery components to React.

3.4.1 hotfix

The 3.4.1. hotfix for oskari-server has an improved CSW parsing which allows anchor or character string in title. This fixes the cases where the parser wasn't catching some of the metadata encoded the ISO 19139 / INSPIRE.

What's next

Next up we are starting to work on Oskari 4.0.

For complete list of changes, check out Changelog. For updating, read The Migration Guide.

A decorative picture that announces a new Oskari release.