OpenLayers draw snapping fixed to avoid cross-bundle projection transform - #520
Merged
Merged
Conversation
|
markfee
approved these changes
Sep 11, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
OpenLayers draw snapping fixed to avoid cross-bundle projection transform
Problem: With the draw plugin and OpenLayers provider loaded as separate bundles, enabling snapping threw
No transform available between EPSG:27700 and EPSG:27700and broke vertex dragging in edit mode. Each bundle vendors its own privateol/projregistry, and only the provider's bundle registersEPSG:27700— the draw plugin'ssnapEngine.jscallstransform()against its own separate, unregistered registry.Fix:
snapEngine.jsnow skips thetransform()call when source and view projection codes already match, avoiding the cross-bundle registry dependency entirely.