[5pt] ValueError: Object not recognized source of Features (Head bridges)

[RobHanna-NOAA]

In the latest hand_4_6_0_0, over 350 errors saying ValueError: Object is not a recognized source of Features can be found in the all_errors_from_logs.log file.

[mluck]

Here's an example from the log file:

Burn in bridges 17100305 0
Traceback (most recent call last):
  File "/foss_fim/src/heal_bridges_osm.py", line 263, in <module>
    process_bridges_in_huc(**args)
  File "/foss_fim/src/heal_bridges_osm.py", line 132, in process_bridges_in_huc
    lidar_osm_gdf, updated_hand_grid_array = process_lidar_osm(
  File "/foss_fim/src/heal_bridges_osm.py", line 89, in process_lidar_osm
    stats = zonal_stats(
  File "/usr/local/lib/python3.10/dist-packages/rasterstats/main.py", line 52, in zonal_stats
    return list(gen_zonal_stats(*args, **kwargs))
  File "/usr/local/lib/python3.10/dist-packages/rasterstats/main.py", line 178, in gen_zonal_stats
    features_iter = read_features(vectors, layer)
  File "/usr/local/lib/python3.10/dist-packages/rasterstats/io.py", line 136, in read_features
    raise ValueError("Object is not a recognized source of Features")
ValueError: Object is not a recognized source of Features

[RobHanna-NOAA]

If this is considered to be an acceptable error, which we have a good handful of, we have some options.

1. if possible, maybe we can add it to our fim exit status code system so we can easily identify those if we even want to.
2. We don't' even need to record it in logs anywhere if you like.
3. We can change the output message to not have the word "error" in it but change it to the word "warning". Our post processing system looks through all logs looking for the word "error" and "warning"

[RobHanna-NOAA]

Yes. it is an actual error and over 350 HUCs failed at the unit_errors in the hand_4_6_0_0 build. I missed this detail earlier (gulp).