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
I really appreciate the schema file and consistent CSV file formats, and I assume it's unintentional that a few TYRain* CSV files have a different number of columns. Looking at TYRain*.csv files in the DATA directory, most have 13 columns (with the last one being empty).
Files with 12 columns:
DATA/WARINGSTOWN-THE-FORGE/TYRain_1920-1930_37_pt1-page-130.csv
Files with 11 columns:
DATA/CWM-ORTHIN/TYRain_1941-1950_27_pt1-page-108.csv
It's not a big deal, of course, but it does add extra handling to otherwise straightforward bulk import and concatenate operations.
The text was updated successfully, but these errors were encountered:
Thanks. That is unintentional - will try and fix these.
The main data files to be used are those which have concatenated the various TYRain*csv files together into one or more gauge series. These have the same name as the folder.
Do you mean the ALLSHEETS directory? I tried those first, and the import was cleaner, but they seem to have more data quality than the DATA files. For instance, the DATA has much fewer monthly values at and over 100 inches.
I really appreciate the schema file and consistent CSV file formats, and I assume it's unintentional that a few TYRain* CSV files have a different number of columns. Looking at TYRain*.csv files in the DATA directory, most have 13 columns (with the last one being empty).
Files with 12 columns:
Files with 11 columns:
It's not a big deal, of course, but it does add extra handling to otherwise straightforward bulk import and concatenate operations.
The text was updated successfully, but these errors were encountered: