permitdata.org
permitdata.org copied to clipboard
open-data-standards
:hammer: A website for the BLDS Data Specification
Many jurisdictions issue combination permits which include multiple trades. We should consider adding a type of: - Combination
Why does the inspection dataset has two separate fields for date and time for things like InspectedDate, ScheduledDate and so on? This seems redundant a single date field can normally...
Why do some inspection fields start with "Insp" like InspType, InspTypeMapped and other start with "Inspection" like InspectionNotes? I would suggest to go with the complete word to be more...
Should Yes/No fields like Final and ReInspection be redefined to BOOL type instead of TEXT with Yes/No. This is usually more efficient and friendly to Database Systems and Programming Languages.
Several jurisdictions have contractors licensed in multiple trades. Can we revisit the ContractorTradeMapped field? Could this be a delimited list? Should we have a column for each trade as a...
Why is Fee in the core permits dataset an integer, shouldn't it be numeric to allow for decimal currency values?
I am confused about the schema for the optional contractor dataset. If I understand the description correctly, this table is meant to hold additional contractors for a permit since a...
Explore any federal reporting requirements agencies must do and determine if any additions to the standard could assist with that process.
The optional contractor and permit status changed datasets are a great addition. However, they both have only one required field or column (i.e. PermitNum). Providing a dataset with only this...
If there is not a way to determine New or Existing should we add a value of Unknown or just leave blank?
Metadata
Owner
Metadata
:hammer: A website for the BLDS Data Specification