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

Consolidate depth coordinate methods #143

Merged
merged 4 commits into from
Jul 8, 2024

Conversation

mx-moth
Copy link
Contributor

@mx-moth mx-moth commented Jul 8, 2024

As per #140, there are far too many methods that deal with depth coordinates. Since #142 it is possible to use either a variable or its name interchangeably in most methods, making one of Convention.depth_coordinate or Convention.get_depth_name() et al superfluous. This PR drops Convention.get_depth_name() and similar methods in preference of using the coordinate variables directly.

Closes #138, #140

@mx-moth mx-moth self-assigned this Jul 8, 2024
@mx-moth mx-moth force-pushed the task/140-consolidate-depth-coordinates branch from 08d5232 to fec56a9 Compare July 8, 2024 04:25
mx-moth added 4 commits July 8, 2024 14:30
`Convention.depth_coordinate` and `Convention.depth_coordinates` are
better suited to the job when used in conjunction with
`utils.data_array_to_name` and `utils.name_to_data_array`.
@mx-moth mx-moth force-pushed the task/140-consolidate-depth-coordinates branch from fec56a9 to 80e0128 Compare July 8, 2024 04:34
@mx-moth mx-moth merged commit 628f441 into main Jul 8, 2024
15 checks passed
@mx-moth mx-moth deleted the task/140-consolidate-depth-coordinates branch July 8, 2024 04:43
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.

Incorrect depth coordinate in UGrid dataset
1 participant