TileStitcher class (anti-gap TileLayer) #9732
Open
Conversation
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
Signed-off-by: Iván Sánchez Ortega <ivan@sanchezortega.es>
This was referenced May 22, 2025
Collaborator
|
@IvanSanchez would love to give this an in-depth review, but I am a bit tied up for the next alpha. Seems like a nice addition though! |
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.
My approach to fix #3575 once and for all.
This is basically #5290, but adapted to the 2.0 codebase.
While @mourner's comment at #5290 (comment) kinda still stands, IMO the 1-px gap has been a PITA for long enough, none of the hacky workarounds were good, and 2.0 is a good excuse to get this in.
Still a separate class since it adds ~250 lines of code that not all users might want to have.
TODO: [ ] links to the new class in the API documentation HTML.