[Places][2026-07-22.0] About 40% of websites values for Türkiye do not respond; a reachability signal would help
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 48/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 领域
- data
调研方向
首先定位 Places pipeline 以及 websites 字段的 schema 定义，然后检查 release 2026-07-22.0 如何生成它。将提议的可达性表示方式与报告中的土耳其案例进行比较，并确定项目可以支持哪些方式；当 consumers 无需重新爬取即可区分已列出的 websites 和可访问的 websites 时，即视为完成。
由索引模型根据 Issue 内容生成。
描述
Summary
Of the Türkiye places that carry a websites value, roughly two in five do not answer an HTTP request. There is nothing in the record that lets a consumer tell a listed website from a working one, so any adoption or digital-presence figure built on the field overstates by about a third. Adding a last-checked timestamp or a reachability flag to the websites entries, or dropping values that have failed for several releases, would fix that at the source.
Release and scope
- Release:
2026-07-22.0, themeplaces, typeplace, Türkiye (bbox25.5..45.0,35.7..42.3,addresses[1].country = 'TR',names.primary IS NOT NULL,operating_statusnotclosed) - 1,786,700 records in scope, 684,496 with a non-empty
websitesvalue (38.3%)
What we measured
We requested the first websites value of every one of those 684,496 records once, in September 2026, from a host in Türkiye:
GETon the URL as listed (https://prefixed if no scheme), redirects followed (max 5), 12 s timeout, identifiable user agent, headers read only, one request per site, no retries.- Counted as reachable: a 2xx response.
- Counted as unreachable: connection or DNS failure, timeout, or a non-2xx status.
Result: 413,777 reachable (60.5%), 270,719 unreachable (39.5%). So the share of Turkish places with a working website is 23.2%, not the 38.3% the field suggests.
Caveats: a single attempt on a single day will misclassify some sites that were briefly down or that block non-browser clients, so the true unreachable share is somewhat lower than 39.5%. It is not close to zero: the pattern by province and sector is stable and the bulk are parked domains, expired hosting and DNS that no longer resolves.
Breakdown
Per-province and per-sector counts (listed vs reachable) are published as CSV/JSON under CC BY 4.0, with the SQL that produced them:
- https://pinlyx.com/research/turkey-business-digital-report
- DOI: https://doi.org/10.5281/zenodo.22217770
We can share the per-record list (GERS id, URL as listed, failure class) if it is useful for the Places pipeline; it is ~270k rows.
Suggestion
Any of these would let consumers stop re-crawling:
- a
last_verified(or similar) timestamp perwebsitesentry, - a boolean or status alongside the URL when the pipeline already checks liveness,
- or removal of URLs that have failed across consecutive releases.
Related: #570 (the addresses[].region field for the same extract).
- 主要语言
- Python
- 星标
- 1.2k
- 派生
- 48
- 平均合并
- 10 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
OvertureMaps/data 的其他 Issue
-
external
难度 2/5 1-3 小时 新手友好度 70/100
OvertureMaps/data#509 ·
-
external
难度 4/5 3-5 天 新手友好度 49/100
OvertureMaps/data#585 ·
-
external
难度 4/5 3-5 天 新手友好度 22/100
OvertureMaps/data#583 ·
-
data-sources external
难度 5/5 一周以上 新手友好度 35/100
OvertureMaps/data#581 ·
-
bug external
难度 4/5 3-5 天 新手友好度 48/100
OvertureMaps/data#580 · 1 条评论 ·
查看 OvertureMaps/data 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement good first issue
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
iceboundrock/AutoForge#304 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
fossasia/visdom-dev#77 ·
维护者通常 4 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
aws-cloudformation/cfn-lint#4890 ·
维护者通常 2 天内回复