Closed mgraber closed 4 years ago
I'm thinking we don't have to output housing_input_research? the only place where housing_input_research would change is adding bistest records. since HED is ok with removing them directly, housing_input_research will not change
I'm thinking we don't have to output housing_input_research? the only place where housing_input_research would change is adding bistest records. since HED is ok with removing them directly, housing_input_research will not change
Don't they need to be able to add to it or modify it?
If it's all the same to you, I think you should give us the manual inputs table to confirm that we have the same version that you are using. I would hate to have any confusion on that front.
@AmandaDoyle @mgraber @SPTKL Tables 1b and 2b (csv for records without a geometry) should be unnecessary. Records without a geometry will be captured in the QAQC table, and 100% geocoded by HED. Therefore, the final output should never include records without a geometry.
173
174
Since the refactor, the package of tables we need to deliver for review is slightly different. What tables need to get delivered for HED to perform their manual review?
Developments database in new schema as outlined in this spreadsheet a. Csv for all records b.
Csv for records that don’t have a geometryc. Shapefile for records that have a geometryHousing database, which is a subset of DevDB a. Csv for all records b.
Csv for records that don’t have a geometryc. Shapefile for records that have a geometrySix aggregate tables as 6 separate tables
QAQC outputs a. FINAL_qaqc table as csv b. HNY_no_match table as csv
Corrections files a.
CORR_hny_match
b.housing_input_research
aka manual corrections table