-
Notifications
You must be signed in to change notification settings - Fork 20
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
IS Catalog widget fails to download the images from an Image Service #36
Comments
@jk518008 Can you elaborate a bit? It worked the first time and it didnt after that? |
I published a different image service today registering the data with the Image Server, but I am still getting the same error as before, even when trying at the first time. ESRI analyst said that he was able to download images using IS Catalog widget only after he chose to copy the data over to the server so that might be the issue. The problem for me is that my images including the mosaic dataset and overviews size up to few TB so that doesn't make sense to copy them to the server. |
Okay. Thanks, we will look into this. |
Hi, |
@gcampanile Thank you for the response. Can you please elaborate on how I can change the widget to do that? What do I need to change in the code? Thank you |
In the ISCatalog\base\CheckoutWidget\base\Download\ImageryDownloadWidget.js, lines 110-114 :
Of course if you need something different from JP2 you must change the string or use a parameter. |
@jk518008 have you been able to try the fix mentioned above? |
When first trying to download individual images from an image service using IS Catalog widget, the download was successful.
After that when clicking on an image to download, the browser will prompt a HTTP ERROR 400 each time. The issue happened with multiple image services with download enabled.
WAB 2.11 edition was used.
An ESRI analyst assigned to this case was able to reproduce the same issue using the IS Catalog widget (Esri Case #02461170). WAB 2.12 edition was used by ESRI analyst.
The text was updated successfully, but these errors were encountered: