While fixing this, would be nice to find a solution to make UploadGUI work with non-LatLonBox object-specific spatial coverages. It would be too costly to add GUI for creating or editing all the types of spatial coverage that our API provides. However, it's possible to at least support limited metadata update for data objects with non-LatLonBox custom geo-coverage. Rather than crash, UploadGUI should preserve the existing custom coverage when it is available, and show some kind of warning for the user. When updated metadata is uploaded, the custom geo-coverage should be preserved as it was.
Example object: https://meta.icos-cp.eu/objects/EiJUQipylAKdSk9j1_kz_5qP
While fixing this, would be nice to find a solution to make UploadGUI work with non-LatLonBox object-specific spatial coverages. It would be too costly to add GUI for creating or editing all the types of spatial coverage that our API provides. However, it's possible to at least support limited metadata update for data objects with non-LatLonBox custom geo-coverage. Rather than crash, UploadGUI should preserve the existing custom coverage when it is available, and show some kind of warning for the user. When updated metadata is uploaded, the custom geo-coverage should be preserved as it was.