cyclestreets / cyclestreets/cyclescape
External data browsing (e.g. collisions) viewing should be available for all slippymap views
Nobody has claimed this yet.
- Dominant language
- PLpgSQL
- Stars
- 34
- Forks
- 15
- PR merge metrics
- No merged PRs in 30d
Description
All instances of the slippymap should have the external data views.
(At present the only such layer is the collisions layer, but CycleStreets Photomap (see issue #213) browsing, is proposed as another. More may be added in future.)
Currently the external data layer only appears on an issue page, like /issues/805-holyrood-crescent-to-butterfield-lane but is not present on its component thread(s) pages, i.e. /threads/1000 .
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
Compare the issue-page view at /issues/805-holyrood-crescent-to-butterfield-lane with the component-thread view at /threads/1000, focusing on how the collisions layer is exposed. Done means external data views are available across all slippymap instances, including thread pages and future layers such as CycleStreets Photomap.
Written by the indexing model from the issue text.
Assessment
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100