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

NSI data API to IN-CORE building inventory dataset #49

Open
jonglee1 opened this issue Aug 31, 2022 · 0 comments · May be fixed by #95
Open

NSI data API to IN-CORE building inventory dataset #49

jonglee1 opened this issue Aug 31, 2022 · 0 comments · May be fixed by #95
Assignees
Labels
2storypoints Between 2-6 hours of work, requiring email and/or a brief meeting feature New feature

Comments

@jonglee1
Copy link
Contributor

  1. develop a database of NSI data (in IN-CORE building inventory dataset TYPE)
  2. develop a API to acquire the bldg inventory with user's given area (either boundary polygon, or FIPS code)
  3. develop pyincore-data method to acquire the bldg inventory with API from step 2
@jonglee1 jonglee1 added the feature New feature label Aug 31, 2022
@longshuicy longshuicy added 5storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models 8storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models and removed 5storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models labels Feb 24, 2023
@ywkim312 ywkim312 self-assigned this Jan 8, 2025
@ywkim312 ywkim312 added 2storypoints Between 2-6 hours of work, requiring email and/or a brief meeting and removed 8storypoints Between 16-24hrs, may involve chainings, new pipelines, very complex models labels Jan 8, 2025
@ywkim312 ywkim312 linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2storypoints Between 2-6 hours of work, requiring email and/or a brief meeting feature New feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants