mapbox / mapbox/vector-tile-spec
Support GeometryCollection?
Open
Nobody has claimed this yet.
3.0 Specification
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
For feature parity with GeoJSON; otherwise it is probably more trouble than it is worth.
It would be a new `GeomType` with a corresponding new `geometry`-like message which contains an array of messages with a `GeomType` and a `geometry` (any of which could also be a nested GeometryCollection).
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
Start by reading the existing GeomType and geometry message definitions in the vector-tile specification. Determine how a new GeometryCollection type would represent an array of typed geometry messages, including nested collections; done means the specification clearly describes that structure and its GeoJSON parity.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100