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

Unable to pull city data #1

Closed
brandonneal opened this issue Dec 26, 2021 · 5 comments
Closed

Unable to pull city data #1

brandonneal opened this issue Dec 26, 2021 · 5 comments
Labels
Bug When something is not quite right

Comments

@brandonneal
Copy link

I am unable to pull my city data however, OWM does see my city on their site.
I get a "Place not found" error.

My city: Lake City, FL
Listed here as Lake City, US
I'm defaulted to Jacksonville when I run without --place

Perhaps allow for selecting location based on location ID, which in my case would be the 4161187 part of the URL.

@Gcat101
Copy link
Member

Gcat101 commented Dec 26, 2021

Please go to https://ipinfo.io/ and send your ip address region data

@Gcat101 Gcat101 added the Bug When something is not quite right label Dec 26, 2021
@brandonneal
Copy link
Author

Sharing my city is one thing but, I'm not too comfortable giving out my IP. I hope you understand.

@Gcat101
Copy link
Member

Gcat101 commented Dec 26, 2021

No, I'm just asking for the city and the county.

@brandonneal
Copy link
Author

Ahh, I misread that

city: "Jacksonville"
region: "Florida"
country: "US"

I know this is why wfetch defaults to Jacksonville, that's why I was trying to do

wfetch --place="Lake City, US"
and was getting
PLACE NOT FOUND.

Gcat101 added a commit that referenced this issue Dec 27, 2021
@Gcat101
Copy link
Member

Gcat101 commented Dec 27, 2021

Fixed + added id support. Update wfetch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug When something is not quite right
Projects
None yet
Development

No branches or pull requests

2 participants