-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Madison Comparison #68
Comments
There are three big differences in methodology that are affecting these scores. #3 would apply most significantly to the
I also ran the pybna scores using destinations I downloaded from OSM at the time of testing, which means there could have been some variation in the destinations adding to the scoring differences. |
I built some testing capabilities into pybna that allow us to verify the LTS scores on a variety of road conditions. I'm attaching that here for you to reference. As you can see, we went through each possible condition and checked what the score should be based on our LTS chart against what pybna was scoring. We corrected any discrepancies as part of the validation process. This is likely another source of variation if there are any cases where the original was inaccurately rating roads or intersections. We did some testing of the original scores but the new method is far more rigorous and gives me much more confidence that our LTS scores are being accurately applied. (Whether the underlying data is accurate is, of course, an entirely different problem.) |
Here are exports of the two Madison runs. |
* In the past we have discussed a better version of the trails score. I've left it out completely here but it would be easy to add a measure for access to trailheads--which is what we've discussed in the past--as long as it can be taken from OSM.
The text was updated successfully, but these errors were encountered: