You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: