Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C climix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • climix
  • climix
  • Issues
  • #179

Closed
Open
Created Mar 27, 2020 by Lars Bärring@a001257Developer

tasmidpoint as standin for tas

The well established indices were developed within the observational data communities. And in that context daily mean temperature, as in tas: cell_method = "time: mean", brings about a lot of complications (given the limited and shifting observation times). Hence they settled for the draconian solution that daily mean temperature is defined as (TN+TX)/2, which in terms of CF would be tas: cell_method = "time: midpoint (assuming that the time bound specify daily data!), where tas should have another name, such as tasmidpoint.

We should have the possibility to compute tas-based indices on tasmidpoint, which then should be calculated on the fly as if input data had been specified as low_data: tasmin, high_data: tasmax

Edited Mar 27, 2020 by Lars Bärring
Assignee
Assign to
Time tracking