Something that strikes me here, but I don't think for now, how the class inheritance goes

1. object
2. Normalise (2 stops min/max)
3. PiecewiseLinearNorm (generic n stops)
4. DivergingNorm (3 stops, min/center/max)

I.e. it should go from the most general at the end of the MRO to most specific at the top... instead we have the most specific,Normalise at the bottom... not something I specifically want to address now, both because I know I have a lot of more fundamental refactoring to do in this area, and I want to make sure I get that right before fiddling about here; and also because having slept on it, I would like to see the OrderedDict on the MRO, rather than existing as just an attribute, and that will have to wait until we drop python-2.6

@OceanWolfNormalize is not themost specific, it is the simplest and most common. It is no more ore less specific than any of its subclasses. Yes, one could split out aNormalizeBase and use that as the common ancestor for all. Is the gain in formal structure worth the additional LOC and the extra level of redirection for the Normalize case, which is probably something like 95% of real world usage?

@efiring by most specific I mean that as far as I can tellNormalize does the same thing asDivergingNorm but withvcenter = np.mean([vmin, vmax]).

DivergingNorm does the same thing asPiecewiseLinearNorm but with just one stop betweenvmin andvmax set specifically at the centre.

I don't see what you mean by "additional LOC", as far as I see it we significantly reduce the LOC, i.e. the Normalise class becomes something like:

classNormalize(DivergingNorm):def__init__(self,vmin=None,vmax=None):super(Normalize,self).__init__(vmin,None,vmax)

Btw the is a lot of overlap between transforms and the norms, it would be nice - a properly quite difficult - to combine these.

@Tillsten Yes, I have plans to do this with my MEP working on refactoring the axes#5029, I plan to merge the colourbar with the other axis code, essentially these Normalisations works as axis transformations, so it makes sense to me to simply the API here.

As these extra norms have been pushed back to at least the 2.1 release next April, this gives me time to work on this MEP. We shall see how far I get with this. Help always appreciated, especially as I have MEP 22 and 27 to finish for 2.1 once 1.5 lands.

See#12419 where I moved this PR (couldn't see force pushing here as viable)