-
Notifications
You must be signed in to change notification settings - Fork 799
load the tile in cases where this.options.crs exists #1411
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
Conversation
@gavinr-maps this looks correct to me. We should support both when a user needs the remapped lodmap from the server AND when the user passes a crs option and it using Proj4Leaflet which I think this handles. Could you drop a reproduction case in for me to take a look at locally in the debug folder? |
# Conflicts: # src/Layers/TiledMapLayer.js
Test cases:
|
@gavinr-maps I think this looks good lets merge it and cut a new release. |
Attempt to fix #1384 .
In #1400 we changed this line so that it would work for cases for custom LODs. But that broke this for cases of Non-mercator projections. So this PR attempts to solve both cases by creating a separate case for non-mercator projections (
this._lodMap = "crs"
) ... but it does feel a bit hacky so I'm wondering if maybe we need to just go back to #1400 and see if that was an incorrect fix. I probably need to discuss this with @patrickarlt.