Convert between GeoJSON and WKT
Nobody has claimed this yet.
- Dominant language
- Swift
- Stars
- 271
- Forks
- 65
- PR merge metrics
- No merged PRs in 30d
Description
This library’s GeoJSON types should have initializers that take WKT-formatted strings and properties that return WKT-formatted strings. This format is more compact than GeoJSON but more expressive than the Encoded Polyline format, supporting the full Simple Features specification, making it ideal for URL query parameters.
The Turf.js project declined to support WKT conversion in Turfjs/turf#2057. However, this library has a slightly different scope, given that it defines its own types for in-memory representations of GeoJSON, something the JavaScript library inherently has no need for. The WKT format isn’t terribly complex, but we can port the wellknown library as a starting point.
/cc @Guardiola31337
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 reviewing the library’s GeoJSON types and the proposed wellknown library as a parser reference. Define the initializer and property behavior for WKT conversion, including the full Simple Features specification, and verify that the resulting strings support URL query parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100