Release 2024.4.1

[josephbirkner]

• Introduce a performance diagnostics dialog which may be opened via Ctrl+X
• Fix occasional hanging updates by using mapget's new clientId instead of an HTTP abort.
  • Introduced in this mapget PR: Release 2024.4.1 mapget#79
• Fix the visualization limit, which was blatantly ignored.

TODO:

• Show number of aggregated tiles
• Allow any integer/number tile info field to be viewed as a statistic.
• Update statistics automatically (it should not be necessary to click "update").
• Allow viewing render performance separately per style sheet and respective "hover"/"selection" modes.
• Add a Button to open the dialog.
• Do not generate hover highlights while the map is being dragged around.
• Switch to synchronous geometry for tile borders as well.
• Do not prematurely re-encode tiles when only a single one is rendered.
• Statistics "Sum" column.

Closes #162

[josephbirkner]

Future TODOs (partially in other repos):

• Add NDS.Live SmartLayer and DataLayer size and add network fetching wall-time statistics.
• Ensure that region rule layers are not redundantly stored.
• Implement two-stage loading: most fat attribute layers are only needed for search/inspection, but not for visualization.
• Have some way of telling which parts of a TileFeatureLayer are occupying space.
• Add some kind of loading progress visualization:
  • % of stage 1 layers received
  • % of stage 2 (add-on) layers received
  • % of finished tile visualizations

[MisterGC]

Some improvements for the Viewport Statistics Dialog

• Use floats only when it is applicable, otherwise int (e.g. number of features)
• Add a tool tip to each entry so that users clearly know what the numbers indicate
• Improve the labels - e.g. why do the render times for styles always contain -normal-, e.g. Number of Features instead of always the technical/tracking keyword
• Would be quite useful to see which tilelayer caused a specific peak value - this would be quite helpful for detailed investigation

[MisterGC]

Speed boost achieved! This PR is a significant step forward. Approved!

Although the improvements of the Viewport Statistics would help - I have compared cases which still cause performance problems - the peak sizes of the tiles where like 10x higher than ones in areas/viewports/maps (2 vs 20MB)

Done