Document elevation normalization logic in Communitu_79a.lua

[Copilot]

Summary

No code changes were made. This PR documents the existing elevation normalization logic in the FloatMap:Normalize() function.

Analysis

The function implements Min-Max Normalization to scale elevation values to [0, 1]:

Why minAlt is subtracted from all elevations (line 5745):

• Shifts the elevation range to be zero-based
• Transforms arbitrary range (e.g., [200, 400]) to [0, 200]

Why minAlt is also subtracted from maxAlt (line 5749):

• Maintains correct range span after the shift
• Ensures the scaler 1.0 / maxAlt produces values that reach exactly 1.0
• Without this adjustment, maximum normalized value would be (maxAlt - minAlt) / maxAlt instead of 1.0

-- Example: elevations [200, 250, 300, 400]
minAlt = 200, maxAlt = 400

-- After subtraction: [0, 50, 100, 200]
maxAlt = 400 - 200 = 200  -- Must reflect actual max in shifted data

scaler = 1.0 / 200 = 0.005
-- Final normalized: [0, 0.25, 0.5, 1.0] ✓

This is standard range normalization used in procedural map generation to ensure consistent elevation distributions.

Original prompt

Can you read communitu_79a.lua mapscript from this repo? I want you to explain why the min elvation is sibtracted from all elevations and additionally from max elevation.

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.