Visualize street solver
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 58/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- python
- Domain
- data-visualization
Research direction
Start by reading the street-solver output in artifacts/street_solve/candidates.jsonl and artifacts/(tag)/street_solve/candidates.jsonl, and compare it with the georef-street.json sidecar path. Use Washington, DC p127 and p128 plus asheville_ny_1925_vol_1 p45 as visualization examples. Done means street-solve results can be directly visualized even when no sidecar is written.
Written by the indexing model from the issue text.
Description
A georef-street.json sidecar is only written in the (rare) event that the street solver pose is adopted over the RANSAC/snap pose. For all other pages, the only record of street-solve lives in artifacts/street_solve/candidates.jsonl and artifacts/(tag)/street_solve/candidates.jsonl. There's interesting information in this file but no direct visualization of it.
Some examples that could be visualized but don't produce sidecars: Washington, DC p127 and p128.
asheville_ny_1925_vol_1 p45 would also be interesting to look at here due to its curved streets.
- Dominant language
- Python
- Stars
- 16
- Forks
- 2
- Avg merge
- 10h 15m
- Merged PRs (30d)
- 105
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from danvk/mapsnap
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
fit: stale p*.contradiction.json survives clear_derived_sidecars and steers the next run's snapOpenbug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
danvk/mapsnap#258 · 1 comment ·
Maintainers usually reply within 1 day
-
debugger
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Cutline model: is "line found, panels not closed" a large class?Possibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
danvk/mapsnap#565 · 1 comment ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 3 days
-
Negation with "not" and "no" is ignored during sentiment analysisPossibly taken @vivek-3728 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
techcsispit/mess-mood#11 · 1 comment ·
-
changelog investigate
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
ramnes/notion-sdk-py#408 ·
-
good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
btclib-org/btclib-wallet#267 ·
Maintainers usually reply within 1 day
-
good first issue tech-debt
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
knnmelprop/YAADO#111 ·