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 discovered that when using the cellsToMultiPolygon method, a SIGSEGV error can occur if there are duplicate indices in the input array. And this issue was addressed in a recent bug fix.
However, since the cellsToLinkedMultiPolygon method is designed to take a set as input, i think it would be beneficial to add a pre-processing step to ensure the input array has unique elements before calling h3Api.cellsToLinkedMultiPolygon.
Alternatively, there should be at least a comment in the code indicating that the input array must contain unique elements. Additionally, it would be helpful to specify an error code for the H3Exception, as it currently returns only 1.
It was really hard for me to find out the reason for the error 😭
The text was updated successfully, but these errors were encountered:
Changing the signature of cellsToMultiPolygon(Collection<Long> h3, boolean geoJson) to cellsToMultiPolygon(Set<Long> h3, boolean geoJson) will enforce it to not have duplicates, as per definition a set doesn't contain duplicates, and not further change is required in the H3Core to deduplicate anything.
I discovered that when using the
cellsToMultiPolygon
method, a SIGSEGV error can occur if there are duplicate indices in the input array. And this issue was addressed in a recent bug fix.However, since the cellsToLinkedMultiPolygon method is designed to take a set as input, i think it would be beneficial to add a pre-processing step to ensure the input array has unique elements before calling h3Api.cellsToLinkedMultiPolygon.
Alternatively, there should be at least a comment in the code indicating that the input array must contain unique elements. Additionally, it would be helpful to specify an error code for the H3Exception, as it currently returns only 1.
It was really hard for me to find out the reason for the error 😭
The text was updated successfully, but these errors were encountered: