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

Modelled Stream Temperature for NRSA 1819 and 2000/2004 #89

Open
mhweber opened this issue Jul 12, 2021 · 7 comments
Open

Modelled Stream Temperature for NRSA 1819 and 2000/2004 #89

mhweber opened this issue Jul 12, 2021 · 7 comments
Assignees

Comments

@mhweber
Copy link
Collaborator

mhweber commented Jul 12, 2021

Use existing code (L:\Priv\CORFiles\Geospatial_Library_Projects\NRSA\NRSA13_14_FinalTables\StreamTempCalibrationFiles) to generate modelled stream temperature for NRSA 1819 and WSA/WEMAP 2000/2004 NRSA data same as we've done and published in StreamCat for NRSA0809 and 1314.

@debboutr
Copy link
Contributor

debboutr commented Aug 31, 2021

the 08/09 && 13/14 survey years stream temperature modelling have not been updated after all of the surveys were remade and need to be included in this ticket.

@debboutr
Copy link
Contributor

TMEANSY_<year>.tif vs. PRISMtmean_<year>.tif raster conflict

making the data here I've found that there is a bit of a legacy issue, it seems that we have moved to making the full year tmean rasters in the PRISMtmean<year>.tif whereas the script for the StreamTemperatureModelling was written to use the TMEANSY_<year>.tif raster. I think these are essentially the same, but want to make sure.

@mhweber
Copy link
Collaborator Author

mhweber commented Aug 31, 2021

That should be the same - I prefer the naming convention TMEANSY_.tif

@debboutr
Copy link
Contributor

looks like we already have it published with PRISMtmean as table PRISM_0809, do you want me to update this or just follow the same convention for all the other years??

@mhweber
Copy link
Collaborator Author

mhweber commented Aug 31, 2021

Well, I prefer naming convention of TMEANSY_, but we can follow convention we've already published. We just need to be explicit in our published tables, metadata what the name means, but if easier can just stick with that.

@debboutr
Copy link
Contributor

debboutr commented Aug 31, 2021

looks like Ryan had added the 2 PRISMtmean_2008.tif and PRISMtmean_2009.tif into QAComplete, we could just use the same FinalTableName for these and then I can just flip the LandscapeLayer value?

we have these TMEAN_S_<year>.tif and TMEAN_W_<year>.tif, what is the S in TMEANSY_<year>.tif supposed to mean?

I was looking through the code thinking that this was a yearly raster but dating from May (05) of the previous year to April (04) of the current , like we do with PSUMPY, cause these would be a different product in this case, but as I read it it is just a reprojected yearly prism raster

@mhweber
Copy link
Collaborator Author

mhweber commented Aug 31, 2021

The specific months for each of those variables are spelled out in the data dictionary - we need to make sure we align and adhere to the data dictionary - very key! The 'S' in TMEANSY stands for 'same' - i.e. 'same year'. Others in this category are 'PW' = 'previous winter', 'SS' = 'same summer' - but the formula and specific months are shown in the label column in the data dictionary.

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

No branches or pull requests

2 participants