Skip to content

BEA Updated their Regional API #33

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

Open
geoffrey-eisenbarth opened this issue Nov 10, 2018 · 1 comment
Open

BEA Updated their Regional API #33

geoffrey-eisenbarth opened this issue Nov 10, 2018 · 1 comment

Comments

@geoffrey-eisenbarth
Copy link

Looks like BEA has finally combined their RegionalIncome and RegionalProduct tables into a single Regional API (see: https://apps.bea.gov/regional/docs/RegionalApi.cfm for more details).

I only use pyBEA for a small portion of my current project, but am quite familiar with the BEA Regional APIs, and might have some spare time soon if you're interested in some help. Any help narrowing down where in the pyBEA code these fixes would occur would be helpful.

Thanks!

@christiejeung
Copy link

Looks like BEA has finally combined their RegionalIncome and RegionalProduct tables into a single Regional API (see: https://apps.bea.gov/regional/docs/RegionalApi.cfm for more details).

I only use pyBEA for a small portion of my current project, but am quite familiar with the BEA Regional APIs, and might have some spare time soon if you're interested in some help. Any help narrowing down where in the pyBEA code these fixes would occur would be helpful.

Thanks!

Not sure where else needs fixing, but updating the hardcoded list of valid datasets in the pybea.py script, function get_data() would be one place to start based on an error I just got. The list is named valid_dataset_names.

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

No branches or pull requests

2 participants