feat: add GRIB2 support to Raster API #529
Open
+2
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue
N/A
What?
.grib2,.GRIB2toCPL_VSIL_CURL_ALLOWED_EXTENSIONSinvedaRasterSettings.envdocker-compose.ymlunder therasterserviceWhy?
Currently only tiff extensions are whitelisted by GDAL, so when trying to stream GRIB2 files directly to the Raster API, it throws an error (see testing url below). Some VEDA tools (eg. the fire tool) currently stream GRIB2 files to TiTiler for fetching wind information but still rely on the public demo TiTiler instance. We’d like to switch them over to the openveda raster API and for that grib2 support is needed.
Testing?
Tested locally:
docker compose up.grib2requests were rejected before the change and succeed after the update using this url in Chrome:http://localhost:8082/cog/preview.png?rescale=-127,128&url=vrt:///vsicurl/https://noaa-hrrr-bdp-pds.s3.amazonaws.com/hrrr.20250512/conus/hrrr.t06z.wrfsfcf04.grib2?bands=10,11&format=png