Currently that works only for Zarr datasets, but that seems like a reasonable place to start and extend that functionality to the general case. For NetCDF granules, we would need a POST endpoint that takes as input the S3 path to the granules, and the variable names for the measurement of interest, latitude, longitude, and time.
The Apache SDAP Project Management Committee discussed possible including this Zarr support as part of the next official release (within a month most likely).
The SDAP development branch for Zarr includes an endpoint to add, update or delete a Zarr dataset into a running SDAP instance: https://github.com/apache/sdap-nexus/blob/234909570eb16c131390c6478e84b499925c7f3a/analysis/webservice/management/Datasets.py
Currently that works only for Zarr datasets, but that seems like a reasonable place to start and extend that functionality to the general case. For NetCDF granules, we would need a
POSTendpoint that takes as input the S3 path to the granules, and the variable names for the measurement of interest, latitude, longitude, and time.The Apache SDAP Project Management Committee discussed possible including this Zarr support as part of the next official release (within a month most likely).