Skip to content

Conversation

emmanuelmathot
Copy link
Member

This PR adds the ability to reference item, collection and asset reference in the URLs

@emmanuelmathot emmanuelmathot requested review from lossyrob and m-mohr May 4, 2023 13:29
@emmanuelmathot emmanuelmathot changed the title updated changelog Reference placeholders May 4, 2023
@m-mohr
Copy link
Contributor

m-mohr commented Jun 19, 2023

Related to and should probably wait for #10

@m-mohr
Copy link
Contributor

m-mohr commented Jun 21, 2023

Also, I'm not really getting why these values are not hard-coded? In the example it looks like all values are "fixed" to a specific value (except for asset)?! And then, why is the asset key defined but not the asset href and/or type?

@emmanuelmathot
Copy link
Member Author

emmanuelmathot commented Sep 19, 2023

Also, I'm not really getting why these values are not hard-coded? In the example it looks like all values are "fixed" to a specific value (except for asset)?!

right, the item values could be fixed as the link is part of it. But there is still the asset case

And then, why is the asset key defined but not the asset href and/or type?

because the asset is relative to the item and it's href may be computed form several source (e.g. alternate extension). a tiling service such as titiler read the stac item and use the asset name to make the tile. The asset placeholder offers the possibility to list a unique link for the tiling service for the item (including all assets)

@m-mohr
Copy link
Contributor

m-mohr commented Jun 22, 2025

Given that we now have a link templates extension, I think this extension generally should migrate all templated links to use that construct. Then there's no specific need to define much in this extension with regards to placeholders.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants