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

Minimum Date Range for providing BLDS data #67

Open
mheadd opened this issue Oct 9, 2015 · 2 comments
Open

Minimum Date Range for providing BLDS data #67

mheadd opened this issue Oct 9, 2015 · 2 comments

Comments

@mheadd
Copy link
Member

mheadd commented Oct 9, 2015

Should the standard specify a minimum date range for permit data? In other words, should a minimum of 1 or 2 years of data be required for compliance?

Alternatively, would it make sense to simply specify the time period covered in a data set in the Dataset Information File?

@mikehamel
Copy link

I don't have a strong opinion, but one observation is that when cutting over from one permitting system to another, some communities make a legacy dataset available. If a community lacked the resources to massage their legacy dataset, but wanted to comply day forward with the new system, would they be required to make the legacy dataset comply, and could that be a disincentive to participate?

@mheadd
Copy link
Member Author

mheadd commented Oct 21, 2015

That's an interesting point. One could argue that the jurisdiction should impose requirements on the vendor to ensure that legacy data is extracted from the system being replaced in a way that ensure compatibility with BLDS.

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

No branches or pull requests

2 participants