As noted in quite a few other questions, US county and city level data was discontinued starting 2020-03-10 and replaced by state level data. (in California, at least; I haven't looked at other states; possibly in other countries as well?)
However, the county and city locations report zero for dates since then. These are not true zeros, these are missing data. NULLs in relational database parlance.
Worse yet, now that we know that zeros at least sometimes represent missing data, what about other zeros, especially earlier ones? How do we know whether a zero is a true zero, or indicates missing data?
Please, could a missing data code be introduced? It is essential to distinguish between real data and missing data.
For my own applications, simply omitting the zeros between commas in the CSV files would work, or a code such as -9999 could be used instead of zero.
As noted in quite a few other questions, US county and city level data was discontinued starting 2020-03-10 and replaced by state level data. (in California, at least; I haven't looked at other states; possibly in other countries as well?)
However, the county and city locations report zero for dates since then. These are not true zeros, these are missing data. NULLs in relational database parlance.
Worse yet, now that we know that zeros at least sometimes represent missing data, what about other zeros, especially earlier ones? How do we know whether a zero is a true zero, or indicates missing data?
Please, could a missing data code be introduced? It is essential to distinguish between real data and missing data.
For my own applications, simply omitting the zeros between commas in the CSV files would work, or a code such as -9999 could be used instead of zero.