a-b-street / a-b-street/speedwalk
QA: Cleanup (missing) crossing ways(?)
- Dominant language
- Svelte
- Stars
- 24
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
## Case
When sidewalks are mapped separately, it is not uncommon that the are missing separate way segments for the crossing. In those cases, the part of the crossing across the street is also just a sidewalk (or path, …)
## Question
We talked about this as a QA step, but I wonder if it is actually needed…
For the analysis that we are planning, we will look at the intersection points, rather than the crossing-ways.
It is a good QA step to create clean OSM Data, of course. But it is not crucial to generate and analyse a foot network, IMO. Right?
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue discusses whether missing crossing ways in OSM sidewalk data is a necessary QA step for network analysis. To understand the context, examine the code that processes OSM data for foot networks, likely in modules handling OSM import or network generation. Look for existing QA steps or validation logic. Determine if the analysis uses intersection points rather than crossing ways, as mentioned. The goal is to clarify the necessity of this QA step for the project's objectives.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100