When data are densely ingested from sensors, the visualization of all samples on rendering years of data Y1 Y2, Y10 (year) is practially impossible in a reasonable time.
So that, speific aggregated indexes are created at the ingestion phase. On the other hand, in some specific cases, on the API usage and on some specific widget, one would be interested in getting them back and/or even on screen widget for time series. The aggregation can be also disabled by using aggregation=no as parameter.
In those cases, the ASCAPI queries can be forced to provide dense data by using parameter: &aggregation=10-minute
such as:
- https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/M...&aggregation=60-minute
- https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/M...&aggregation=3-hour
- https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/M...&aggregation=1-day
- https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/M...&aggregation=no
https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=
http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/WoodPainting4&fromTime=7-day&valueName=relativeHumidity&aggre...
https://servicemap.disit.org/WebAppGrafo/api/v1/?serviceUri=
http://www.disit.org/km4city/resource/iot/orionUNIFI/DISIT/WoodPainting4&fromTime=7-day&fromTime=7-day&valueName=equilib...
if the data are in the past we suggest to use &fromTime=....&toTime=............
using dates as ISOstrings
-- end --
