Watel level UI enhancements

[Adelle-Pitsas]

These next few are enhancements not bugs...

New features/behaviors:

• Add vertical line to show current time on plot

Changes to current features/behavior (open to discussion)

• Default time is GMT - do we want to convert to EST?

• For stations with not a lot of difference in benchmarks, it's hard to see the difference in the two levels. the https://water.noaa.gov has this problem too, so it may be a tough one to solve.

• For stations that have a lot of additional data do we want to limit what we show in the station info? Noticed this on a station that had 6-7 variables.

Originally posted by @youngmorse in #2701 (comment)

[Adelle-Pitsas]

• Add fixed height and scroll to sensor dropdown in sidebar

[Adelle-Pitsas]

• refactor "Feet" to "ft" in in side bar to account for "1 Feet"

[abkfenris]

How about we just standardize distance measurements to Smoots?

[youngmorse]

Adding a few new issues/requests that I ran into testing the Next.js viewer in production (with enough resources to be fast!)

• Alpha sort the station list

• Even with alpha sort, the station IDs are mysterious and hard to decipher unless you know them. We may want to consider using Station Name (and maybe ID in parentheses) from the drop down. And use smaller font.

• Similar to the Water Level station list, make sure the Station Name and ID are set up consistently in buoy barn. @youngmorse

• Timeframe bound: If the page is open with station selected, it doesn't refresh the start/end time for forecast/predictions even if you hit the little refresh icon. You have to go to another station and come back. I noticed this looking at the app 9/27 the day after testing 9/26. We've seen this one before I think but I think it's in a different issue.

• Add NAVD88 as datum option (I know we are still figuring this out on the data side, but this should be an option)

• This is more of a data issue, but now that the MD's memory is well-resourced and fast, there is still a real delay (15 seconds or more) in fetching the predicted tide data from the dataset in Sea Eagle. It doesn't seem to improve via caching either. Is the data set too big or unweildy? All the stations (30+) are in one dataset being selected via Buoy Barn constraints. It's 6 minute predictions that go back to 4/1/2023 and 1 year out from current date.

[Adelle-Pitsas]

Adding a few more from NERACOOS Water-level Viewer Repo:

• Somewhere on the dashboard, we need to link to the NWS Eastern Region Coastal Flood Page https://www.weather.gov/erh/coastalflood. Here is a draft text to include
  For official watch, warning, advisory, and forecast information please visit the NWS Eastern Region Coastal Flood Page. This text could go on the open map page but probably should go on each sensor page since some users will likely bookmark their favorite sensor and go directly to it.
• suggestion from Todd - rearrange the list of stations on the right side of the landing page so that they are listed geographically from north to south
• In addition to ordering the list of stations from north to south, consider having a list of regions e.g. Downeast Maine, Western Maine, etc., that have a dropdown with a list of the sensors in that region.
• On each water level station page, provide a link to the NWS page for coastal forecasts.
  In the text box on the left under the water level reading, provide the time of the next forecasted high tide and low tide. Below are a couple of examples.

[youngmorse]

For this issue:

In the text box on the left under the water level reading, provide the time of the next forecasted high tide and low tide. Below are a couple of examples.

I thought we could test this by adding the Coastwatch NOS CO-OPS Water Level Data, High Low Tide Prediction dataset to Buoy Barn that has water level with the High and Low tide variable from Coastwatch nosCoopsWLTPHL. The variables that we need are waterLevel and type (H or L) and we'd need to add a data type in Buoy Barn to understand that type is High Tide or Low Tide.

But we have the same issue with the predicted tide dataset from Coastwatch only giving us data in MLLW. So I think we may need Dylan to add a High Low tide dataset to Sea Eagle and get readings via the NOS API in NAVD88. We may be able to use this dataset with predicted tide for gauges without a nearby harmonic station but we'd only have the high and low readings vs. 6 min or hourly. I'll check on the coverage/available stations.

[Adelle-Pitsas]

From meeting with Tom and Anna 10/25/24 (hopefully to be done by NROC meeting in mid-Nov):

• Clean up names in buoy barn - Ordering of ID vs name, take out tide gauge from names
• Explore smaller groupings of GoM platforms for better intuitive finding of sensors
• Shorten x-axis to 2 days in past, 3 days in future
• Change map icon from squares to circles