Add support for ndgeojson / GeoJSONSeq / GeoJSON Text Sequences
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 12.4k
- Forks
- 2.4k
- PR merge metrics
- No merged PRs in 30d
Description
## Motivation
I'm thinking if we should support sequential GeoJSON https://gdal.org/drivers/vector/geojsonseq.html, new line delimited GeoJSON https://stevage.github.io/ndgeojson/ and GeoJSON Text Sequences https://tools.ietf.org/html/rfc8142 out of the box, transparently with the `geojson` source.
## Design Alternatives
Don't support this out of the box and instead rely on a custom source api #2920 and plugin to implement.
## Design
I'm proposing to support sequential geojson transparently though auto-detection so no API changes are needed.
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 with the existing `geojson` source and the custom source API discussion in #2920, then compare the proposed behavior with the GDAL, ndgeojson, and RFC 8142 references. Done means sequential GeoJSON, newline-delimited GeoJSON, and GeoJSON Text Sequences are transparently recognized through the existing `geojson` source without API changes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100