These changes affect the long-lived capital-planning-flow feature branch.
The zoning-api has an error. The lift field of the community_district table is listed incorrectyl as a multipoint. The correct geometry type is a 'multipolygon'. This will be corrected in the zoning api as part of ticket nycplanning/ae-zoning-api#334.
The capital-planning-flow includes a "patch" to populate the community district 'li_ft' field with multipoint data, instead of multipolygon data. When the zoning-api is updated to have the correct geometry type, the patch should be removed so that the long island state plane data is correctly populated as a multipolygon.
Also, the data-flow database is initialized to have its target tables follow this incorrect structure. The hard-coded SQL used to generate the target tables needs to be updated to reflect the correct type.
Acceptance criteria
[ ] The SQL used to generate the structure of target tables is updated to use multipolygons instead of multipoints for the community district lift field
[ ] The "patch" in the transformation that changes the community district geometry data from a multipolygon to a multipoint is removed
Description
These changes affect the long-lived
capital-planning-flowfeature branch.The zoning-api has an error. The
liftfield of thecommunity_districttable is listed incorrectyl as a multipoint. The correct geometry type is a 'multipolygon'. This will be corrected in the zoning api as part of ticket nycplanning/ae-zoning-api#334.The
capital-planning-flowincludes a "patch" to populate the community district 'li_ft' field with multipoint data, instead of multipolygon data. When the zoning-api is updated to have the correct geometry type, the patch should be removed so that the long island state plane data is correctly populated as a multipolygon.Also, the data-flow database is initialized to have its target tables follow this incorrect structure. The hard-coded SQL used to generate the target tables needs to be updated to reflect the correct type.
Acceptance criteria