CityScope / CS_Urban_Indicators

Scripts for getting urban data and building urban indicators. A module for computing urban indicators in response to real-time CityScope inputs.
GNU General Public License v3.0
7 stars 4 forks source link

Benchmark #5

Open LAAP opened 4 years ago

LAAP commented 4 years ago

Are we going to have a Benchmark like in Volpe? Which one? Barcelona, Volpe, a synthetic one based in North American cities...?

doorleyr commented 4 years ago

There is now a front-end issue which includes handling of multiple scenarios on the indicators plots (eg. current vs benchmark or baseline).

We need to decide how to handle this information in the module. In the Corktown project, the reference scenario will be the baseline i.e. calculations based on data for the existing site with all geogrid cells set to None. (in another project, the reference scenario could be a different district).

Maybe each indicator needs to have a function: calculate_baseline() which outputs the baseline indicator values for that district (either by reading and analyzing baseline data or by reading data produced manually etc.). Then we would pass a parameter to the Handler indicating whether the baseline values should be included with each indicator. @crisjf what do you think?

crisjf commented 4 years ago

That sounds good. Let's not pass the parameter though, let the Handler take care of it by checking if the user has defined the calculate_baseline function.

Given how the Handler behaves, the calculate_baseline function can return a dictionary with multiple scenarios. Something like:

def return_baseline(self):
    barcelona = 1
    paris = 2
    return {'baseline': paris, 'benchmark': barcelona}
crisjf commented 4 years ago

commit 784f3b12f61fa1f2b83c2bb54153495549f808b0 adds placeholder return_baseline function to Indicator class. The Handler class still does not know what to do with the return_baseline function.