-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade titiler-pgstac #234
Comments
Most of the breaking changes (Some of them only concern the main application of titiler-pgstac so it might not be relevant):
|
ref #234 This PR aims to update titiler-pgstac from version 0.2.3 to 0.8.0. Doing so, will also update titiler, rio-tiler, morecantile, fastapi and pydantic. Endpoint changes - ~~Use `/collections/{collection_id}/items/{item_id}` prefix for Item endpoint.~~ I was able to keep this as it was (`{endpoint}/stac/info?collection=collection1&item=item1`) - `post_process=` -> `algorithm=` - change tile url path parameter order from `/tiles/{searchid}/{TileMatrixSetId}/{z}/{x}/{y`} to `/{searchid}/tiles/{TileMatrixSetId}/{z}/{x}/{y}` ``` # Before {endpoint}/mosaic/tiles/20200307aC0853900w361030/0/0/0 # Now {endpoint}/mosaic/20200307aC0853900w361030/tiles/0/0/0 ``` - replace `/{searchid}/{z}/{x}/{y}/assets` endpoints by `/{searchid}/tiles/{z}/{x}/{y}/assets` - replace - by _ in query parameters - coord-crs -> coord_crs - dst-crs -> dst_crs - remove `max_size` default for mosaic's `/statistics [POST]` endpoint breaking change - add `/bbox` and `/feature [POST]` optional endpoints
I created a test stack with the new titiler and a copy of the staging database that I needed for testing the veda-docs |
Adding more changes that were commented on the original PR (Thanks @anayeaye for thoroughly going through the changes!)
|
Veda-config PR with algorithm change. |
We need another version upgrade for This is hopefully the last missing change to enable us to do equal-area zonal statistics. 🚀 Happening here: |
Note: any re-deploy will include the new rio-tiler fix (because rio-tiler is not pin to specific version 🙏) #246 will be nice to have if we want to use the custom algorithm instead of eqa projection! |
Awesome, @anayeaye and @vincentsarago, this now works: import requests
RASTER_API_URL = "https://dev.ghg.center/api/raster"
ITEM_ASSET_URL = "s3://veda-data-store-staging/no2-monthly/OMI_trno2_0.10x0.10_202109_Col3_V4.nc.tif"
AOI = {
"type": "FeatureCollection",
"features": [
{
"type": "Feature",
"properties": {},
"geometry": {
"coordinates": [
[
[
-115,
82
],
[
-115,
-82
],
[
-43,
-82
],
[
-43,
82
],
[
-115,
82
]
]
],
"type": "Polygon"
}
}
]
}
result = requests.post(
f"{RASTER_API_URL}/cog/statistics",
params={
"url": ITEM_ASSET_URL,
"dst_crs": "+proj=cea"
},
json=AOI["features"][0],
)
result.raise_for_status()
result.json() and gives different results when I set |
Large backlog
TiTiler-PgSTAC is now at 0.8.0 and we are still at
veda-backend/raster_api/runtime/setup.py
Line 9 in e4b02a5
This is blocking a number of features that were implemented upstream in TiTiler, which we need in VEDA, most notably
Complications
There have been some breaking API changes in TiTiler between the latest version and what we have, so any update will need to be coordinated with dependants - the VEDA Dashboard and the EO Dashboard.
Acceptance criteria
The text was updated successfully, but these errors were encountered: