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
It's actually neither. We just don't have the data in our database for ...BySpecimenDate for the DAs.
We only have recently started to receive the data, but it takes a while for our data team to incorporate it into the pipeline. They will be added in the coming weeks.
Sorry to hijack the thread. The data is for Scotland's council areas are recorded on a day-by-day basis but is volatile. In that, it is only the most recent record that returns any information, even though previous day's data has existed (#6).
@GraemeRMcAllister All cases data that we receive on a daily basis are volatile, which is why they change every day as we process and deduplicate them from 10s of millions of records every single day. The most recent records are usually the most volatile... they tend to settle down after a while.
We are calculating the records by publish date (where one is not provided) from a number of other records (if they are available) to provide a level of consistency. If you need more details, it's probably worth it to get in touch with our data team.
Probably an issue with the backend rather than the python API; not sure where best to report it.
Queries for Scottish areas seem to return only a single record, depending on what is requested in the structure.
I'd expect to get the same number of records regardless of structure metrics. Something to do with None versus 0 perhaps?
The text was updated successfully, but these errors were encountered: