You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am using the Invest Urban Cooling module and noticed something strange when checking the intermediate results. The cc_park_ini.tif file seems to be calculated using green_area with an exponential distance weighting, rather than using cci. According to the documentation, the formula should be:
This seems to indicate that green_area is being used in the calculation, not cci. Could I be misunderstanding the code? I would appreciate some clarification.
The text was updated successfully, but these errors were encountered:
Hi @GuohuaHu , thanks for bringing this up. I agree that this seems like an error. As it is, cc_park.tif is simply an exponential decay of the green area map, which is a binary mask. It is not a product of cc.tif at all.
For the sample data, cc.tif (cooling capacity) has a range of values from (0.138 - 0.839), while cc_park.tif (allegedly, the exponentially decayed cooling capacity index, due to proximity to green areas) has a range of values from (0.0006 - 0.0041).
This does not make sense to me. @chrisnootenboom or @jagoldstein , would you be able to confirm that the cc_park.tif intermediate results are not logical?
I am using the Invest Urban Cooling module and noticed something strange when checking the intermediate results. The cc_park_ini.tif file seems to be calculated using green_area with an exponential distance weighting, rather than using cci. According to the documentation, the formula should be:
However, after further inspection, I found the following code snippet in the source on GitHub:
https://github.com/natcap/invest/blob/main/src/natcap/invest/urban_cooling_model.py#L524
This seems to indicate that green_area is being used in the calculation, not cci. Could I be misunderstanding the code? I would appreciate some clarification.
The text was updated successfully, but these errors were encountered: