[GUI] Show the CRS Epoch up to 3 decimal digits when needed and in more places #57725
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In the current implementation, the CRS Epoch value is displayed incorrectly rounded to 2 decimal digits (i.e. Epochs from 2024.246 to 2024.254 are all displayed as 2024.25). Anyway, 3 decimal digits are needed in order to have at least 1 day precision for the Epoch.
I've modified
QgsCoordinateReferenceSystem::userFriendlyIdentifier()andQgsMapLayer::crsHtmlMetadata()to useQStringLiteral( " @ %1" ).arg( qgsDoubleToString( epoch, 3 ) );instead of
QStringLiteral( " @ %1" ).arg( epoch );I've also added the Epoch value to the ToolTipRole of
QgsLayerTreeModel::data()and ofQgsMapLayerModel::data().I think it would be useful to backport this PR to 3.34.