Feature request: Dynamic seasonal saturation adjustment based on month

[501NotImplemented]

As of AutoOrtho 2.1.2, seasonal color adjustment in AutoOrtho is implemented through fixed saturation multipliers applied to the ortho imagery:

This assumes that vegetation intensity is constant within each season.

Problem

Vegetation color intensity changes gradually during the year and does not follow discrete seasonal steps. Examples:

• Early–mid March vegetation appearance is close to late February.
• Late May vegetation is typically the most saturated/bright period of the year.
• Similar gradual transitions exist between all seasons.

Using a single saturation value per season produces visible jumps in color intensity at seasonal boundaries and does not match the real vegetation cycle.

Proposed approach

Replace fixed seasonal values with a month-based saturation model.

Instead of mapping saturation to 4 seasons, define a monthly saturation curve (12 values).
The value applied during rendering is selected based on the current month.

Example baseline table:

Month	Saturation
Jan	55%
Feb	55%
Mar	60%
Apr	75%
May	100%
Jun	100%
Jul	95%
Aug	95%
Sep	85%
Oct	75%
Nov	65%
Dec	55%

Optionally apply linear interpolation between months to avoid discrete transitions.

Result

• Continuous seasonal transition.
• Better match with real vegetation cycles.
• No abrupt color change when season changes.
• Still lightweight and configurable.

Optional extension

Allow user-editable curves in configuration so saturation behavior can be adapted for different climate zones.

[karlrado]

There is already an interpolation performed here which should create a curve and perform the linear interpolation.

I admit I have not completely analyzed the code (yet) to see if this is the case.

But before I/we look further, are you actually able to detect an abrupt color change over some supposedly small change in date?

It would be useful to see screenshots along with the date for each one that illustrates the problem.

[501NotImplemented]

There is already an interpolation performed here which should create a curve and perform the linear interpolation.

I admit I have not completely analyzed the code (yet) to see if this is the case.

But before I/we look further, are you actually able to detect an abrupt color change over some supposedly small change in date?

It would be useful to see screenshots along with the date for each one that illustrates the problem.

Oh, that's great to know. TBH, I can't say that I really noticed any visible difference. Even more, in some areas of flying, I'm not even sure whether the seasoning is applied at all. Which led me to the thought that the seasoning is constant and could be improved.

[karlrado]

TBH, I can't say that I really noticed any visible difference. Even more, in some areas of flying, I'm not even sure whether the seasoning is applied at all.

I'm actually glad to hear that because I've been hard pressed to detect any application of seasons at all sometimes. So, I was surprised to hear about someone interested in this level of fine tuning.