stac copy with SELF_CONTAINED still has absolute links for assets #31
Comments
lossyrob
added a commit
to stac-utils/pystac
that referenced
this issue
Jan 14, 2021
Previously only link href types (absolute vs relative) were modified as part of the `Catalog.save` process based on the catalog types: for ABSOLUTE_PUBLISHED, all link hrefs were made absolute, etc. The asset HREFs were not modified, which was counter to the expected result outlined in stac-utils/stactools#31. This change causes asset HREFs to also be changed to absolute or relative based on the catalog type. Note that if the asset HREF cannot be made relative, e.g. the asset HREF points to an HTTP location and the item is being stored locally, then the HREF is left unchanged.
lossyrob
added a commit
that referenced
this issue
Jan 15, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The main goal I'm trying to accomplish here is to be able to make a stac catalog that has asset links that are all relative, so I can upload to the cloud or zip up and send to someone. One route I tried was move-assets, and my problems there are in #30.
The other thing I was hoping would help was to do
stac copy -t SELF_CONTAINED. I assumed that it would make it so all the asset links would turn relative. This didn't happen, they all just stayed absolute, even if I included the assets in my copying. I also tried RELATIVE_PUBLISHED, and it didn't work either.Maybe I'm expecting too much, and the assets should have their links updated with move-assets, but if so then we need to figure out #30, and then should also put a note here.
The text was updated successfully, but these errors were encountered: