Confusing attributes for historical calls
arianmaghsoudnia opened this issue · comments
Hi there and thanks for maintaining this project.
I find using the same one_call.OneCall method to parse responses from historical requests onecall/timemachine a bit confusing because the original DTO has the hourly object as opposed to forecast_hourly. Using the same attribute does not match the original DTO and gives off the impression are the predicted values in the past; whereas those are actual measured values.