P2.4 two-hole arrangement (OV-P2 / Bar 2) - #19
Open
grootstebozewolf wants to merge 2 commits into
Open
Conversation
Walk two crossing hole rings with the existing noder (two line-line nodes, no shared run) and assemble CAP/CUP/SUB/XOR. H-SHELL-HOLE-X is exact; snap-rounding was not required. Co-authored-by: Jeroen Bloemscheer <grootstebozewolf@users.noreply.github.com>
Co-authored-by: Jeroen Bloemscheer <grootstebozewolf@users.noreply.github.com>
This was referenced Aug 16, 2026
grootstebozewolf
marked this pull request as ready for review
August 16, 2026 12:49
This was referenced Aug 23, 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.
Stacked on
cursor/p23-bite-vs-hole-3909@ 7a3a4fb (draft #18). Do not merge this into #7. This is OV-P2 / Bar 2, not OV-P1. Does not merge #12 / #13 / #15 / #16 / #17 / #18 / #7. Does not push tofeature/sfa-curve-rgror master.Sentence
The noder is the named-miss suite, one assembly rule at a time. Nodes (P2.1), overlap-as-edge (P2.2), bite vs hole (P2.3), then two-hole arrangement. Densify is never a noder. Snap-rounding is not this rung.
What this is
P2.4 is the next face walk after P2.3, and only this cell:
H-SHELL-HOLE-X — two holes that cross.
Same
HALF_DISCouter. Two axis-aligned unit squares:(0 1, 1 1, 1 2, 0 2, 0 1)(0.5 0.5, 1.5 0.5, 1.5 1.5, 0.5 1.5, 0.5 0.5)They overlap in
[0.5,1] × [1,1.5]. The Geometry-level noder still returns null (the pair has holes). The hole rings are LineStrings: P2.1 names the two crossing nodes(0.5 1)and(1 1.5). No shared run (P2.2 edges empty). No circular–circular hole hits. Snap-rounding was not required.Face assembly is a 3-ring arrangement (shared circular shell + two hole rings). Package-private
TwoHoleOverlaywalks each hole in and out of the other withCurveSegmentString/CurveSegmentNoder/TwoNodeClip, then:12.5π − 1.7512.5π − 0.250.751.5Exact,
isApproximate()=false. Decide / clip-node pins sit next to the overlay pin. No new public API. No noder injts-core. Name is OverlayNGCurve. P2.5 / N-SS was not started.Lasering vs stamped
assertNull.assertNull. This fixture did not need them.What this is not
SegmentString/Noderin jts-core)feature/sfa-curve-rgr/ PR SFA/SQL-MM curve awareness: Curve rename, arc-aware operations, OverlayNGCurve ratchet (#1195 RGR series) #7 / locationtech masterVerify
All green after this revision:
CurveSegmentStringTest16 / 0 (hole-ring nodes(0.5 1)/(1 1.5); Geometry-level pair still null;BiteVsHole.MISS;TwoHoleOverlay.CROSS)CompoundCurveShellOverlayTest26 / 0 (HOLE-X CAP/CUP/SUB/XOR exact; HOLE-CROSS / SAME-OUTER / DIFF-OUTER / HOLE-OUTER / MIXED unchanged)CircularArcOverlayTest11 / 0CircularDiscOverlayTest12 / 0CircularDiscPolygonOverlayTest7 / 0CircularLineOverlayTest7 / 0OverlayNGCurvePhase0Test19 / 0OverlayNGCurveRatchetTest48 / 0 (two-hole cross EEEE both orders)OverlayNGCurvePerfGateTest82 / 0 (15% slack)jts-curvesucceededSlack stays 15%. Overlay name is OverlayNGCurve. No new public API. No noder was written in jts-core. P2.5 / N-SS was not started.