Different recognized coordinates when calling variable by standard name
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
Research direction
No file, test, or entry point is named. Start by reducing the two reported access expressions to a minimal dataset that reproduces the difference, then trace how cf-xarray resolves coordinates for a variable name versus its standard name. Done means both access paths consistently recognize the longitude coordinate, with a regression test covering the case.
Written by the indexing model from the issue text.
Description
I know this isn't good form, but I am going to describe my problem to see if anyone has an idea of a direction to go, without a good example to start. I am using several libraries together and making an example case seems difficult.
Here is the base question though:
ds['zeta'].cf['longitude'] worked but ds.cf['sea_surface_height_above_mean_sea_level'].cf['longitude'] did not
in other words, when I used the variable name to access a variable in my dataset, cf-xarray knew the mapping for longitude. But, when I referred to the variable by its standard name that cf-xarray recognized, cf-xarray did not then know the mapping for longitude. This seems weird right? Any ideas of what could be wrong?
- Dominant language
- Python
- Stars
- 181
- Forks
- 49
- Avg merge
- 43m
- Merged PRs (30d)
- 1
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from xarray-contrib/cf-xarray
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
xarray-contrib/cf-xarray#623 ·
-
Consider adding opt-in support for circular axes when calling `bounds_to_vertices` (related to #594) Open
Difficulty 5/5 Over a week Newbie friendliness 38/100
xarray-contrib/cf-xarray#596 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 25/100
xarray-contrib/cf-xarray#570 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 15/100
xarray-contrib/cf-xarray#568 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
xarray-contrib/cf-xarray#566 · 2 comments ·
All issues in xarray-contrib/cf-xarray
Similar issues
-
area/auth bug comp/agent P3 platform/discord type/security
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
NousResearch/hermes-agent#117848 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100