Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file AIP-66 #889

Merged
merged 3 commits into from
Apr 16, 2024

Conversation

linz-li-bot
Copy link
Collaborator

No description provided.

Copy link
Contributor

Individual Inserts

hawkes-bay-2023-2024-0.125m

hawkes-bay-2023-2024-0.125m

Individual Updates

hawkes-bay-2023-2024-0.125m

Copy link
Contributor

Individual Inserts

hawkes-bay-2023-2024-0.125m

hawkes-bay-2023-2024-0.125m

Individual Updates

hawkes-bay-2023-2024-0.125m

Copy link
Contributor

Individual Inserts

hawkes-bay-2023-2024-0.125m

hawkes-bay-2023-2024-0.125m

Individual Updates

hawkes-bay-2023-2024-0.125m

@blacha blacha changed the title config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file. config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file AIP-66 Apr 15, 2024
@blacha blacha changed the title config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file AIP-66 config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file AIP-67 Apr 15, 2024
@blacha blacha changed the title config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file AIP-67 config(raster): Add imagery hawkes-bay-2023-2024-0.125m to aerial config file AIP-66 Apr 15, 2024
@blacha blacha added this pull request to the merge queue Apr 16, 2024
Merged via the queue into master with commit 40e7c9e Apr 16, 2024
6 checks passed
@blacha blacha deleted the feat/bot-config-raster-hawkes-bay-2023-2024-0.125m branch April 16, 2024 00:01
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.

3 participants