Access Score Calculation So Inaccurate as Not to Be Useful

[jonfroehlich]

Case in point--look at how many surface problems there are in Hill Crest and yet it still receives a good accessibility score. It's a bit embarrassing that it's marked as 99 out of 100 on our accessibility scale.

In the short term, I think we should emphasize that Access Score is in beta somewhere in the text. In the longer term:

• I think we should make our access score algorithm more transparent. We should literally have a link to a page that describes our calculation/algorithm for this
• We should obviously improve this formula (@manaswis is currently working on it)
• We need to add other elements like road grade and elevation changes along a street segment

[manaswisaha]

PR #361 Short-term solution:

[jonfroehlich]

This continues to be rather embarrassing to be honest. I think we need to discuss whether we want to take down Access Score until the load times are better and, just as importantly, the access score model is improved. Check out the sheer number of orange 'Surface Problem' labels in Hillcrest and yet, it is rated as 99 'Very Accessible.' We can and should do better.

[misaugstad]

do we want to take this down, leave it as-is, or make any updates to it this summer?

[jonfroehlich]

Is this now the results page? Can you send a URL for me to check it out?

[misaugstad]

No, this is at the /demo endpoint, it was actually using accessscore, unlike /results I believe.

https://sidewalk-newberg-test.cs.washington.edu/demo

[jonfroehlich]

This is actually related to @johnsonkuang's summer project. We should have a discussion.

[jonfroehlich]

Tagging @crescendochu so she sees this.