As a Open Data Hub Data Consumer I want to see a preview of the x previous day of the time series, to understand how is the trend of the data I'm interested to.

[sseppi]

The idea behind this issue is to activate a small graph to display for example the last 7 days (is just an example of duration of the preview) of each time series.

[sseppi]

In the implementation of this issue we have to consider that we probably have to deal with long uploading times. The user should understand that the Data Browser is loading the data to render the graph and not have perception that there is an error.

The Data Browser must continuously working and not wait for all the data to allow the user navigating the data.

In case of error occurring during the load of the data, only the part which is consuming the loaded data should be deactivated. For more information please see the dedicated issue: #457

[pkritzinger]

@sseppi here you can find a first proposal of the chart. Looking forward to feedback :)

https://www.figma.com/file/DmuP6Dbv5LzkCNOXrDnWIL/2023?type=design&node-id=1775%3A4001&mode=design&t=2kGDcpXSS4qLt0eq-1

[gappc]

@sseppi there seems to be a problem with the API when trying to fetch the data, the request times out.

For example, if I want to fetch the EChargingStation data for just one minute (2023-11-29 12:00:00 to 2023-11-30 12:01:00) I get the error below, although the pagination parameters offset and limit are set. The invoked URL was https://mobility.api.opendatahub.com/v2/flat/EChargingStation/*/2023-11-29T12:00:00/2023-11-29T12:00:01?offset=0&limit=200

Note: I also tried to set the shownull and distinct parameters, but there was no difference in the outcome. Just using whole days as start / end values (e.g. 2023-11-29 to 2023-11-30) also made no difference.

{
    "code": 400,
    "hint": "Query for smaller response chunks. Use SELECT, WHERE, LIMIT with OFFSET, or a narrow time interval.",
    "description": "Query timed out",
    "message": "ERROR: canceling statement due to user request",
    "error": "Bad Request",
    "timestamp": 1701341784884
}

How should we go on with this?