uber / uber/h3

h3SetToMultiPolygon -> get the hex indices of the "edge" hexes instead of the polygon

Open
#479 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
6.5k
Forks
627
Avg merge
3d 21h
Merged PRs (30d)
6

Description

Hi, love this library! Any guidance on how to do something similar like h3SetToMultiPolygon, where we are tracing the edges of the active hexes, but instead of returning a multipolygon with x/y coords, we get the hex indices of the hexagons that are on the edge?

Thanks!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the h3SetToMultiPolygon API and related documentation to understand how polygon boundaries are derived from active hexes. Clarify the expected definition of an edge hex and the output API before determining what tests would demonstrate that the requested hex indices are returned.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
data
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.