[convert] Ensure winding order of polygon linear rings#28
Merged
Conversation
mickmis
force-pushed
the
8/ensurewindingorder
branch
from
365cb49 to
a18b8a9
Compare
BenjaminPelletier
approved these changes
Mar 12, 2026
mickmis
force-pushed
the
8/ensurewindingorder
branch
from
a18b8a9 to
86f74b9
Compare
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
2 participants
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.
Fix focagis/geoawareness-cis#8
Issue: linear rings of some polygons in the original ed269 do not respect the right-hand rule as specified by https://datatracker.ietf.org/doc/rfc7946/ section 3.1.6.
With the changes in this PR we ensure that the winding order do respect this rule.
We do so by using the Shoelace formula to determine whether the coordinates are specified clockwise or counter-clockwise, and reverse them if that is necessary.
The output of the converter for the FOCA files generated locally may be found in this gist. Checking manually e.g. the 'GE32' airspace seems to yield correct result.