Lines instead of dots?

Open
#22 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

The issue names no files, tests, or entry points. Start by tracing how tile-count represents samples and where its output is rendered, then determine how connected lines should be defined and how GPS error should affect them; done means sparse areas show connected samples without unacceptable visual noise.

Written by the indexing model from the issue text.

Description

Sparse areas of the world would be much better documented if we connected lines between samples instead of just including dots at the samples themselves.

The downside: more visual noise when there is GPS error

Dominant language
C++
Stars
32
Forks
9
PR merge metrics
No merged PRs in 30d

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.

More from mapbox/tile-count

All issues in mapbox/tile-count

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.