permitdata.org
permitdata.org copied to clipboard
open-data-standards
:hammer: A website for the BLDS Data Specification
List apps / sites, etc. that use BLDS data. /cc: @chrismetcalf @axtheset @jqnatividad @eddietejeda
How would a permit with multiple parcels be best handled in BLDS? In an extreme example, a single permit for a pipeline that is several miles long crossing hundreds of...
I suggest a generic "Closed" status be added to the list of standard values for StatusCurrentMapped. Some final statuses like "Withdrawn" or "Admin Close" are not appropriate to map to...
Why do fields like AddedSqFt and RemovedSqFt are integers while TotalFinishedSqFt, TotalUnifinishedSqFt and friends are text? shouldn't there be consistency?
StatusCurrentMapped in the core permits data set and StatusPreviousMapped in the permit status history data set seem to refer to the same data right? Shouldn't their allowed values be the...
The scheme should define resource lifecycles and accompanying fields. It should be strict about what modifications trigger a new updated timestamp (hopefully all of them, but it should declare that...
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...
If the minimum bar for providing BLDS is going to be a web-accessible CSV file, we should discuss ways to make those files more discoverable and ideally machine-discoverable. One option,...
In discussing alternatives to the LIVES-style feed_info.csv file, I recommended we take a look at the [CSV on the Web](http://www.w3.org/2013/csvw/wiki/Main_Page) standard. I think it might be a more standards-compliant way...
Why do all the fields have a number 2 attached in the contractor dataset schema? Does this make sense?
Metadata
Owner
Metadata
:hammer: A website for the BLDS Data Specification