Virtual point clouds overview in 2D

[Withalion]

Description

This PR changes the default behaviour of VPC rendering. We switch from rendering extents when zoomed out to rendering overview when it's present. This change adds seamless transition between overview into specific point clouds. Furthermore the user is able to switch between just extents, just overview and extents rendered over overview, by using combo box in layer styling side panel.

Screencast_20241212_142233.mp4

The label settings were also moved together with zoom out behaviour settings into new Virtual point cloud options QgsCollapsibleGroupBox. Which is visible only when dealing with virtual point clouds styling.

Note: When I dealt with setting the default Qgis::PointCloudZoomOutBehavior for layer renderer I noticed that the renderer is actually created multiple times!

• First time the renderer gets created in QgsPointCloudLayer::setDataSourcePrivate, which is called by constructor
  

  QGIS/src/core/pointcloud/qgspointcloudlayer.cpp

  Lines 467 to 487 in fb501d5

  	if ( loadDefaultStyleFlag && isSpatial() && mDataProvider->capabilities() & QgsPointCloudDataProvider::CreateRenderer )
  	{
  	// first try to create a renderer directly from the data provider
  	std::unique_ptr< QgsPointCloudRenderer > defaultRenderer( mDataProvider->createRenderer() );
  	if ( defaultRenderer )
  	{
  	defaultLoadedFlag = true;
  	setRenderer( defaultRenderer.release() );
  	}
  	}
  	if ( !defaultLoadedFlag && loadDefaultStyleFlag )
  	{
  	loadDefaultStyle( defaultLoadedFlag );
  	}
  	if ( !defaultLoadedFlag )
  	{
  	// all else failed, create default renderer
  	setRenderer( QgsPointCloudRendererRegistry::defaultRenderer( this ) );
  	}

• Second time the renderer is created by QgsAppLayerHandling::postProcessAddedLayer
  

  QGIS/src/app/layers/qgsapplayerhandling.cpp

  Line 187 in fb501d5

  layer->loadDefaultStyle( ok );

Note 2: The layer has to be readded into the project for qgis to apply the default behaviour.

Funded by: Klimadatastyrelsen

[github-actions]

🪟 Windows builds

Download Windows builds of this PR for testing.
Debug symbols for this build are available here.
(Built from commit db141fe)

🪟 Windows Qt6 builds

Download Windows Qt6 builds of this PR for testing.
(Built from commit db141fe)

[uclaros]

Nice!
I have an objection on the need for those averageSubIndexWidth and averageSubIndexHeight methods, though.

[nyalldawson]

This will need some unit tests added too 👍

[qgis-bot]

@Withalion

This pull request has been tagged for the changelog.

• The description will be harvested so please provide a "nearly-ready" text for the final changelog
• If possible, add a nice illustration of the feature. Only the first one in the description will be harvested (GIF accepted as well)
• If you can, it's better to give credits to your sponsor, see below for different formats.

You can edit the description.

Format available for credits

• Funded by NAME
• Funded by URL
• Funded by NAME URL
• Sponsored by NAME
• Sponsored by URL
• Sponsored by NAME URL

Thank you!

[qgis-bot]

@Withalion
This pull request has been tagged as requiring documentation.

A documentation ticket will be opened at https://github.com/qgis/QGIS-Documentation when this PR is merged.

Please update the description (not the comments) with helpful description and screenshot to help the work from documentors.
Also, any commit having [needs-doc] or [Needs Documentation] in will see its message pushed to the issue, so please be as verbose as you can.

Thank you!

[github-actions]

The QGIS project highly values your contribution and would love to see this work merged! Unfortunately this PR has not had any activity in the last 14 days and is being automatically marked as "stale". If you think this pull request should be merged, please check

• that all unit tests are passing

• that all comments by reviewers have been addressed

• that there is enough information for reviewers, in particular

  • link to any issues which this pull request fixes

  • add a description of workflows which this pull request fixes

  • add screenshots if applicable

• that you have written unit tests where possible
  In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this pull request.
  If there is no further activity on this pull request, it will be closed in a week.