[Oskari-user] Oskari 3.3.0 released!

[Mäkinen Sami]

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 release doesn't have many visible changes for end-users, but it does have lots of library updates like:

  *   OpenLayers 10.6.1 -> 10.8.0
  *   Cesium 1.135.0 -> 1.139.1
  *   Webpack  5.102.1 -> 5.105.4
  *   AntD 5.27.5 -> 5.29.3 (might require an application to migrate from AntD Select/Option-components to a new syntax)
  *   Spring framework 6.2.11 -> 6.2.17
  *   Jackson 2.20.0 -> 2.21.1
  *   and many other dependency updates

We are working towards making the myfeatures-functionality (combination of myplaces and userlayers) production ready. The current state of the functionality can be enabled for preview by following the same steps like before (adding/importing the frontend-functionality, adding the server-side dependency and enabling the new Flyway-migration module). The functionality is technically stable, but we are still working on the migrations and making the user-interface more user-friendly.

Some fixes and new functionalities have been added while working on myfeatures that can be helpful on applications based on Oskari-frontend:

  *   Map layers can now have tools that can be triggered for features on the layer. This will be used on myfeatures so the user can start editing a feature owned by them by just clicking the feature on the map (and edit button from the "GetFeatureInfo" popup) or directly from the feature data table UI. The content-editor functionality could also be updated to use the same tooling in the future and it's a new hook/plugin point for you to use in whatever way it makes sense on your application.
  *   Importing datasets (currently userlayers, when enabled myfeatures) now supports GeoJSON-format. Users have been able to download myplaces-features as GeoJSON and now they can be reimported as userlayers. It might not make sense to do so, but it does make sense that we can import in a format that we use for exporting data.
  *   Fixes an issue for numeric values on feature properties when editing them with content-editor functionality
  *   Fixed an issue when reading a paginated results from OGC API Features services.
  *   Touch events on vector features now use hitTolerance for FeatureEvents as well (features added at runtime etc) so it's easier to select a vector feature using a touch screen than before.

The compiled list of release notes can be found on  https://oskari.org/documentation/docs/3.3.0/12-Changelog

Note that we have also added some usage instructions for administrators on how to manage the map layers in Oskari: https://oskari.org/documentation/docs/3.3.0/9-Usage-instructions#Map-layer-administration

Current thoughts on upcoming versions/roadmap:

3.4: myfeatures production ready, opt-in on migrating applications from myplaces and userlayers to myfeatures
4.0: forced migration to myfeatures, removal of myplaces and userlayers. Spring 6 -> 7 version and related Tomcat 10 -> 11 migration. On frontend side: hopefully a new API/React implementation of the main navigation and flyout UI and/or containers for map plugins to be migrated from jQuery to React.


Happy updating,
    Sami
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/oskari-user/attachments/20260410/5dac37e0/attachment-0001.htm>