Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Port turf-buffer #28

Open
1ec5 opened this issue Jan 12, 2018 · 3 comments
Open

Port turf-buffer #28

1ec5 opened this issue Jan 12, 2018 · 3 comments
Labels
improvement Improvement for an existing feature. JS parity

Comments

@1ec5
Copy link
Contributor

1ec5 commented Jan 12, 2018

Port turf-buffer as padded(by:).
@1ec5 1ec5 added the improvement Improvement for an existing feature. label Jan 12, 2018
@1ec5 1ec5 added the JS parity label Jan 24, 2018
@1ec5
Copy link
Contributor Author

1ec5 commented Mar 4, 2020 •
edited
Loading

turf-buffer depends on a port of JSTS’s BufferOp. Turf.js has wanted to move away from JSTS for a long time, particularly turf-buffer: Turfjs/turf#88 Turfjs/turf-buffer#4 Turfjs/turf-buffer#33 Turfjs/turf#674.

@1ec5
Copy link
Contributor Author

1ec5 commented Mar 4, 2020

GEOSwift, which like JSTS is ultimately derived from the Java Topology Suite, has a buffering implementation available in Swift.

@nighthawk nighthawk mentioned this issue Oct 21, 2022
Open
@almin1337
Copy link

Will buffer method soon be available for Swift (https://github.com/Turfjs/turf/tree/master/packages/turf-buffer)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
improvement Improvement for an existing feature. JS parity
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@1ec5 @almin1337