Rather than a dedicated /point endpoint, I followed the pattern for querying assets at a lon/lat pair ({lon}/{lat}/assets).
I tried to mimic the response class from the analagous titiler endpoint, the only difference is that the assets object comes back as a list. It looks like this:
The other odd thing is that if you send a query for a point that doesn't intersect any assets, you get a 204 instead of a 200 with an empty values list.
I added the capability to query asset values at a point as discussed in https://github.com/stac-utils/titiler-pgstac/discussions/144.
Rather than a dedicated
/point
endpoint, I followed the pattern for querying assets at a lon/lat pair ({lon}/{lat}/assets
).I tried to mimic the response class from the analagous titiler endpoint, the only difference is that the
assets
object comes back as a list. It looks like this:The other odd thing is that if you send a query for a point that doesn't intersect any assets, you get a 204 instead of a 200 with an empty
values
list.