Add geometry_type to layer definition
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 296
- Forks
- 51
- PR merge metrics
- No merged PRs in 30d
Description
Some renderers (like ours) require to map a geometry type to a layer. Therefore I propose to have an optional field "geometry_type" for the layer definition. The geometry_type should relate to one of the simple feature types of defined in GeoJson [1]:
> ... geometry type refers to seven case-sensitive strings: "Point", "MultiPoint", "LineString", "MultiLineString", "Polygon", "MultiPolygon", and "GeometryCollection"
[1] https://tools.ietf.org/html/rfc7946#section-1.4
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No file, test, or entry point is named in the issue. Start by locating the layer definition and its specification checks, then confirm that the optional field accepts the seven case-sensitive GeoJSON geometry strings and that the documented definition reflects the change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100