Investigate GeoJSON feature collection and multidimensional support for the location attribute
还没有人认领这个 Issue。
评估
调研方向
This is a spike, not an implementation: read how the location attribute is currently typed as GeoJSONPoint in the asset model and any existing GeoJSON handling. Answer the three listed questions (whether to expand location/area, feasibility of feature collections and 3D, and limits/resolution/aggregation of complex shapes) and record a decision plus direction. Done means the acceptance-criteria discussion is written up, not a code change.
由索引模型根据 Issue 内容生成。
描述
User Story
As a developer I want to investigate whether the location attribute (currently GeoJSONPoint) can be changed to fully support any GeoJSON shape, whether 3D shapes are possible and more space efficient alternative formats, so that we can make an informed decision on how to expand the location attribute and accommodate more shapes.
Description
Decide whether the location attribute should grow beyond GeoJSONPoint before anything is built on top of it.
The spike covers three questions:
- whether expanding the location or area attributes is wanted at all,
- whether the existing attribute can feasibly carry a collection of features and 3D shapes,
- and what large complex shapes imply.
The last one includes the resolution to store curves at, whether an asset may hold hundreds or thousands of features or needs a limit, and how the shapes of several assets (houses, streets) could combine into the area of a parent asset such as a city.
Outcome is a decision and a direction, not an implementation.
Acceptance Criteria
- 1. Discuss whether we want to expand the location (or area) attributes
- 2. Investigate the feasibility of expanding the existing location attribute
- To support a collection of features
- To support 3D shapes
- 3. Investigate the impact of larger complex shapes
- How to deal with curves? Namely the resolution of those?
- Should we allow an asset to be a shape with hundreds or thousands of features? Or should there be a limit?
- How could multiple assets e.g. multiple house-, street assets (and whatever else) be combined to form the area of e.g. city asset?
- 主要语言
- Java
- 星标
- 1.9k
- 派生
- 478
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
openremote/openremote 的其他 Issue
-
Infrastructure
难度 2/5 1-3 小时 新手友好度 68/100
openremote/openremote#3502 ·
-
Bug Gateways
难度 2/5 1-3 小时 新手友好度 72/100
openremote/openremote#3457 · 1 条评论 ·
-
Bug
难度 2/5 1-3 小时 新手友好度 72/100
openremote/openremote#3439 ·
-
Bug
难度 2/5 1-3 小时 新手友好度 65/100
openremote/openremote#3438 ·
-
难度 2/5 1-3 小时 新手友好度 64/100
openremote/openremote#3278 · 3 条评论 ·
查看 openremote/openremote 的全部 Issue
相似的 Issue
-
[BUG] micronaut-serde-oracle-jdbc-json brings a second OJDBC driver onto the runtime classpath可能已有人在做 @ZARAYACH 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
micronaut-projects/micronaut-serialization#1494 · 4 条评论 ·
维护者通常 2 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 73/100
维护者通常 2 天内回复
-
code-health feature/sync OS/Android QA/Test-Plan-Specified QA/Yes
难度 2/5 1-3 小时 新手友好度 75/100
brave/brave-browser#60327 ·
维护者通常 1 天内回复
-
Type: Bug
难度 2/5 1-3 小时 新手友好度 65/100
it-at-m/raumreservierung#383 ·
维护者通常 3 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
aws/context-ontology-accelerator#325 ·
维护者通常 1 天内回复