TileLayer should be able to handle rotations without trying to fetch tiles beyond the given extent
#7573
jeffpeck10x
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
See comments in this PR #5080 from 2020 where @ilan-gold implemented a great solution for handling arbitrary
modelMatrix
inputs for the TileLayer.One minor hiccup in that solution is that when the
extent
is recalculated for the givenmodelMatrix
, there is seemingly some imprecision that leads to occasional 404s when there is a request for a tile that is outside the given bounds (provided in theextent
prop bbox).In that discussion, I proposed a workaround to adjust the
extent
to account for the margin of error:But, I am opening this discussion to see if there is a more elegant general purpose solution for the
TileLayer
to handle this small issue.I should note, I am not 100% sure that the result of the extent transformation is actually the problem here, but as a simple example, let's rotate two points 90 degrees:
Result:
(of course, that rotated bottom left should really be
[-1234567, 0]
)The resulting transformed
extent
can potentially cause the TileLayer to try to fetch tiles that are beyond its bounds.Beta Was this translation helpful? Give feedback.
All reactions