Sort the mess in spatial_tools.py

[rhugonnet]

Right now it's a bit our "dumper" module.

Looking at what's inside, I think we could split into:

• a robust_stats.py module, that includes nmad, nd_binning, robust_polynomial_fit, robust_sumsin_fit, subsample, and all related subfunctions
• move stack_rasters, merge_rasters, merge_bounding_boxes, get_array_and_mask, etc... to geoutils
• rename spstats into spatial_stats.py for consistency with robust_stats.py

[rhugonnet]

@erikmannerfelt @adehecq An opinion on this?

[erikmannerfelt]

I agree on your division! I would like to discuss the robust_stats.py, however, as I interpret "robust" as just another synonym for "good". It would (for me) sound like calling it good_stats.py (as opposed to the bad_stats.py? ;) ). Maybe I'm alone on that opinion? What do you think, @adehecq?

I especially agree on the -> geoutils suggestions.

[rhugonnet]

Maybe there's a better subdivision for that module?
For the naming robust, it is the term widely used in statistics for this kind of methods, from a "simple" NMAD to more complex M-L methods like RANSAC (https://en.wikipedia.org/wiki/Robust_statistics).

[adehecq]

Ok to move some of the functionalities to geoutils.
Should it be in georaster directly? Right now, it's mostly just one class and not really a lot of other functions, but this can change.

[erikmannerfelt]

CLosed with 226