The summary returned at /scenarios route do not include years in key names, instead, it uses popConnectedBaseYear, popConnectedIntermediateYear and popConnectedFinalYear:
|
popConnectedBaseYear: {}, |
|
popConnectedIntermediateYear: {}, |
|
popConnectedFinalYear: {}, |
This doesn't affect the data stored, as it was ingested with year in their property names:
|
entry.summary[`Pop${baseYear}`] = nanParser(record[`Pop${baseYear}`]); |
|
entry.summary[`PopConnected${baseYear}`] = nanParser( |
|
record[`ElecPopCalib`] |
|
); |
|
entry.summary[`ElecCode${baseYear}`] = elecCodeParser( |
|
record[`FinalElecCode${baseYear}`] |
|
); |
This is not an ideal implementation because there will be no way to represent a model with more than two time steps and the data service should account for that.
The files affected by these keys at the Explorer are:
The summary returned at
/scenariosroute do not include years in key names, instead, it usespopConnectedBaseYear,popConnectedIntermediateYearandpopConnectedFinalYear:data-service/app/index.js
Lines 447 to 449 in a66be2b
This doesn't affect the data stored, as it was ingested with year in their property names:
data-service/cli/scenarios.js
Lines 210 to 216 in a66be2b
This is not an ideal implementation because there will be no way to represent a model with more than two time steps and the data service should account for that.
The files affected by these keys at the Explorer are: