You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We decided on not storing aggregations in the DB, but dynamically compute them when requested for this we added the aggregations parameter to the infectiondata-query.
The query object should look like this:
{
"aggregation1": [
"Inf",
"V2"
]
}
Where the first key is an arbitrary name for the aggregation that holds a list of compartment tags.
The backend querys the data and calculates the sum of all compartments containing the tags (AND connected).
The response will then contain datapoints with the aggregation name and no compartment.
FastAPI currently does not support deepObjects as query parameters but the feature is in planning.
When fastapi/fastapi#9867 is merged we can add in aggregations as deepObjects.
Alternatively a custom serialization may be possible, acting as a string query parameter.
The text was updated successfully, but these errors were encountered:
We decided on not storing aggregations in the DB, but dynamically compute them when requested for this we added the aggregations parameter to the
infectiondata
-query.The query object should look like this:
Where the first key is an arbitrary name for the aggregation that holds a list of compartment tags.
The backend querys the data and calculates the sum of all compartments containing the tags (AND connected).
The response will then contain datapoints with the aggregation name and no compartment.
FastAPI currently does not support deepObjects as query parameters but the feature is in planning.
When fastapi/fastapi#9867 is merged we can add in aggregations as deepObjects.
Alternatively a custom serialization may be possible, acting as a string query parameter.
The text was updated successfully, but these errors were encountered: