Support for buffer zone (ie. territorial waters = 12nm) #11
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This comment was marked as outdated.
This comment was marked as outdated.
|
Rather than buffer zone which requires much memory and recompute, I just refactored using @geo-maps/countries-maritime-10m boundaries. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
@simonepri - this was my attempt to add buffer zone logic to your is-sea module. I updated index.js and package.json but did not update readme, demos, or test. Was not sure how to do that as I'm more comfortable with python. I thought adding the @turf/buffer module would be lighter weight than trying to import another map which has buffers drawn and would be especially 'lite' for raspi or embedded use aboard a vessel. If you can guide me on whatelse needs added, I'll surely do my best to contribute.