Which CoverageJSON fragments would make good "building blocks" for re-use
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- json
调研方向
首先阅读 opengeospatial/bblocks 仓库中链接的 OGC building-block register 示例和 register.json。然后确定符合所述 building-block 类别的 CoverageJSON 片段，并记录一份具体提案。提案已记录，并且在获得接受后以包含所需注册条目的 pull request 提交，即表示完成。
由索引模型根据 Issue 内容生成。
描述
OGC has a policy for re-usable "building blocks" at various levels of granularity to improve interoperability.
@chris-little and @jonblower agreed that a first proposal would be to register the parameter object in the OGC register of building blocks.
The building blocks are organised in these folders:
• geo: geospatial building blocks
• ogc-utils: Utility building blocks that are used in OGC API's but are not inherently geospatial. They were created to ensure consistency within OGC API's where there was not a clear mainstream standard, and in line with best practices of the web and could be replaced, e.g. by building blocks specified in an IETF RFC or similar, if and when available. API's built with the geo building blocks do not need to use these, but they provide a nice default option that OGC-focused tools will understand.
• unstable: These building blocks are not yet stable or mature. They may be extracted from core OGC API standards that have not yet been fully approved, or they may also be new ideas that are not yet in a standard.
Each building block is an AsciiDoc document, whose name follows the convention: PREFIX-NAME.adoc. The prefix is parameter, in the case of parameters, header in the case of headers, and encoding (e.g.: JSON) in the case of data types or resources. This is an example of a building block
In addition, please register the building block in the register.json
This provides information about the item, using an extension of the ISO19135 schema.
All contributions welcomed, as pull requests to this repository
- 主要语言
- HTML
- 星标
- 15
- 派生
- 9
- 平均合并
- 6 小时 1 分钟
- 30 天内合并 PR
- 3
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
opengeospatial/CoverageJSON 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 45/100
opengeospatial/CoverageJSON#233 ·
-
Implementations
难度 5/5 一周以上 新手友好度 25/100
opengeospatial/CoverageJSON#229 · 3 条评论 ·
-
难度 5/5 一周以上 新手友好度 25/100
opengeospatial/CoverageJSON#227 · 3 条评论 · 1 个 reaction ·
-
enhancement
难度 5/5 一周以上 新手友好度 30/100
opengeospatial/CoverageJSON#218 · 4 条评论 ·
-
V1.1
难度 5/5 一周以上 新手友好度 35/100
opengeospatial/CoverageJSON#216 · 9 条评论 · 3 个 reaction ·
查看 opengeospatial/CoverageJSON 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 90/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
MicrosoftLearning/PL-400_Microsoft-Power-Platform-Developer#231 ·
-
docs good first issue
难度 2/5 1-3 小时 新手友好度 78/100
VenetoStato/giorgio#6 ·
-
specification
难度 1/5 1 小时以内 新手友好度 85/100
WICG/webmonetization#754 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
linagora/twake-on-matrix#3446 ·
维护者通常 3 天内回复