Replies: 3 comments
-
Hi @bransonf 👋! Unfortunately it is not possible to use an expression that combines assets from items in different collections. titiler-pgstac attempts to create an array out of every STAC item in the search results, and it fails when it finds an item that does not have all of the requested assets. In the case you have presented half of the items are missing This is a feature that I would like to support someday, though! Keep an eye on #189 for further discussion. |
Beta Was this translation helpful? Give feedback.
-
You might be able to do this be it will involve customization of the backend methods titiler-pgstac/titiler/pgstac/mosaic.py Lines 322 to 357 in d212969 The idea would be to avoid passing the |
Beta Was this translation helpful? Give feedback.
-
The core of the problem is that titiler-pgstac assume that collections have the same assets and that indexes or expressions are set of Maybe Cross collection visualization is something users need/want but for now we never had |
Beta Was this translation helpful? Give feedback.
-
I have two collections:
["opera-loss", "nlcd"]
that I want to mosaic assets from and run some statistics via Titiler.I register a search via
POST /searches/register
And validate the assets are found via
GET /searches/<SEARCHID>/-98.5795,39.8283/assets
:But when attempting to run
POST /searches/<SEARCHID>/statistics
with params:I get the error:
Changing to
expression=opera_loss
I get:And
expression=nlcd
I get:Is this a misguided use of the /searches endpoint, or should this sort of query across different collection-assets be possible?
I can work around this by adding the appropriate assets from the
nlcd
collection to theopera-loss
collection or creating a new collection with the assets from both and registering a single-collection search + statistics, but it's not as elegant as being able to do cross-collection mosaicing.PgSTAC version 0.8.5
Titiler version 0.1.0
Thanks for any insights here!
Beta Was this translation helpful? Give feedback.
All reactions