Skip to content

Use var prefix list #103

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

Merged
merged 2 commits into from
Sep 6, 2022
Merged

Conversation

jyucsiro
Copy link
Contributor

@jyucsiro jyucsiro commented Jun 3, 2022

This PR provides a small change to include the netCDF variables in scanning for a prefix list (in addition to groups).

This is in line with Section 6.5.4
http://docs.opengeospatial.org/DRAFTS/19-002.html#_prefix_definition

"The attributes defining prefixes shall be in a separate netCDF group or variable, as attributes."

Test file: test.zip

@jyucsiro jyucsiro requested a review from marqh June 3, 2022 03:25
@marqh
Copy link
Member

marqh commented Jun 28, 2022

consider opengeospatial/netcdf-ld#115

is prefix variable a not-recommended approach?
is it shall-not?

should this be implemented?
is it useful backup behaviour for any use cases

@jyucsiro
Copy link
Contributor Author

jyucsiro commented Aug 9, 2022

A reason for not allowing encoding of prefixes in variables is that some netCDF client software treat variables as special selectors. After some thinking, I can't see an advantage of implementing it this way if we allow encoding of prefixes in globals as per opengeospatial/netcdf-ld#115 and #104

@marqh marqh merged commit ca59666 into binary-array-ld:master Sep 6, 2022
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