[Project Proposal]: ERDDAP mobile application

[iwensu0313]

Project Description

This project would build on work completed during the 2019 hackathon in Ann Arbor. Recently, Axiom has updated and deployed an updated version of the ERDDAP mobile application. This project would focus on creating methods for customizing the data included in an application instance, deploying it using github CI (or similar) and customizing the home page as well as overall look and feel (logo, color scheme, labels and descriptions)

Expected Outcomes

Documented ability to create and deploy a customized version of the existing ERDDAP mobile app project. Customizations should include: look and feel, home page content, source ERDDAP, included content within source ERDDAP. Depending on interest and expertise, functional improvements could be made to the application, including: addition of new content types (gliders, habs data, etc), unit conversion, improved unit and parameter labeling.

Skills required

Intermediate skills or keen interest in learning in any of the following:

• React
• D3js
• Google CI deployment process
• Typescript/Javascript

Expertise

Intermediate

Topic Lead(s)

@akbstone

Relevant links

Existing application: https://stage-mobile-erddap.srv.axds.co/stations. Note: Axiom will need to move mobile erddap to github. Shared charts/maps/utilities dependencies are publicly available on npm, but should probably also be moved from internal git to github.

[srstsavage]

@ianbrunjes and I discussed another possible approach for this topic, which would be to federate select station datasets from RA ERDDAP (probably discovered via script from the IOOS catalog?) and use that federating ERDDAP to power the ERDDAP mobile interface. Some of this is similar to what the IOOS Environmental Sensor Map does (discovery of RA sensor datasets and presenting them on a unified map, etc).

[mwengren]

Interested in following the plan for this.

[MathewBiddle]

@akbstone, @iwensu0313, @srstsavage For this year's Code Sprint, 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

[srstsavage]

@MathewBiddle Since Axiom won't be able to attend physically this year we discussed internally and think it's best to defer to other topics for this year. There are plenty of other areas we can contribute to, especially the xpublish/xreds related work.

[MathewBiddle]

Thanks, @srstsavage. I marked this as wont fix 2024 but we can pivot the day of the event if folks change their minds.