Open martincollignon opened 4 years ago
Any idea on how to factor that in in relation to the other factors that are already used?
Currently
const bookingClassWeightingFactor = (bookingClass, isShortHaul) => {
// TODO(bl): use constants in sources to improve matching probability
switch (bookingClass) {
case 'business':
return isShortHaul ? 1.26 : 1.54;
case 'first':
return 2.40;
default:
return isShortHaul ? 0.960 : 0.800; // assumed economy class by default
}
};
is used, which creates a multiplier for emissions associated to a flight. Should we set this factor as 0.766 for economy for long haul vs 2.221 for business for long haul for example?
Just a note: we currently don't have any way to describe seating class in our activity model. Furthermore, we don't have planned any UX input changes nor do we have any integration that has awareness of the seating class. I think this should be considered as a part of a feature that includes the UX? Else it won't be visible anywhere.
Finally, what is the improvement targeted here? We already have business class and first no? Thanks for looking into this though!
Yes indeed, I'm just going through the issues to see where I could help while my scripts are running. So I'll let @martincollignon detail whether this issue should stay open or not
From https://assets.publishing.service.gov.uk/government/uploads/system/uploads/attachment_data/file/829336/2019_Green-house-gas-reporting-methodology.pdf page 80