A point of uncertainty in the creation of the spatial open data files:
Both spatial opendata tables reference tables that are created in the export step, specifically dcp_attributes_pts, dcp_attributes_poly, and cpdb_projects_combined. I suspect this will cause an issue because these referenced tables will not have been created (as they are all produced via the export step). Proposed refactor involves recreating the creation of these fields (geom, totalspend, maxdate, mindate, typecategory) in the same way they are created in the above mentioned tables rather than referencing those tables directly.
A point of uncertainty in the creation of the spatial open data files:
Both spatial opendata tables reference tables that are created in the export step, specifically dcp_attributes_pts, dcp_attributes_poly, and cpdb_projects_combined. I suspect this will cause an issue because these referenced tables will not have been created (as they are all produced via the export step). Proposed refactor involves recreating the creation of these fields (geom, totalspend, maxdate, mindate, typecategory) in the same way they are created in the above mentioned tables rather than referencing those tables directly.