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

Inconsistent classification and inclusion of maritime vs land boundaries

未关闭
  • 哪里不对？
#560 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
data

调研方向

首先使用 Hudson River、Riker’s Island、Great Lakes 和 New Jersey 的示例，追踪 Division 边界的来源方式以及 maritime/land 类别的分配方式。将生成的边界与链接的 OSM ways 进行比较，并检查当前的 boundary schema。分类和纳入规则得到解释，并且已处理报告中的不一致或 schema 缺口，即表示完成。

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

描述

external

Below I've rendered the class=maritime boundaries in red and all others (currently always maritime) in blue.

Image

Can we get some insight on how these classes are assigned? Parts of the Hudson River are classified as maritime and another part are classified as land.

Image

Areas like Riker's Island have an insane level of granularity splitting up a the line! It's like there was a pixel detection classifier run over this.

At the moment, the classification seems to be more or less random, and the classifications are not supported by the OpenStreetMap source data. Here is the OSM Way for that Bronx / Queens border. It's a single way, and no tags on the way or any of the parent relations suggest a maritime border.

Meanwhile the Great Lakes are classified as land borders (this is consistent with OSM and how most maps want to render these, even if they don't render more typical ocean maritime borders). So I guess wrapped up in this is a schema question of whether 2 classes are enough.

I also noticed a bunch of external borders, like this one in NJ are missing from the Division boundaries. https://www.openstreetmap.org/way/309513136#map=11/39.0272/-74.7548&layers=N. Typical maritime boundaries like the this one (a way that is part of the US international border and the EEZ) are also omitted. (These also seem worth including with an expanded set of classes.)

主要语言
Python
星标
1.2k
派生
48
平均合并
10 分钟
30 天内合并 PR
2

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

OvertureMaps/data 的其他 Issue

查看 OvertureMaps/data 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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