You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on the h3Line algorithm (#162), and my tests are running into issues when crossing a pentagon onto an adjacent base cell. The following image shows the results of h3ToLocalIjk from the res 3 cell 1, 0, 0 (next to the 0, 0, 0 pentagon):
This takes a k-ring of 12 and shows only cells with valid coordinates from h3ToLocalIjk. The cells on the failing sides of the pentagon on the same base cell are excluded, but cells on the adjacent base cell across the pentagon are included (incorrectly, I believe).
Looks like the reason for this are the Class III checks here. In the same-cell branch, both FAILED_DIRECTIONS_II and FAILED_DIRECTIONS_III fail, but in the cross-cell branch they depend on Class III status. Is there a reason for this? This pentagon is base cell 4, which seems to have a few special properties (no CW offset rotation faces in baseCellData), but I'm not sure if that's relevant here.
The text was updated successfully, but these errors were encountered:
I'm working on the
h3Line
algorithm (#162), and my tests are running into issues when crossing a pentagon onto an adjacent base cell. The following image shows the results ofh3ToLocalIjk
from the res 3 cell1, 0, 0
(next to the0, 0, 0
pentagon):This takes a k-ring of 12 and shows only cells with valid coordinates from
h3ToLocalIjk
. The cells on the failing sides of the pentagon on the same base cell are excluded, but cells on the adjacent base cell across the pentagon are included (incorrectly, I believe).Looks like the reason for this are the Class III checks here. In the same-cell branch, both
FAILED_DIRECTIONS_II
andFAILED_DIRECTIONS_III
fail, but in the cross-cell branch they depend on Class III status. Is there a reason for this? This pentagon is base cell 4, which seems to have a few special properties (no CW offset rotation faces inbaseCellData
), but I'm not sure if that's relevant here.The text was updated successfully, but these errors were encountered: