Investigate difference in `rs cover` vs `tile-cover` tile list

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by reproducing the comparison between the tile-cover output and the rs cover output for the same geometries, using the reported wc -l counts. Inspect the rs cover entry point and compare its tile list with tile-cover to identify the 982 missing tiles. Done means the discrepancy is explained and, if appropriate, the two tools produce matching coverage.

Written by the indexing model from the issue text.

Description

When generating lists of tile ids covering geometries we are seeing a difference between the tile-cover and the rs cover generated tile ids. For the same geometries:

wc -l /tmp/tile-cover.tiles
116230 /tmp/tile-cover.tiles

wc -l /tmp/rs-cover.tiles 
115248 /tmp/rs-cover.tiles

Our rs cover tool does not include 982 tiles the tile-cover tool gives us. We need to look into this.

Tasks:

  • Figure out difference between tile-cover and rs cover
Dominant language
Python
Stars
2.1k
Forks
385
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/robosat

All issues in mapbox/robosat

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.