search

kcigeospatial / balt_co_ETL

This will provide a place to track internal issues around the Baltimore County NPDES NCT application ETL.
0 stars 0 forks source link

ETL - AltBMPPoly.PROJECTED_IMPL_YEAR populated by TREE_INFO.IMPL_YEAR #81

Open dhenry-KCI opened 6 years ago

dhenry-KCI commented 6 years ago

The ETL excel file (v8) indicates that MDE.AltBMPPoly.PROJECTED_IMPL_YEAR will be populated from NPDES.TREE_INFO.PROJECTED_IMPL_YR.

For TREE_INFO record APY000179, NPDES.TREE_INFO.PROJECTED_IMPL_YR = 2015, and NPDES.TREE_INFO.IMPL_YEAR = 2012. The ETL output MDE.AltBMPPoly.PROJECTED_IMPL_YEAR = 2012, so the ETL did not use PROJECTED_IMPL_YR.

Please explain this discrepancy. Is it good logic that was not documented in the ETL excel file? Or is it an error in the ETL script that needs to be corrected?

gerrykelly commented 6 years ago

@dhenry-KCI It's an error that I corrected .... I'm making this same update for IMPERVIOUS_REM>AltBMPPoly also bc I had the same wrong mapping (IMPL_YEAR to PROJECTED_IMPL_YEAR should only be used ANNUAL_PRACTICE_AREAS>AltBMPPoly ) Updated at KCI

dhenry-KCI commented 6 years ago

Confirmed fixed at KCI. Ready for testing at the County