Oskari Roadmap 2026+
Oskari roadmap for 2026 is a compiled by the many organisations that use Oskari and are members of the Oskari Joint Development Forum (JDF).
Oskari's coordinators and the Oskari JDF will continue to work on keeping Oskari as a product that is up-to-date and easy to use. In order to do so, one of the aims for 2026 is to apply for a project funding to do joint developing of Oskari between organisations.
In 2026, Oskari development focuses on both the development of the Oskari core and re-organizing and enhancing the work of the JDF.
Oskari core development in 2026 consists of the following:
Library updates (Q1-Q4)
Updating the existing libraries makes sure that Oskari is up-to-date, safe to use and operates smoothly.
Migrating the old jQuery components to React (Q1-Q4)
Migrating to React will make Oskari easier to use for developers and simplifies maintaining the Oskari codebase. A big leap forward in React migration was made in the Oskari 3.0 update yet some components are still based on jQuery.
Combining My Data (userlayer) and My Places (myplaces) to a new bundle: myfeatures (Q1-Q3)
This is a functionality that will replace My Places (features that user draws on map) and My Data (spatial datasets that user uploads to an Oskari instance). The functionality from user perspective is the same as userlayer today but the internal code will be rewritten on both frontend and server. Preview of the functionality was published in 3.2.0 update in November 2025 and developing will continue in 2026. The functionality is functionalli ready at Q2 2026, is currently being tested and the stable version is included Q3 2026 as part of Oskari 3.4.
Metadata search and display improvements (Starting Q3 2026)
The functionality for searching and displaying metadata records (fetched from a CSW) will be under review and refactoring starting from Q3 2026.
Oskari 4.0 (Starting Q4 2026)
After the 3.4 release we will start working on Oskari 4.0. Initial goals are updating server side libraries like Spring Framework version 6 to 7, Jackson 2 to 3, Tomcat 10.1 to 11 and related changes. For frontend functionality, as we are already bumping the major version, we would love to include a React-based implementation of the main navigation. For Oskari-based applications with customized functionality, this means that functionalities using the jQuery-based flyouts will probably need to be updated to React. We are still investigating the options we can support for these. Other frontend changes that could be included are:
- SVG-based (theme colored!) icons for toolbar and a new API for the toolbar functionality
- Migrating plugin containers on map that are still initialized with jQuery. These are on the roadmap for removing the jQuery parts from these, but its not certain we can include this on 4.0 (basically the buttons on top of the map might see some API change)
- Functionality for myplaces and userlayers will be dropped on 4.0 as the myfeatures functionality is the planned replacement for these and it is not feasible to maintain both myfeatures and the older similar functionalities side by side as we have plans on making myfeatures better than myplaces or userlayers are.
Improvements on the documentation (Q1-Q4)
To make sure that Oskari is easy to implement and develop, the documentation has to be comprehensive and up-to-date. In 2026 the work on improving the documentation will begin with revising the RPC section and going through the issues listed in the GitHub repo of documentation.
The Oskari Roadmap process
Oskari software is developed different parties: the National Land Survey of Finland, which is coordinating the Oskari project, organizations that use and develop Oskari and individual Oskari community members. The development is based on jointly created vision described in the Roadmap and the individual needs of Oskari developing organizations. The source code provided by the community members or other developers will be integrated into the core Oskari software if deemed suitable. The development projects should document the created source code with good codes of conduct, so that the reuse of the code is fluent. The technical team of NLS FI checks the documentation before a commit can take place.
Release schedule
New Oskari versions are being released 2-4 times a year. Usually there is a new version every 3-4 months.
