v.perturb: Modify points for all types #2852
Draft
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 modifies points in all feature types not only type GV_POINT. While this may create unexpected results for some data, separate lines work just fine. The current code just does that always, but this should be opt-in (changes behavior) and it can be marked as experimental or just with a good description of what to expect. I test with lines, but not areas. Speed implications of the for loop not tested.
github-actions
bot
added
vector
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.
This modifies points in all feature types not only type GV_POINT. While this may create unexpected results for some data, separate lines work just fine. The current code just does that always, but this should be opt-in (changes behavior) and it can be marked as experimental or just with a good description of what to expect. I test with lines, but not areas. Speed implications of the for loop not tested.