Visualize street solver
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 12
- Forks
- 2
- Avg merge
- 13h 21m
- Merged PRs (30d)
- 98
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.
Contributor guide
No contributing guide indexed for this repository
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.
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.
Assessment
- Tech stack
- python
- Domain
- data-visualization
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 58/100