utilities/data_conversion /csv2catchmentnetcdf.py fails if 'Time' is name in csv #710
Comments
Ben-Choat
added a commit
to Ben-Choat/ngen_Calib_CFE_TOPMODEL
that referenced
this issue
Jan 18, 2024
Address issue NOAA-OWP#710. In line 79, when parsing the date column, using the dictionary, as was done before this edit, pandas attempts to parse the column at index 0, to a column 'Time'. So, if 'Time' is already a column the error in issue NOAA-OWP#710 is produced. The proposed change assumes column at index 0 is the date column, but works despite the name.
11 tasks
11 tasks
hellkite500
pushed a commit
that referenced
this issue
May 6, 2024
Address issue #710. In line 79, when parsing the date column, using the dictionary, as was done before this edit, pandas attempts to parse the column at index 0, to a column 'Time'. So, if 'Time' is already a column the error in issue #710 is produced. The proposed change assumes column at index 0 is the date column, but works despite the name.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Short description explaining the high-level reason for the new issue.
I needed to convert forcing .csv files to a netcdf forcing and it was failing.
Current behavior
Executing csv2catchmentnetcdf.py fails with ValueError when attempting to convert csv forcings to a netcdf forcing.
'''
ngen/utilities/data_conversion/csv2catchmentnetcdf.py -i forcing -o forcing.nc -j 2
'''
results in:
ValueError(Date column Time already in dict)
Expected behavior
'''
ngen/utilities/data_conversion/csv2catchmentnetcdf.py -i forcing -o forcing.nc -j 2
'''
results in forcing.nc file containing values that were in the cat-##.csv in the /forcing folder.
Steps to replicate behavior (include URLs)
Screenshots
The text was updated successfully, but these errors were encountered: