deprecated ArcGisImageServerTerrainProvider #4981
Merged
Conversation
This file contains 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
|
Looks good, please submit an issue to remove this with the |
|
Also in that issue note that there are a few |
|
Part of #4897 |
|
Did the ArcGisImageServerTerrainProvider coundn't work all the time? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Resolves #4955.
Do we know if there is anything roadmapped for browser TIFF support? Or, out of curiosity for someone who knows very little about how imagery servers work, how impractical is in-engine TIFF -> RGBA PNG conversion if the TIFF can just be fetched as a binary or something?