Consistent namings for conversion functions

[Zeitsperre]

Addressing a Problem?

This is a pet peeve of mine, with a very simple (albeit API-breaking) fix.

We currently offer several conversion tools that use the following naming conventions:

• x2x:
  • amount2rate
  • flux2rate
  • lwethickness2amount
  • pint2cfattrs
  • pint2cfunits
  • rate2amount
  • rate2flux
  • str2pint
  • units2pint
• x_to_x:
  • days_since_to_doy
  • doy_to_says_since
  • prsn_to_prsnd
  • prsnd_to_prsn
  • snw_to_snd
  • snd_to_snw
• x_2_x:
  • sfcwind_2_uas_vas
  • uas_vas_2_sfcwind

Potential Solution

We agree on the following conventions:

• xclim.core conversions that are typically used internally use the [a-z]+2[a-z] pattern.
• xclim.indices | xclim.indicators conversions use the [a-z]+\_to\_[a-z] pattern.

Additional context

We can deprecate the sfcwind_2_uas_vas and uas_vas_2_sfcwind conversions now and replace them in the next two or three releases.

Contribution

• I would be willing/able to open a Pull Request to contribute this feature.

Code of Conduct

• I agree to follow this project's Code of Conduct