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

Migrate inspire schemas #116

Merged
merged 2 commits into from
Feb 6, 2025
Merged

Migrate inspire schemas #116

merged 2 commits into from
Feb 6, 2025

Conversation

JohannaOtt
Copy link
Member

SVC-1946

@JohannaOtt JohannaOtt requested a review from annat2022 February 5, 2025 12:52
Copy link
Member

@annat2022 annat2022 left a comment

Choose a reason for hiding this comment

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

LGTM

The INSPIRE schema update to version 5.0 had impacts on the base alignments
as well as the TN base alignments.
As there was no new versions for the TN-A and TN-C schemas, the JRC decided
to also keep the TN common schema version 4.0 for it.
That means that the migrated base alignments and TN base alignments now using
version 5.0 cannot longer be used for TN-A and TN-C.
Therefore, new 4.0 versions of these alignments were added and used in TN-A
and TN-C.

SVC-1946
According to changes done to INSPIRE HY-N schema in (first release 2025)[https://github.com/INSPIRE-MIF/application-schemas/releases/tag/2025.1]

SVC-1946
@JohannaOtt JohannaOtt force-pushed the migrate_INSPIRE_schemas branch from 9881673 to ac1bf36 Compare February 6, 2025 13:44
@JohannaOtt JohannaOtt merged commit 3524dff into master Feb 6, 2025
1 check passed
@JohannaOtt JohannaOtt deleted the migrate_INSPIRE_schemas branch February 6, 2025 13:47
Copy link

github-actions bot commented Feb 6, 2025

@wetransform/service Please make sure that the PostNAS alignments are adapted accordingly.

@JohannaOtt
Copy link
Member Author

JohannaOtt commented Feb 6, 2025

Please make sure that the PostNAS alignments are adapted accordingly.

There is SVC-1974 for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants