The colour key always matches the map

Changes since 2.14.1.

#Fixed

• The result card's colour key is read from the map. The key under an OrionAI result used to be written by OrionAI from its own notes. When a result was a grid (an NDVI or crop-vigour map, for example), OrionAI was never told which colours the grid was drawn in and sometimes described other colours: one crop-vigour map was keyed pale yellow to dark green while the map was drawn red to green. The key now comes from the map's own legend, the same one you see under Controls → Legend, so it always shows the colours on the screen.
• Grid legends match the grid. Hillshade, distance, soil and aspect grids were drawn in one colour scale and listed in the legend with another (usually purple to yellow). The legend now uses the exact colours the map is drawn in.
• Classes made from a grid keep its colours. Grouping a hillshade, viewshed, wetness or aspect grid into classes now colours the classes along the grid's own scale instead of a default purple to yellow.
• Ordered classes keep their order. When OrionAI coloured areas by range classes such as "0.2 to 0.35" and "0.65 to 1", the colours could follow the order the classes appeared in the data, so a middle class was darkest. Range classes are now coloured from lowest to highest.

#Improved

• OrionAI describes the colours it can see. Each grid step now tells OrionAI the exact colours it drew, and saving the map hands it the map's colour key, so the words in the result ("pale yellow for bare ground, dark green for dense crops") match the key.
• Legend labels match the result card. Classed maps show the same class labels in the map legend as on the result card, for example "1,470 – 1,750 m" instead of "≥ 1,470".