I have uploaded a KML/OBJ file set as a 3D Capture and I would like to make it available for offline download. When I toggle the “Make Available for Offline Download” option the archiving progress bar completes but eventually freezes with the error “There was an error while processing the asset to be downloaded. Use the toggle to start the process again.”. Using the toggle has no effect once this error happens.
I’ve had this problem in the past with similar datasets and I can usually resolve it by deleting the Asset and reuploading it. But I’ve tried that a few times and am not having any luck with this dataset.
My Asset ID is 1833573.
The team is investigating the issue you are seeing. To gather more context for our team, do you have any other asset ids of archives currently stuck in an errored state that we could look at? It is very rare to see an archiving job fail and so any information you could provide us will be extremely helpful in diagnosing the problem.
No, unfortunately we don’t have any others currently. We are running low on space, and this is a large dataset, so when we get a failure we have to delete the failed one before starting a new one.
Though I can say that all of the failures have been small variations of 1833573. We edit the .obj and .mtl files to alter the terrain and then upload to Ion to convert to 3D Tiles.
We have opened an issue regarding this internally and linked back to this thread to follow up in the future. If you do see any more failures in the meantime, please let us know here with the asset ids before re-running the archive so that it can be investigated further.
I just tried to upload an unmodified version of the tileset and got the same error, asset ID is 1844351.
The original source of the data is here: City of Melbourne 3D Textured Mesh (Photomesh) 2018 — CoM Open Data Portal
We run a script on the data to remove all but the highest LOD meshes in that dataset, but otherwise it is not modified.
Thanks for letting us know. The content of the upload has no bearing on this issue but having a fresh failure helps us better understand what’s happening. The problem seems to be internal to how the archiving process is being started in certain edge cases.
While I do the majority of the debugging on my side, can you help me understand the workflow you are using when uploading/archiving this data? Is it:
- Upload data and select “Make available for download” as part of the upload UX
- Upload data
- While it’s tiling, select “Make available for download”
- Upload data
- Once it’s finished tiling, select “Make available for download”
Also, are you using the “Adjust Tileset Location” tool to position the tileset?
My suspicion is that the issue has to do with the interplay of the above items, so by having a better idea of your work flow, I can debug it quicker.
Here is our workflow:
- Upload Data
- Once it’s finished tiling, adjust tileset location.
- Select “Make available for download”
We found that if we did it any other order, the tileset location would not be saved in the offline data archive.
Have you had any luck finding the cause of this issue? We have a project coming up that needs this dataset, and I’m just wondering if I should start thinking about a Plan B .
I apologize that this is taking some time. We are still actively investigating the cause of this. I will reach out to you as soon as we get to the bottom of it. Thank you for your patience!
Sounds good, Thanks @Ankit_Trehan!
To provide you with an update regarding these errors, our team has deployed a fix to the archiving logic last night addressing these errors. Please let us know if you continue to face issues.
Thank you for all your help here!
Thanks @Ankit_Trehan, I just tried and was able to successfully transfer my dataset!