QA: "nearby sidewalks" detection range too large / mark issue as "wont fix"

[tordans]

With the possible separate sidewalk QA layer there are quite a few cases like below where the sidewalk that is referenced is way to far away.

How could this be improved?

• Shorter detection radius?
• Could we add the "crosses building" logic from this other PR recently so only sidewalks that are "in line of sight" are candidates?
• Maybe we just need a "wont fix" action to handle those false positives in the UI easily, so Users can click and continue until the list is at 0 … – see QA: Filter hw=service for "possible separate sidewalk" case #99

Example:

https://a-b-street.github.io/speedwalk/#16.08/52.793421/13.281368