Closed damonmcc closed 9 months ago
this build version is dependent on #102
will send emails to request agency partner data ASAP
Data requests have been made to from agency partners
Received:
@AmandaDoyle - we currently version (in edm publishing) cpdb by date. I'd prefer to use the actual name of the release
Opendata has format of "23pre", "23exec", and "23adopt", so let's go with that?
@AmandaDoyle - we currently version (in edm publishing) cpdb by date. I'd prefer to use the actual name of the release
Opendata has format of "23pre", "23exec", and "23adopt", so let's go with that?
@fvankrieken not sure if you got a reply on this already. I like this idea, but maybe we should save that change for the first 2024 build for consistency in 2023?
revising data dictionary with Capital Planning and GIS to reflect recent changes to columns
(I'm guessing here)
~the latest build of CPDB 23Q4 aka CPDB 23_adopt was from branch fvk-cpdb-fisa-enhancements
and the S3 link to the zipped outputs is here~
Oops sorry - that's the wrong output. Zipped outputs are here
Distributed by GIS on 2/15
The purpose of this issue is to help the team track the tasks that need to occur before kicking off a CPDB update.
Update source data
Read more about who to reach out to and how to update a specific dataset here
Received from agency partner and manually loaded into data libraries
Automatically loaded into data libraries
Before initiating a build of cpdb, verify the latest version in DigitalOcean matches the version in NYC OpenData
Projects
Building and lot-level info
Spatial boundaries
Come from Geosupport update
Other