Draft
Enforce 300 ft minimum separation for CL1/CL2/CL3 in cloud-levels.lua#38
Conversation
Copilot
AI
changed the title
[WIP] Fix separation issue in cloud levels calculation
Enforce 300 ft minimum separation for CL1/CL2/CL3 in cloud-levels.lua
Jun 5, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
cloud-levels.luacould still emit CL1/CL2/CL3 bases closer than the required 300 ft after its layer selection and fallback reshuffling. This change adds a final spacing guard so the published cloud layers always satisfy the minimum separation rule.What changed
CL1,CL2, andCL3after the existing layer-selection logic.dz = 300, the pass drops one layer and compacts the remaining outputs.Selection rule for conflicts
BKN+.BKN+.BKN+, preserve the lower layer.Why this is needed
Implementation detail