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

No consistency check on price year for exposure data and census data and no user-choice which price year to use. #125

Open
2 tasks done
kathrynroscoe opened this issue Mar 4, 2024 · 0 comments
Assignees
Labels
bug Something isn't working

Comments

@kathrynroscoe
Copy link
Collaborator

Preliminary Checklist

  • I have searched the existing issues list for similar reports and found none. If you did find a similar issue, please add a comment to the existing issue instead of opening a new one.
  • I have verified that the issue exists in the latest version of DelftDashboard and its dependencies. Please update to the latest version and check if the issue still exists.

Severity Level

Low

Steps to reproduce

A user can currently use NSI data, which has a specific price year (we think 2021, to be confirmed), and then choose census data from a different year, without any correction for price-year differences. We'd like to have a user specify a price-year (for example, 2024), and then both the NSI and the census are converted to that price year. This is the same year we should use for our 'current year' when we do cost benefit analysis in FloodAdapt (i.e. this should be passed to the FloodAdapt site toml)

Current behaviour

No consistency between NSI price year and Census year, and no ability for the user to specify a price-year.

Desired behaviour

There are consistency checks and corrections to ensure NSI and Census are in same price-year, and allow the user to select the price year they want to use in FloodAdapt.

Additional context

We will need to have the price-year corrections somewhere

@kathrynroscoe kathrynroscoe added the bug Something isn't working label Mar 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants