Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

More lenient guess_coord_axis() rules?

未关闭
#464 3 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
停滞
技术栈
python
领域
data

调研方向

Start by reading the guess_coord_axis() implementation and its existing tests, focusing on the current name-matching rules and intentional exclusions described in the issue. This is currently a design discussion: completion requires a maintainer-agreed leniency approach, including how eta and xi should be handled, followed by behavior tests.

由索引模型根据 Issue 内容生成。

描述

Hi. I regularly find myself wishing guess_coord_axis() would find more dimension and coordinate names. I was just adding some to do a PR but I see that some are purposely excluded. For example I would like it to find "lat" when the variable name doesn't start with "lat" but it is just in the name somewhere. I see this was purposefully done because some people must have datasets that use "nlat" as a dimension to count their latitudes but want it to be "Y" not "latitude". Same with lon, time, and Z.

I also would like to add "eta" and "xi" to the guess regex for "Y" and "X" respectively to pick up dimensions in ROMS files. However, perhaps this would cause a problem for some users if they have other variable names with those names in them.

Would it make sense to have a flag for levels of leniency for guesses? Or for whether they have to be at the start of the variable name or not?

I can submit the code I have if this is too abstract to discuss. Thanks.

主要语言
Python
星标
181
派生
51
平均合并
6 小时 39 分钟
30 天内合并 PR
1

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

xarray-contrib/cf-xarray 的其他 Issue

查看 xarray-contrib/cf-xarray 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。