-
Notifications
You must be signed in to change notification settings - Fork 49
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
cfunits package confusion #89
Comments
See also: #30 (comment) |
@pelson What do you propose we do about this confusion? Or are you just highlighting that the cfunits package is similar, but different. Or are you hinting that we should allow a way for users to add their own custom units? 🤔 |
I'm proposing that we try to bridge the gap - there is no good reason for two CF units type packages IMHO. At the very least, we should recognise the other in our README, and highlight some of the pros/cons of each (I don't know what they are at this point, hence my probably naive "no good reason" statement 😉). |
Related: NCAS-CMS/cfunits#17 |
@rcomer This link seems to reject the difference as not worthy of talking about. In fact, just the fact that this project thinks it is worth a few sentences was encouraging to me. Does anyone know both well enough to say whether there a difference in how configurable/changeable the list of units is, or is this an xml edit in either library? One issue I have is that I am in a community that uses particular conventions for going between mhos or Siemans and practical salinity units. At low salinities it includes adjustments for things like agricultural salts. So, to replace tools we have I would need this to be possible and I need to be able to specify my own custom function to do it. Do the above changes get me closer to where I want to go or is hard because I want to interject a nonstandard unit plus a new conversion? I'm understand there are several larger questions at play and I will caveat my projects accordingly. |
Note : this does deserve some consideration, at least to answer the above question about defining custom units |
The cfunits package is extremely similarly named to this one, and apparently has a purpose in common.
In particular, one major difference is cfunits' changes to the standard udunits definitions:
The text was updated successfully, but these errors were encountered: