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

add unit recommendation from iris validator #76

Merged
merged 2 commits into from
Jan 19, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 18 additions & 2 deletions docs/appendices.rst
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,24 @@ http://docs.fdsn.org/projects/source-identifiers

Unit Naming Rules
===========================================
The FDSN stronly recommends the use of SI unit names whenever possible, which are
defined case sensitively.
The FDSN strongly recommends the use of SI unit names whenever possible. For
details see the SI brochure at:

`<https://www.bipm.org/en/publications/si-brochure>`_

* Use SI units, base or derivative, and their standard symbols whenever possible. Spell out and avoid abbreviations of non-SI units.

* Exponents for powers are specified with `**`, e.g. `s**2`.

* Multiplication is specified using `*` while division is specified with `/`. For example `hit/(cm**2*hour)`.

* Use parentheses sparingly, only when FORTRAN-like precedence would not be correct.

* Unit definitions are singular, not plural, e.g. use `second` not `seconds`.

* Unit names should not mix symbols and full names, use one or the other, e.g. use `m/s` or `meter/second` but not `meter/s` or `m/second`.

* Units should be used case sensitively, using the case specified by SI rules.

In the SEED format all unit names are recommended to be uppercase and
SI when possible. For this reason, some unit documentation and
Expand Down