Pydap was causing troubles on an on and as we require netCDF anyways, we could also just use netCDF for accessing opendap resources. This PR sets all opendap resources to be accessed via netCDF.
During creation of this PR, another issue surfaced: some netCDF datasets are incompatible with the classic data model of netCDF (which is assumed to be the opendap data model by several clients). This PR changes access to the affected datasets to direct download of the original netCDF files (using simplecache) and opens those files as local netCDF files. I expect this to be a good trade-off, as the relevant netCDF files are rather small (several MB).
Pydap was causing troubles on an on and as we require netCDF anyways, we could also just use netCDF for accessing opendap resources. This PR sets all opendap resources to be accessed via netCDF.
During creation of this PR, another issue surfaced: some netCDF datasets are incompatible with the classic data model of netCDF (which is assumed to be the opendap data model by several clients). This PR changes access to the affected datasets to direct download of the original netCDF files (using
simplecache) and opens those files as local netCDF files. I expect this to be a good trade-off, as the relevant netCDF files are rather small (several MB).