Kai Mühlbauer

Yeah, but we might improve the current code to only pad if really needed. As of now the padding is applied in any case, which slows down your processing.

The best solution to this problem would be to create the underlying dataset with the wanted netcdf-c/netcdf4-python fillvalues. ```python import netCDF4 netCDF4.default_fillvals ``` ```python {'S1': '\x00', 'i1': -127, 'u1': 255,...

@master-nemo Glad you found a workaround for your use-case. Nevertheless it would be good to fix this within the package. I'll leave it open for now until fixed.

Yes, that's actually the case. If the size of the dimension and the size of the variables dimension do not match, the whole array is read to0 memory before subsetting....

@ljstrnadiii Did you come any further with this?

@syedhamidali Thanks for opening this issue. We would need to completely free wradlib from any oldstyle `pylab` style plotting. So if anyone wants to take the lead here...

@syedhamidali Yes, please go ahead. This will be a great improvement in wradlib compared to the current solution.

While researching #545 this resurfaced. The `plot_plan_and_vert` and `plot_max_plan_and_vert` need to be properly refactored/reimplemented.

Nice package and discussion! Sorry for being late to the party! We at [wradlib](https://github.com/wradlib) only load current DWD radar data in our example notebooks via a quite simple http-request, no...

@meteoDaniel Nice to see you around, too! I'll open a new issue regarding the HDF5 radar data. Looking forward to testing that.