as some of Iliad Partners are using ERDDAP, some OpenDAP, I wonder if it is feasible to propose the .DAP file properties mapping so the potential connectors could follow.
ERDDAP is already supporting GeoJSON format, which is Features collection, the mapping of query properties and metadata can be required.
ERDDAP is also supporting NC files access and .nc.dods and that is what DAP python client is using https://www.pydap.org/en/latest/client.html
Here, also the properties mapping can be done.
Proxying for heavy data data probably does not make sense, while there is already pygeoapi wrapper over the features from ERDDAP API available https://github.com/geopython/pygeoapi/blob/master/pygeoapi/provider/erddap.py
I propose to define the NetCDF files arrangements and query mapping that could support OIM simply and refer to DAP it as one of the options.
as some of Iliad Partners are using ERDDAP, some OpenDAP, I wonder if it is feasible to propose the .DAP file properties mapping so the potential connectors could follow. ERDDAP is already supporting GeoJSON format, which is Features collection, the mapping of query properties and metadata can be required. ERDDAP is also supporting NC files access and .nc.dods and that is what DAP python client is using https://www.pydap.org/en/latest/client.html Here, also the properties mapping can be done. Proxying for heavy data data probably does not make sense, while there is already pygeoapi wrapper over the features from ERDDAP API available https://github.com/geopython/pygeoapi/blob/master/pygeoapi/provider/erddap.py
I propose to define the NetCDF files arrangements and query mapping that could support OIM simply and refer to DAP it as one of the options.