Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSV file consistency: number of columns #2

Open
xangregg opened this issue Feb 19, 2023 · 2 comments
Open

CSV file consistency: number of columns #2

xangregg opened this issue Feb 19, 2023 · 2 comments

Comments

@xangregg
Copy link

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/BROUGHAM/TYRain_1910-1919_22_pt1-page-216.csv
  • 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.
@ed-hawkins
Copy link
Owner

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.

@xangregg
Copy link
Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants