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

StreamTemperatureModelling naming conventions #105

Open
debboutr opened this issue Sep 9, 2021 · 1 comment
Open

StreamTemperatureModelling naming conventions #105

debboutr opened this issue Sep 9, 2021 · 1 comment
Assignees

Comments

@debboutr
Copy link
Contributor

debboutr commented Sep 9, 2021

the names in the control tables for each survey need to use the following MetricName titles:

  • TMEAN_PW_<year>
  • TMEAN_W_<year>
  • TMEAN_S_<year>
  • TMEAN_SY_<year> ???

This will also require changes in the StreamTemperatureModelling.Rmd

@debboutr debboutr self-assigned this Sep 9, 2021
@debboutr
Copy link
Contributor Author

debboutr commented Sep 10, 2021

@mhweber @ryan-hill after looking through more of these rasters I think we should really take a moment and clarify what naming convention we want to use. Especially for the MEANSY metric. I always have to think whether that is just the straight year (Jan-Dec) or if it is the months (May - April) like it is in PSUMPY.There seems to be a bit of a loose coupling with these as we have applied them. The data dictionary shows the .bil files for the MAST | MWST | MSST metrics but if you look at the PRISMtmean_2009.tif row, we show the table names to be Tmean<year>(Cat |Ws)

  • prediction code (O:/PRIV/CPHEA/PESD/COR/CORFILES/Geospatial_Library_Projects/StreamCat/FTP_Staging/Documentation/DataProcessingAndQualityAssurance/stream_temperature_prediction_code.html)

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

1 participant