test: add declination table to map layout BM-1636#30
Draft
tawera-manaena wants to merge 1 commit into
Draft
Conversation
tawera-manaena
changed the title
This file contains hidden or 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
1 participant
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.
This piece of work closely relates to this pull request.
Motivation
The magnetic declination panel tells map users the difference between grid north and magnetic north for this map sheet, including the rate of change over time. This is critical information for users navigating with a compass. Replicating this in QGIS ensures the panel is dynamically generated from accurate, location-specific data rather than manually authored, reducing the risk of error and the burden on cartographers.
Modifications
map-series/nztopo50/
nztopo50.qgsI've appended the set of project-scope variables required to generate the magnetic declination component. For a given map sheet, the intent is to inject each variable's value code-side, and then consume it in the map layout at runtime.
I've added a table component to the map layout so that each new variable's value is visible.
Verification
I attempted to run a Map Production workflow (Argo). However, I ran into an issue.