Geospatial formats: Shapefile / GeoJSON / KML / GPX conversion and GeoTIFF band split
维护者通常 1 天内回复
@KnifeLemon 已经在做这个了。
开始于 2026年10月19日。
评估
这个 Issue 还没有评估数据。
描述
What would you like Filee to do?
Convert common geospatial (GIS) files, in two steps that can ship as separate pull requests:
- Vector data: Shapefile (
.shpwith its.dbf/.prj, or a.zipof them), GeoJSON, KML / KMZ, GPX and CSV (lat/lon columns or WKT) converting to each other. A Shapefile can also be split into several files, for example one output per value of an attribute column. - Rasters: read GeoTIFF (including 16-bit and float bands), save a multi-band raster as one file per band (
name_b1.tif,name_b2.tif, …) and the reverse (stack bands), and save a colour-mapped PNG preview.
Why / when would you use it?
I work in geospatial analysis, where these files are exchanged all day, and the usual way to convert them is a large GIS program or a command-line tool. "Drag a Shapefile onto GeoJSON" or "drag a satellite image onto separate bands" fits Filee well. Because of the route planner it would also unlock chains for free, e.g. Shapefile → CSV → XLSX / JSON.
Ideas for how it could work
I'd like to build this myself, following docs/ADDING-A-CONVERTER.md, and I'd rather agree on the shape with you first:
- In-process C# only, like the 3D models and data engines: no GDAL/QGIS and nothing from
PATH. For the vector side I'm considering NetTopologySuite (BSD-3) with its Esri Shapefile and GeoJSON readers, plus small hand-written KML / GPX readers and writers; I'll check each library's license and list it inTHIRD-PARTY-NOTICES.md. Tell me if you prefer fewer dependencies and hand-written readers. - Rasters need their own TIFF reader. The ImageMagick Q8 build is 8-bit, so a 16-bit or float elevation or satellite band would be clipped. I'd read the TIFF and its GeoTIFF tags directly (or with a small managed TIFF library) and keep the georeferencing in the per-band outputs.
- One new format category (for example
Geo) with its own donut toolbar profile, so geo files don't mix into Data. Is that fine, or would you rather file them underData/Cad/Imageto keep the UI changes small? - Options such as "split by attribute" or the band choice would need preset options and a settings migration. I would start without options (one fixed behaviour per preset) and add them in a later PR.
- Tests use files generated in the test (as the other engine tests do), plus a few tiny hand-made samples; every new UI string goes into all
i18n/*.jsonfiles.
Planned pull requests, each small and independent:
- GeoJSON ↔ KML / KMZ ↔ GPX ↔ CSV
- Shapefile read/write (+ split by attribute)
- GeoTIFF reading, PNG preview
- Band separation and stacking
Does this direction sound right to you, and is there anything you'd change before I start? If a geospatial engine is out of scope for Filee, I'd rather know now.
- 主要语言
- C#
- 星标
- 3.6k
- 派生
- 192
- 平均合并
- 4 小时 6 分钟
- 30 天内合并 PR
- 158
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
KnifeLemon/Filee 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 65/100
KnifeLemon/Filee#363 ·
维护者通常 1 天内回复
-
enhancement
难度 5/5 一周以上 新手友好度 35/100
KnifeLemon/Filee#362 ·
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 1/100
KnifeLemon/Filee#361 ·
维护者通常 1 天内回复
-
bug
难度 3/5 1-2 天 新手友好度 25/100
KnifeLemon/Filee#358 ·
维护者通常 1 天内回复
-
bug
难度 5/5 一周以上 新手友好度 38/100
KnifeLemon/Filee#356 ·
维护者通常 1 天内回复
相似的 Issue
-
area: client bug
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
bug mcp misleading small
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复
-
Bug Platform: Android
难度 2/5 1-3 小时 新手友好度 78/100
getsentry/sentry-dotnet#5764 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
microsoft/SimpleL7Proxy#287 ·
维护者通常 1 天内回复