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

Fix fetching interest by region with CITY resolution #509

Merged
merged 1 commit into from
Mar 26, 2022

Conversation

punchagan
Copy link
Contributor

When fetching interest by region with a CITY resolution, the response doesn't
seem to have the the geoCode column and instead has a coordinates column. This
commit fixes the code to use this column as the geoCode column instead of
raising an error when fetching data with CITY resolution.

Closes #392

When fetching interest by region with a CITY resolution, the response doesn't
seem to have the the geoCode column and instead has a coordinates column. This
commit fixes the code to use this column as the geoCode column instead of
raising an error when fetching data with CITY resolution.

Closes GeneralMills#392
@JettScythe JettScythe mentioned this pull request Mar 21, 2022
@emlazzarin emlazzarin merged commit 0e887b8 into GeneralMills:master Mar 26, 2022
@emlazzarin
Copy link
Collaborator

Thanks!

@punchagan punchagan deleted the fix-no-geocode branch March 26, 2022 17:12
@punchagan
Copy link
Contributor Author

Thanks for the merge, @emlazzarin! It may be worth doing a release with this bug fix, since a lot of people seem to run into this.

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

Successfully merging this pull request may close these issues.

"['geoCode'] not in index" when request CITY LEVEL interest_by_region Google trends
2 participants