-
Notifications
You must be signed in to change notification settings - Fork 368
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Orthographic threshold reduction #1951
base: main
Are you sure you want to change the base?
Conversation
Looks like you'll have to update some images that are causing the test failures. I think all of the new images look like improvements to me, which is good :) For the multiple projections one, we may want to just increase the tolerance a bit rather than updating that image, since it is only a small difference for one image test. (We should really break this out into separate images later on) |
Oh, wait, have I not PR'd this already? |
@ludwigVonKoopa, the images were just updated, so you're going to have to rebase this and likely need to update the Orthographic test image. Can you also remove the |
@ludwigVonKoopa, I still think this looks like a good update if you're interested in getting it in. I'm guessing you'll need to update the Orthographic image tests already present in the test suite. One additional request would be to put a comment above, saying something about why this should be the threshold so someone else doesn't come and change it later unknowingly. |
|
Related issue : #1907
This PR changes Orthographic projection threshold to solve tiles loading error.
With actual threshold value, when using tiles with enough precision, the projection boundaries are eroded too much, and result in some tiles data not loaded :
I did not add tests with this PR, because i don't see how i could easily tests this.
I could add a test which
But this may be too much. What do you think ?
Thanks