-
Notifications
You must be signed in to change notification settings - Fork 796
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
Undesired white background being added to dynamicMapLayer #1187
Comments
@teofilosalgado can you please share the URL to the mapservice you are using? |
@teofilosalgado also what |
And a demo to help us debug would speak 1,000 words, too.
|
@jwasilgeo I left
I will create an JSBin and reply it's link here ASAP. |
@teofilosalgado thank you for the extra info and for the jsbin. Can you try also this property in your layer options?
I think that works better and seems to provide the visual output you want. Must just be png24 vs png32. |
@jwasilgeo it worked like a charm! Thank you! Me and my team were stuck with this problem for days! |
I'm very happy to hear the good news. Do you happen to have any feedback or suggestions on improvements to the documentation, such as for the |
would it help to just default to |
I agree with @jgravois, I really thought |
Change all references to 'png24' in the Dynamic Map Layer Spec to 'png32' Related to Esri#1187.
Change all references to 'png24' in the Dynamic Map Layer Spec to 'png32' Related to Esri#1187.
Change all references to 'png24' in the Dynamic Map Layer Spec to 'png32' Related to Esri#1187.
All supported browsers;
L.version
):1.6.0
L.esri.VERSION
):2.3.3
Steps to reproduce the error:
dynamicMapLayer
to a leafletmap
with the following code:What happens is: every layer my ArcGIS MapServer provides are rendered with an opaque white background layer below them.
According to Firefox's network tab in developer options, the image returned by the ArcGIS service for the aforementioned screenshot is:
I was expecting: esri-leaflet to render my layers just like AGOL does.
The text was updated successfully, but these errors were encountered: