Thomas Lavergne

This is "slightly" related to issue #12 indeed. But in issue #12, I use a pre-computed weight (e.g. an uncertainty estimate), and was not aiming at an on-the-fly decision (e.g....

Originally, my request also had getting the coarser grid spacing. But mixing the two in a single function meant a lot of checks and documentation. Maybe have another method like:...

Could work. But the routine has to check the validity of the input (that they are exactly multiples or fractions of what is already there).

And just to think ahead: I see two applications of this: 1) motion detection. For motion detection from cross-correlation techniques you need two grids: the target grid which is the...

I have a version of that in my modules somewhere, but never pushed it to the codebase.

@gerritholl `area.crs.to_cf()` takes us a long way. But it only encodes the "crs" variable, not the `projection_(x|y)_coordinate` variables, nor create the associated dimensions, etc...

I opened this feature request a while ago, and had honestly forgotten about it. @gerritholl 's comment made me think a bit more. I recall how `AreaDefinition.load_cf_area()` works: ``` >>...

It is indeed only from CF-1.8 that lat/lon could be omitted in case the coordinate system is fully defined by x, y, crs. https://github.com/cf-convention/cf-conventions/pull/133 I don't have a strong feeling...

I am somehow doubtful that the edges/corners of the swath are the issue. I am not aware that the structure of the swath has anything to say for pyresample and...

It is late (and early!). It seems data_reduce works better with two small edits. Will have to confirm tomorrow, particularly that this does not break the tests. ```python =:D git...