Hajk 4 Release Candidate 2

[Hallbergs]

98 commits and changes across 198 files since the most recent stable release, 3.14.1 – here's Hajk 4! This packaged release was brought to you by @Hallbergs and @jacobwod, with contributions from multiple coders. Please see the list of commits for all contributors.

This is the first release on the 4.x branch. Enjoy!

For an overview of planned development, refer to the project's roadmap.

Hajk 4 represents a significant milestone for Hajk for two main reasons:

• Layer Switcher has been rewritten and seen crucial improvments, including filtering the layer's list.
• There's now one official Hajk backend and it's written in NodeJS (the .NET backend has become a community extensions, for those who for some reasons still are in need of it).

Hajk 4 is packed with new features, bug fixes, and security improvements. 🔒

Scroll down to find a comprehensive list of changes! 🚀

Release Candidate Reporting Period

We're looking forward for your the results of your tests with this release candidate. Please use the dedicated discussions thread and report your findings. We're accepting test reports until April 2nd, 2025.

Changes since Hajk 4 Release Candidate 1

Several bugs have been identified (see the dedicated discussions thread for RC1) and fixed in RC2. For a list of changes between RC1 and RC2, please refer to CHANGELOG.md.

Breaking changes

• Dropped official support for the .NET backend.

Changelog highlights

For a comprehensive list of commits, please visit this link.

Added

• Major LayerSwitcher improvements and new features (see below for details)
• Measurer: It is now possible to measure segments in lines and polygons. #1549
• LayerComparer: It is now possible for to select specific layers (in Admin) that will be visible in the tool. Previously only all background layer and/or all regular layers could be selected. #1570
• Search: Added possibility to set default search options via admin UI. PR: #1496

Major LayerSwitcher changes

• 🚀 Added filter functionality
• Enhanced layer visibility indicators
• Quick Access grouping in LayerSwitcher for access to frequently used layers. Includes support for saving and restoring sets of "Quick Access layers" to LocalStorage.
• Quick Access Layer Presets/Themes/Packages. Choose from ready made sets of Layers to load into the Quick Access section. The Presets/Themes Packages are set up in the map config. See example in simpleMapConfig.json.
• Improved Draw Order tab functionality for managing layer drawing order

For further details, see the following issues: #1237, #1275, #1284, #1296, #1300, #1347, #1365, #1380.

Fixed

• Improved how overlapping windows are handled. PR: #1546
• Several accessability improvements. PRs: #1561, #1562, #1563, #1565, #1566, #1567, #1569
• Admin: Fixed issue with naming of the FME Server configuration property (commit

Security

• Updates across the board to dependencies

Changed

Removed

• In accordance with the roadmap the .NET backend was removed in the 4.0 release. (commit)

New Contributors

• @karljakoblarsson made their first contribution in LayerSwitcher: New take on Filtering, QuickAccess, QuickAccessPresets and DrawOrder improvements #1568
• @michaelsund made their first contribution in Measurement segments #1549
• @sweco-semtsg made their first contribution in Add alt text to logo #1561

Downloads

There are multiple ways to get the latest Hajk up and running, including Docker container.

Pre-compiled releases

There are two different versions of the pre-compiled solution: the regular (NodeJS edition) and a simple edition. The main difference is that the simple edition does not contain a Backend nor an Admin (it's just some static files that read all required configuration from a bunch of JSON files). The regular (NodeJS edition) contains all three Hajk components: the Backend, the Frontend and the Admin.

1. Hajk 4.0 NodeJS edition
2. Hajk 4.0 Simple edition

Docker container

The container is available on Docker Hub: https://hub.docker.com/r/hallbergs/hajk

Installation

Refer to our installation guide.

Full Changelog: v3.14.1...v4.0.0-rc.2

---

This discussion was created from the release Hajk 4 Release Candidate 2.

[OlofSvahnVbg]

The expand button in search window...

... does not make search window come to the top as shown here:

Inspelning.2025-03-26.094835.mp4

[OlofSvahnVbg]

Same issue with

button

[jesade-vbg]

Fix on the way.

[jesade-vbg]

Fixed in d96bda0

[optimalt]

Excellent job on the new layer switcher!
I have one question:
It seems that with v4 the legend image is now one more click away and harder to find compared to v3, or is this somehow configurable?
If not, it's unfortunate because for many types of data, the legend is probably the easiest way for the end user to understand what they are looking at.

[karljakoblarsson]

Thats a good suggestion! The current design is based on a sketch by Göteborg Stad, who also sponsored the work on the new LayerSwitcher. That's why it's done this way now. I we should have a new discussion with more stakeholders to find a design that is even better. I think there is a lot of room for improvement, especially in the "Layer details"-screen shown here. And personally I agree with you that the legend image should be shown by default.

However I will argue that this is a change for version 4.1 and not the current release. This current stage is mostly for bug fixes.

[optimalt]

Ok, thank you for the explanation.
Yes, sorry it's probably more of an addition maybe suitable for a later version than a bug fix :-)
As a workaround I made the legend always visible with html/markdown like this:

[maan002]

There are now two buttons by default that turn off all layers in the web map. One button (the control button) has a tooltip that says "hide all active layers", the other button (found under the more buttons in the layer manager) is called "turn off all layers". For the sake of clarity - should the names/tooltips of these buttons be the same?

[Hallbergs]

#1632 is merged and should fix it!

[maan002]

Some map links ("Kartlänkar") in the Document Manager ("Dokumentahanteraren") cause Hajk to stop working and you have to close the tab and start a new instance.

One map link may work in one zoom level but not in another.

[Hallbergs]

Hmm. Do you have an example of a link that causes hang? I would guess it is related to the OL animate bug where integers cause hang...

[maan002]

Testa https://hajk-lab-5.sbk.goteborg.se/

Om man klickar på kartlänken "Markanvändningskarta" i menyn till vänster direkt vid uppstart så fungerar den.

Laddar man om sidan och zoomar in två steg ( till 1:50 000) och därefter klickar på kartlänken "Markanvändningskarta" i menyn till vänster så slutar sidan att fungera och man måste stänga ner fliken och starta applikationen på nytt.

[Hallbergs]

The animate method is the culprit. Fix incoming.

[Hallbergs]

Should be fixed in 1ab25f0

Also tried bumping OL to 10.5.0 but the issue still persisted. The fix is not pretty but should get the job done for now.

[maan002]

Nice!

[maan002]

The wrong number of heading levels is displayed in the printout from the document manager in the client. In admin, the number of heading levels has been set to 2. The printout instead shows about 4 heading levels.

[Hallbergs]

If i remember correctly this cannot be reproduced when using the standard config (using the example documents, you get as many heading levels as you would expect).

Some organization has made altercations (setting "levels to show" to let's say 4 even if they want to show 3) so that the wrong behaviour works for them, therefore fixing this bug now would create problems for other organizations.

I think we should look into this more deeply and fix it after the 4.0 release. I've recently been told that the bug has been present before the 4.0 release.

[maan002]

It would have been nice if you could change the number of characters in Admin that are required before a search is performed in the layer manager ("Lagerhanteraren").
The client uses the setting "layerFilterMinLength", but you cannot change this in Admin.

[Hallbergs]

I missed the code meeting yesterday, but i think it was decided that this fix will be implemented after the release.

[maan002]

Yes, Gothenburg will implement this after the release of Hajk 4