mapbox / mapbox/vector-tile-spec
Adopt explicit MultiPoint, MultiLineString, and MultiPolygon types
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1k
- Forks
- 213
- PR merge metrics
- No merged PRs in 30d
Description
This is the "change for a future release" tail of https://github.com/mapbox/vector-tile-spec/issues/30.
Currently, it's not possible to encode a MultiPoint geometry with a single point in a way that is distinguishable from a Point geometry. Thus VTs cannot round-trip GeoJSON or other formats in which a singleton MultiPoint is valid. The same is true for singleton MultiLineString and MultiPolygon.
If the spec adopted explicit MultiPoint, MultiLineString, and MultiPolygon types, it would resolve this compatibility issue.
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 vector-tile-spec issue and the linked issue 30 to understand the proposed future-release change and the singleton geometry compatibility problem. No implementation files or tests are mentioned, so define the specification requirements for explicit MultiPoint, MultiLineString, and MultiPolygon types and document how the change enables GeoJSON round-tripping.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 20/100