From sami.makinen at maanmittauslaitos.fi Mon Oct 5 07:41:27 2026 From: sami.makinen at maanmittauslaitos.fi (=?utf-8?B?TcOka2luZW4gU2FtaQ==?=) Date: Mon, 5 Oct 2026 14:41:27 +0000 Subject: [Oskari-user] Oskari 3.4.0 released! Message-ID: Good news everyone, The new version is now available on GitHub (https://github.com/oskariorg) and Oskari.org Maven repository. The sample application package has been updated on the download link in Oskari.org (https://oskari.org/download) and http://download.osgeo.org/oskari/. As always you can take a peek at the latest release at https://demo.oskari.org/. 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. 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. Take a look at the migration guide regardless! Next up, we are starting to work on Oskari 4.0 that will drop support for myplaces/userlayers and remove code related to them from the codebase. The new functionality is much more advanced than myplaces or userlayers, which however might also be seen as a negative, if users have become accustomed to how things worked before. 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). We have streamlined the process of adding new datasets by initializing a default name-attribute with localizations for features on a new dataset. This makes it easier for users to add simple datasets but also allows the user to fully configure the dataset (the pre-initialized attribute can be removed, replaced, renamed by users). 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 but of course are fully 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. As we don?t have resources to maintain all three functionalities, the old ones will be removed in 4.0 and there?s time to improve the new one before the old ones are removed, but only by being active in the community ? The compiled list of release notes can be found on https://oskari.org/documentation/docs/3.4.0/12-Changelog Current thoughts for version 4.0/roadmap: * Forced migration to myfeatures * Removal of myplaces and userlayers from codebase * Spring 6 -> 7 version and related Tomcat 10 -> 11 migration * On frontend side: still hopeful for a new API/React implementation of the main navigation and flyout UI * Also migrating containers for map plugins from jQuery to React * Possibly toolbar implementation with React and SVG-icons Happy updating, Sami -------------- next part -------------- An HTML attachment was scrubbed... URL: