Closed AmandaDoyle closed 1 year ago
make sure geosupport is updated to 23a
re geosupport: I noticed builds failing in the docker-geosupport repo and oppeed this issue for it: https://github.com/NYCPlanning/docker-geosupport/issues/24
but I'm not sure how related that is to your comment above @mbh329
My comment was just a reminder to use the new 23a release of geosupport in response to an email lynn and AD sent @damonmcc
The issue template needs to be updated fyi. I think maybe we should close this issue and I can open up a PR fixing the issue template or I can just leave comments and put a pin in the updated issue template @damonmcc @AmandaDoyle
Closing this @AmandaDoyle @damonmcc. New issue open #618
Update code
Update source data
Make sure the following are up-to-date in recipes:
dcp_mappluto
dof_shoreline
updated with zoningtaxlots, safe to ignorecouncil_members
check opendatedoitt_buildingfootprints
check opendatadoitt_buildingfootprints_historical
check opendatadoitt_zipcodeboundaries
-> never changed, safe to ignoredoe_school_subdistricts
-> received from capital planningdoe_eszones
-> the url for this changes year by year, search on opendatadoe_mszones
-> same as abovehpd_hny_units_by_building
check opendataDCP Admin Boundaries from Bytes
dcp_cdboundaries
dcp_cb2010
dcp_censustracts
dcp_school_districts
dcp_boroboundaries_wi
dcp_councildistricts
dcp_firecompanies
dcp_policeprecincts
DOB data
dob_cofos
-> manually updated, received by emaildob_jobapplications
check actionsdob_permitissuance
check actions