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

[Project Proposal]: UDUNITS javascript library #38

Open
iwensu0313 opened this issue Mar 7, 2024 · 6 comments
Open

[Project Proposal]: UDUNITS javascript library #38

iwensu0313 opened this issue Mar 7, 2024 · 6 comments
Labels
code sprint topic Proposed topic for a code sprint activity wont fix 2024 Topic will not be executed during 2024 event

Comments

@iwensu0313
Copy link

Project Description

This project would explore and pursue ways of offering UDUNITS functionality to front end applications. Depending on expertise and interest, a few methods could be looked at:

Expected Outcomes

A typescript library that can be included in an existing project using npm-install that would allow client side or server side on the fly conversion between units using udunit codes as unit identifiers.

Should include:

  • Proof of concept application that demonstrates conversions
  • Tests that can be run against different cases
  • Helper methods for getting/setting display labels
  • Possible inclusion within ERDDAP mobile app

Skills required

Any of:

  • Knowledge about UDUNITS, including compiling code; ideally someone that understands how configs are put together and is capable of compiling/running existing UDUNITS application
  • Experience or keen interest in creating web assembly from C
  • Typescript/Javascript

Expertise

Intermediate

Topic Lead(s)

akbstone

Relevant links

@iwensu0313 iwensu0313 added the code sprint topic Proposed topic for a code sprint activity label Mar 7, 2024
@mwengren mwengren added the 2024 Topic to be executed during 2024 event label Mar 29, 2024
@abkfenris
Copy link

We've built on top of convert-units for the NERACOOS Mariner's Dashboard. We weren't trying to match UDUNITS, but we'd be willing to upstream any of it's code that is useful to others.

@ocefpaf
Copy link
Member

ocefpaf commented Apr 4, 2024

BTW, in the Python world, it is quite hard to depend on anything related to the udunits2 library and/or any effort to re-write it exactly was abandoned. The most successful MetOcean library that requires units, metpy, uses pint.

TL;DR it may be easier to just reuse something that has the basic units than pursing the ideal 100% unit support in udunits.

@cjolson64
Copy link

Could there be some overlap here with #33? The focus there is on CF standard names but I can imagine a combined library with front end components for CF, UDUNITS, GCMD keywords, NERC, etc.

@MathewBiddle
Copy link
Contributor

@akbstone, @iwensu0313 For this year's Code Sprint, there wasn't a lot of interest in this topic. If it is something you'd still like to pursue during the event, does someone want to take the lead on this topic? If so, please identify who that lead will be. Will this be a topic to execute during the sprint or somewhere else?

Expectations for topic leads: Leads are expected to identify a plan for the code sprint topic, establish a team, and take the lead on executing said plan.

For more information on how topics will be selected see the contributing guide

Otherwise, let's mark it as wont fix 2024 and come back to it later.

@MathewBiddle MathewBiddle removed the 2024 Topic to be executed during 2024 event label May 14, 2024
@iwensu0313
Copy link
Author

@MathewBiddle - we can mark it as wont fix 2024 for this round. Thanks for checking in

@MathewBiddle MathewBiddle added the wont fix 2024 Topic will not be executed during 2024 event label May 17, 2024
@MathewBiddle
Copy link
Contributor

Thanks @iwensu0313. We can always pivot day of.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
code sprint topic Proposed topic for a code sprint activity wont fix 2024 Topic will not be executed during 2024 event
Projects
None yet
Development

No branches or pull requests

6 participants