-
Notifications
You must be signed in to change notification settings - Fork 9
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
Handle MDU Addresses #11
Comments
Good catch. I can probably add something to it. Prolly won't be able to till thursday sadly. |
So I figured out what needs to be added to speedcheck.py this handles the first part this makes the addesses "Appear this was just a test
This selected the top option of the sub addresses This clicks the button then the rest returns like normal. Like I said won't be able to do more till thursday or so. |
Ill see if I have some time today to integrate the change. |
I have added to code to handle MDU. |
re-opening as the MDU code needs to be updated for the new webservice querying method |
As a starting point, here an example HTTP response for an MDU location:
|
By the way, ATT does have an official MDU map here: https://www.att.com/att/mdu/ Might be able to check people's findings against it to see if it is properly getting them or if we pick up some that aren't on the official map. |
Thanks for sharing the MDU map! In my area I found quite a few other neighborhoods that are not listed on their map. My scans did cover one area they show as well. |
Currently it looks like if a street address has multiple units (e.g. apartment complex), the speedcheck script just marks it as a bad address. It would be great if it could detect this condition and select one of the unit numbers from a list (e.g. just pick the first one would be good enough, they should all be the same), so it can get the real speed offered at MDU locations.
See the attached screenshot for the interstitial page that is inserted for MDUs:
The text was updated successfully, but these errors were encountered: