8000 h3ToLocalIjk incorrectly succeeds across a pentagon · Issue #163 · uber/h3 · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

h3ToLocalIjk incorrectly succeeds across a pentagon #163

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
nrabinowitz opened this issue Dec 12, 2018 · 0 comments
Closed

h3ToLocalIjk incorrectly succeeds across a pentagon #163

nrabinowitz opened this issue Dec 12, 2018 · 0 comments
Assignees

Comments

@nrabinowitz
Copy link
Collaborator

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):

screen shot 2018-12-11 at 5 49 07 pm

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants
0