Skip to content
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

Allow pulling data for your current location based on GPS #20

Open
justdave opened this issue Sep 3, 2015 · 4 comments
Open

Allow pulling data for your current location based on GPS #20

justdave opened this issue Sep 3, 2015 · 4 comments

Comments

@justdave
Copy link
Owner

justdave commented Sep 3, 2015

requested by Ben Spears via Play Store review.

@justdave
Copy link
Owner Author

justdave commented Sep 7, 2015

OK, so this turns out to be a hard problem. In order to pull data for a county, I need a three-digit number for the county to give the NWS. These code numbers are pretty much arbitrarily defined (looks like they may have been numbered in alphabetical order in some cases). They have a mapping on their site of county names to code numbers, which the app uses to convert from the county you picked in the settings (the list of counties is also taken from their site, so they match). However I can find nothing for mapping from GPS coordinates to those NWS code numbers. I have found a few free services that'll let me throw GPS coordinates at them and they'll tell me what county those coordinates are in, but I've already noticed a few discrepancies (mostly in semantics or formatting) between the county names returned by those services and the ones in the lookup table on the NWS's website. That means if I use one of these services I'm going to have to make it do some intelligent guessing on which county from the NWS's table is the best match :|

@justdave
Copy link
Owner Author

justdave commented Sep 7, 2015

@justdave
Copy link
Owner Author

And all of the above is no longer necessary. NWS now has direct support for this in their own API. #36 will fix this.

@justdave justdave added this to the Version 2.0 milestone Mar 22, 2020
@justdave
Copy link
Owner Author

Correction, #36 will not fix this, but will make the fix substantially easier to implement. :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant