Idea from GIS team to help in QA ZTLDB and PLUTO minor since they will both be created monthly and pull in the same source data.
there's a QAQC process in place for the ZTLDB that focuses on checking the source data. This process will stay the same.
QA of the PLUTO minor release will focus on confirming that nothing but expected fields changed
One report that may be useful to add is outputting any records where the BBL is the same in both ZTLDB and PLUTO, but the zoning values are different.
Not all bbls that are in ZTLDB will be in PLUTO and vice versa.
If we decide to implement, the next step is to do a quick huddle to outline this.
Idea from GIS team to help in QA ZTLDB and PLUTO minor since they will both be created monthly and pull in the same source data.
there's a QAQC process in place for the ZTLDB that focuses on checking the source data. This process will stay the same.
QA of the PLUTO minor release will focus on confirming that nothing but expected fields changed
One report that may be useful to add is outputting any records where the BBL is the same in both ZTLDB and PLUTO, but the zoning values are different. Not all bbls that are in ZTLDB will be in PLUTO and vice versa.
If we decide to implement, the next step is to do a quick huddle to outline this.