search

natcap / urban-online-workflow

This repository hosts the beta implementation of the Urban Online ES Workflow. The project is intended to give urban planners the ability to create and assess scenarios using InVEST Urban models.
1 stars 5 forks source link

Urban Cooling: local parameterization of air temperature #87

Open davemfish opened 1 year ago

davemfish commented 1 year ago

For now, these parameters are all hardcoded, but some of them should vary by location. So we'll need to gather some other data to support that local parameterization. See also https://github.com/natcap/urban-online-workflow/wiki/Data-for-InVEST,-by-model#urban-cooling

"cc_method": "factors",
"cc_weight_albedo": "0.2",
"cc_weight_eti": "0.2",
"cc_weight_shade": "0.6",
"t_air_average_radius": "600",
"green_area_cooling_distance": "450",
"t_ref": "35",
"uhi_max": "3.56"
davemfish commented 1 year ago

At first, we should just change t_ref to represent the average August temp for San Antonio. For a future milestone we can parameterize this dynamically for the location.

davemfish commented 1 year ago

Should uhi_max vary with the baseline landcover type? For example, there's a lot of variation across a city like San Antonio seen in this app https://yceo.users.earthengine.app/view/uhimap

So do accurate estimates of cooling depend on getting this uhi_max parameter right for different sites within a city? What do you think @chrisnootenboom

chrisnootenboom commented 1 year ago

Good question! I think taking the city-wide maximum value from the Yale tool is still the best practice, since the InVEST model is trying to recreate the spatial heterogeneity you reference. We know temperatures vary across the city--InVEST takes the maximum and minimum possible temperatures and maps those across the city according to the influence of land cover. If we apply a variable uhi_max, we risk double counting the effect of land cover since we can assume land cover is also driving the heterogeneity in the https://yceo.users.earthengine.app/view/uhimap data.

davemfish commented 7 months ago

We can put this on hold because our application currently only supports sites within San Antonio, and as Chris suggests above, it's okay to use a single, city-wide value for uhi_max and t_ref. No need to set these dynamically unless/until our LULC coverage expands beyond San Antonio.