Generalize post-processing handlers across zoom levels
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.1k
- Forks
- 385
- PR merge metrics
- No merged PRs in 30d
Description
At the moment we have a parking lot handler tuned with thresholds specifically for zoom level 18:
https://github.com/mapbox/robosat/blob/4cc40914a32443c1358ef7b45451b52298302597/robosat/features/parking.py#L11-L103
Instead what we should do is:
- generalize thresholds and base them on meters
- compute meters per pixel based on the zoom level
Here is how to compute meters per pixel on a specific zoom level:
https://wiki.openstreetmap.org/wiki/Zoom_levels
Tasks
- [x] implement function to compute meters per pixel on a zoom level
- [x] base thresholds on meters
This will allow us to have feature post-processing independent of zoom levels.
Contributor 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.
Research direction
Start with robosat/features/parking.py, especially the linked handler code and the completed meters-per-pixel and threshold tasks. Verify how zoom level reaches post-processing, then confirm that parking feature thresholds are expressed in meters and behave consistently across zoom levels; the issue provides no test path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- computer-vision
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100