Skip to content

Conversation

@sadielbartholomew
Copy link
Member

Close #366 by setting up discussed data structure to close #365, reporting invalid standard names in the new output structure, as indicated in #365 (comment).

Opening as a draft since it's my last working day before the Christmas break but I have a few issues left to iron out (I only realised today a few bad standard names weren't being reported and yet to diagnose the reason why - annoying timing but I need to call it a day at some point!). In Jan when I am back to work I will finalise and add some notes to aid reviewing here.

@sadielbartholomew sadielbartholomew self-assigned this Dec 19, 2025
@sadielbartholomew sadielbartholomew added enhancement New feature or request UGRID Relating to UGRID mesh topologies conformance labels Dec 19, 2025
@sadielbartholomew sadielbartholomew changed the title Recast dataset_compliance output with POC of standard names validation Redesigned dataset_compliance w/ POC of standard names validation Dec 19, 2025
@sadielbartholomew sadielbartholomew changed the title Redesigned dataset_compliance w/ POC of standard names validation Redesigned dataset_compliance w/ standard names validation Dec 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

conformance enhancement New feature or request UGRID Relating to UGRID mesh topologies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Compliance reporting: flag any invalid standard names Output for Field.dataset_compliance towards a CF Checker

1 participant