Consistence between startDate & endDate attributes in response and request #52
Description
Problem description
Any reason why we have startDate and endDate in the request and then startTime and endTime in the response (class TimedPopulationDensityData)
In both case it is a datetime
Expected behavior
Use same attribut name?
Alternative solution
Additional context