[8pt] Hydrotable with row with hydroID but mostly nulls after it

[RobHanna-NOAA]

HydroVIS detected this and for now, it was only detected on one huc and one row in a hydrotable, but it is suspected to be happening more.

The Question:

• In a Hydrotable, it is acceptable to have a row in there with a hydroid but mostly nulls after it? Or is this a bug in our code?
• Is it a quick fix? Should we do a scan of other ones? What is the effort / reward on this fix. PS. I have a way from the HV side to get all records where this can be happening if it is needed, but only if it has value to this problem.

The case found:

This is an image of a HydroVIS join table. If we check the huc and hydroID against our hydrotables, will we see some nulls in that row and should there be any?

HydroVIS has hardcoded put in a temp emergency fix with Derek's blessing to just drop all records when it see's that fix.

At a min, if we can figure out if it is a bug or just an acceptable condition, we can update HydroVIS code to put in a note of why it might happen. If we get a fix and when they get new code, we can tell them to drop that temp hardcoded fix in their code.

More details: Part of a redmine ticket and also recorded in HydroVIS isssue 950.

[CarsonPruitt-NOAA]

This is definitely coming from our side, the number of cells is zero all the way down, so somehow this is a catchment with no pixels?

[CarsonPruitt-NOAA]

This particular hydroid's catchment looks to only be one 10m pixel.

There appears to be at least 5 other hydroids like this one in HUC 04040002. This is a great lake HUC, so I'm sure the lake masking has something to do with it.