Skip to content

feat: use elevation capture areas for hillshade capture areas#1151

Merged
amfage merged 10 commits intomasterfrom
feat/use-elevation-capture-area-for-hillshades-tde-1839
Mar 24, 2026
Merged

feat: use elevation capture areas for hillshade capture areas#1151
amfage merged 10 commits intomasterfrom
feat/use-elevation-capture-area-for-hillshades-tde-1839

Conversation

@amfage
Copy link
Contributor

@amfage amfage commented Mar 11, 2026

📣 Co-ordinate merge with release linz/topo-imagery#1494

Motivation

Use the capture-area.geojson file of the upstream data source, which will be, or has been (change in progress) created from the national DEM/DSM capture-dates.geojson files.

Modifications

Do not create footprints when creating hillshades.
Use the supplied_capture_area parameter to provide a capture area from the upstream data source.
The exception to this are the merged DEM hillshades, which backfill from the 8m DEM and do not use the hillshade command. These will generate footprints as usual.

Note that if the 8m DEM needs to be recreated, create_capture_area will need to be set to true

Verification

Test workflows run.

@amfage amfage marked this pull request as ready for review March 23, 2026 22:33
@amfage amfage requested review from a team as code owners March 23, 2026 22:33
Copy link
Collaborator

@paulfouquet paulfouquet left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there any reason not changing create_capture_area to false for cron-national-merged-dem-hillshades, or is that forgotten? - I should have read the description :D

@amfage amfage added this pull request to the merge queue Mar 24, 2026
Merged via the queue into master with commit ae1320c Mar 24, 2026
5 checks passed
@amfage amfage deleted the feat/use-elevation-capture-area-for-hillshades-tde-1839 branch March 24, 2026 04:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants