natcap.invest (c)logging

Hey Team,
I'm reporting some strange -- but not necessarily unwanted -- behavior related to natcap.invest, logging, jupyter notebooks, and fiona.
I'm doing some pre/post-processing of invest results in a jupyter notebook where I've imported the following:
In my workflow, whenever I make a call to read/write a shapefile using geopandas (which then calls fiona), fiona spews out endless DEBUG messages to the console. It's especially problematic in Jupyter because all those printouts bog down the browser and eat up GB of memory. I noticed this only happens if I have natcap.invest imported.
I've got workarounds, so not looking for a fix, just thought this might reveal some unintended side-effects of how natcap.invest does it's logging. And I know how @James get's excited about logging!
Tagged:
This discussion has been closed.
Comments