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
You will be very interested in this. I try this code and the output tables are different depending on whether I used mac or windows:
output <-importNOAA(code = "958960-99999",
year = 1995:2000,
quiet = FALSE,hourly=T) Mac_output_for958960.csv Win_output_for958960.csv
These are the example sites. I also tried out a few other sites and the differences are consistent:
the data download in Windows has "precip" column but this column is not exit in the data table download in Mac.
the precip_6 in windows version was 10 times greater than the values in the table in the Mac version.
I made sure that the package version are the same on both machines. Because I have code running in both machines, it will be great if the output are the same.
In addition, some sites have "precipitation" related columns and some sites don't. It will be nice the downloaded data structure is the same but fill in NA if there is no data. But this is low priority compared to the issue described above.
Thank you!
The text was updated successfully, but these errors were encountered:
Hi David,
You will be very interested in this. I try this code and the output tables are different depending on whether I used mac or windows:
output <-importNOAA(code = "958960-99999",
year = 1995:2000,
quiet = FALSE,hourly=T)
Mac_output_for958960.csv
Win_output_for958960.csv
These are the example sites. I also tried out a few other sites and the differences are consistent:
I made sure that the package version are the same on both machines. Because I have code running in both machines, it will be great if the output are the same.
In addition, some sites have "precipitation" related columns and some sites don't. It will be nice the downloaded data structure is the same but fill in NA if there is no data. But this is low priority compared to the issue described above.
Thank you!
The text was updated successfully, but these errors were encountered: