Open mheadd opened 9 years ago
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?
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.
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?