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

feat: add multiple STAC licensors TDE-643 #355

Merged
merged 1 commit into from
Feb 15, 2023

Conversation

paulfouquet
Copy link
Collaborator

@paulfouquet paulfouquet commented Feb 15, 2023

Description

Data Managers need to add several licensors in some rare cases.

Changes

  • collection_from_items.py takes a new optional argument --licensor-list and expect a string representing a list separated by semicolon ; (example: Waka Kotahi; Nelson City Council; Tasman District Council). This argument is used if there is more than 1 element in the list. Otherwise, --licensor is used.
  • quick refactor moving /scripts/test/ to /scripts/cli/tests as it was related to /cli only.

Test

https://argo.linzaccess.com/workflows/argo/test-imagery-standardising-multilicensors-wxvt7?tab=workflow&nodeId=test-imagery-standardising-multilicensors-wxvt7-3822207485
"providers": [{"name": "Auckland", "roles": ["licensor"]}, {"name": "Nelson Council", "roles": ["licensor"]}, {"name": "LINZ", "roles": ["licensor"]}, {"name": "Unknown", "roles": ["producer"]}, {"name": "Toitū Te Whenua Land Information New Zealand", "roles": ["host", "processor"]}]

NOTE: linz/topo-workflows#101 to allow Argo users to pass this new argument.

Copy link
Contributor

@MDavidson17 MDavidson17 left a comment

Choose a reason for hiding this comment

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

Looks great, thanks!

@kodiakhq kodiakhq bot merged commit 001b9fc into master Feb 15, 2023
@kodiakhq kodiakhq bot deleted the feat/add-multiple-stac-licensors-tde-643 branch February 15, 2023 22:31
@github-actions github-actions bot mentioned this pull request Feb 15, 2023
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