Similar to manual loading of checkbook nyc data, we should load historical cpdbs used in db-checkbook project.
While we push these to the publishing bucket and could grab them from there programmatically, those don't have the explicit versioning we would like (preliminary vs exec vs adopted), so longer term it would make sense to grab them from bytes. However, cpdb was only added to bytes in the last few years. So for historical ones used in the exploratory project grabbed from carto, they should just be loaded manually (local file as input for data library), and then after archival implement something longer-term pulling from bytes. So to do this:
[ ] create a working yaml for a manual upload.
name I think should be dcp_cpdb (@damonmcc if this specifically is the shapefile, maybe dcp_mapcpdb? By the pluto naming approach. I would lean just the former though.
Similar to nycoc_checkbook, there will be a url defined for the source for the file in maybe library/tmp
you'll need to specify srs and geom for source and dest - I would say keep them the same
[ ] load the files used in checkbook project. Outputs should probably just standard pgdumps, though feel free to do csvs too if you were using them. Versions should maybe be `{year}{type}as in2017_adopted`. This must be specified during the command line call to library archive.
[ ] Submit PR and merge to main with manual loading yml file
[ ] update yml file to pull from bytes (and test, submit pr, merge). dcp_colp is another dataset pulled from bytes
Similar to manual loading of checkbook nyc data, we should load historical cpdbs used in db-checkbook project.
While we push these to the publishing bucket and could grab them from there programmatically, those don't have the explicit versioning we would like (preliminary vs exec vs adopted), so longer term it would make sense to grab them from bytes. However, cpdb was only added to bytes in the last few years. So for historical ones used in the exploratory project grabbed from carto, they should just be loaded manually (local file as input for data library), and then after archival implement something longer-term pulling from bytes. So to do this:
dcp_cpdb(@damonmcc if this specifically is the shapefile, maybedcp_mapcpdb? By the pluto naming approach. I would lean just the former though.urldefined for the source for the file in maybelibrary/tmpas in2017_adopted`. This must be specified during the command line call to library archive.