Following the discussion on maximum time frame and area to cover, we've been analyzing the management of valid/useful requests and the corresponding response.

Considering the size of a common request, of 1 week and common areas of around 10Km2, the size of the response's content may be too big for being handled directly in the API REST body.

Proposal

Include a second option for a developer to be able to request a big area,that will receive as response containing a file link instead of a direct content response. That will allow developers to better manage big responses (<1MB) when asking for data of big areas or long time frame.

To discuss the best approach on how to manage both flexibility and speed of a direct response, with more complete data in a filed response.