anstosa / ferry.fyi Goto Github PK

OS: iOS 15.3.1
Browser: Safari (home screen)
Repro Steps:

1. Open https://www.ferry.fyi on iPhone Safari
2. Click the share icon from the url bar
3. Click "Add to Home Screen"
4. Open the page from the added home screen button
5. click any location to display footer menus

Footer menu style is broken when the page is loaded from the iPhone home screen. It looks fine when it is opened on a regular safari tab or other browsers. I did a little debugging and it looks like the env(safe-area-inset-XXXXX) values break the style.

Overwriting values to 0 on margin bottom on the Footer and the padding top and bottom on the child fixes it.

It might need to use a media query of [display-mode: standalone](https://developer.mozilla.org/en-US/docs/Web/CSS/@media/display-mode) to make the spacing values conditional.

Better loading screen while data and estimates are loaded for new dates

TBD

https://capacitorjs.com/docs/plugins/ios

To repro

1. Select Seattle -> Bainbridge
2. Tap the right hand menu, then tap on the bottom half of the text ("Bremerton")

Expected
Shows Seattle -> Bainbridge

Actual
Tap is not detected (due to gradient overlay at bottom of menu)

• Swipe left to open/close menu
• Swipe down to close flyups
• Swipe down to close notificatitons

Unclear what's going on here. VesselWatch is up, so it doesn't appear to be a WSF outage.

Use TesseractJS to read text off cropped bottom of images on server. Send updatetime to clients

Wanted to check this out and run it locally to see how it works, trying to create a similar UI for work shuttle arrivals. Ran into a few issues, following the README instructions verbatim:

1. Font Awesome token is missing

   1. This is expected, since it's a secret. However, local development instructions can include that this value needs to be replaced in .npmrc. Alternatively, I have commented out all dependencies for Font Awesome to get around this issue.

2. npm run server doesn't seem to be a command that works. I get this response, after running brew update && brew upgrade npm && npm update && npm install:

   $ npm run server
   npm ERR! missing script: server
   npm ERR! 
   npm ERR! Did you mean this?
   npm ERR!     worker

   It looks like the corresponding run command should be web, if my understanding is correct.

3. There's a PostgreSQL server which needs to be running, defined in server/lib/db.js#8:

   const [, dialect] = process.env.DATABASE_URL.match(/^(\w+):\/{1,2}(.*)$/);

   1. I'm going to try to run this against an empty database instance, but I'm not sure if schema provisioning is required for this to work. Since there's a server/migrations and server/model folder I'm thinking it will create the necessary tables.

Let me know if there's anything I missed in getting my environment up and running. I'm happy to submit a PR for items 1 and 2 if the workarounds make sense. Still looking into 3.

It looks like today's "severe weather" schedule has the Clinton departure times listed under "Mukilteo-Clinton" and the Mukilteo departure times listed under "Clinton-Mukilteo" -- so strange!

At 2020-01-07 18:30 PST the M/V Suquamish was simultaneously reported to be an hour late for the 5:35 sailing from Clinton and also on time for the 6:35 sailing. This seems like a bug, though it could originate on the WSF side.

Take into account whether there were more or less sailings on previous weeks/years when making forecast calculations

Display crossing progress and status (e.g. "sailing", "at dock", etc)

Way to view vessel details by clicking a <VesselTag>

• Infrastructure for sending alerts based on filtered WSF bulletins and detected delays.
• Allow user to filter by day of week and route

Can this be done without accounts?

If the user grants location permission and they are within a few miles of a ferry terminal, suggest that they view that terminal

Solves the problem where you are accidentally viewing the right schedule in the wrong direction

Temporary 1-boat schedule:

Mukilteo-Clinton ferries typically stay on time in the AM (uni-directional peak volumes eastbound) but get progressively later throughout the afternoon (bi-directional peak volumes). They then gradually return to on-time operation in the late evening. Currently late ferries are predicted to stay late all night.

Cache version of "normal" schedule so that cancelled runs or other variations can be highlighted

Currently this data only exists for Mukilteo & Clinton

• Open wsf-cameras.js
• Put cameras in order for terminal. 0 = first cars on. Set orderFromTerminal
• Get positions on VesselWatch (turn on optional Ferry Camera map layer)
• Measure with My Maps
• Set feetToNext
• Set spacesToNext as feetToNext / 22

To repro

1. Open ferry.fyi (in a private browser it defaults to Mukilteo -> Clinton
2. Tap Seattle (top left)
3. Tap Bainbridge (top right)

Expected
shows Seattle -> Bainbridge

Actual
shows Bremerton -> Seattle

Saw this on my iPhone as well, but this video is from desktop

😨

Cancellations may need to be inferred from human-readable ferry alerts, TIS data, and/or user reports if they are not reflected in the WSF schedule.

Take into account the boat size when making forecasts

Ideas:

• Open list at bottom and animate scroll to top
• Inner shadow on scrollable edges
• Size list to cut an item in half

• Scan barcodes with Quagga
• Detect reservation barcode and save it with special tag
• Allow user to tag other barcodes with set of sensible tags (route, multi-use pass, etc)
• Tap to view barcode in full screen with jsbarcode

At 6:27 p.m., ferry.fyi was showing that the 6:10 departure from Mukilteo was predicted to be 28 minutes late, i.e. at 6:38. This is accurate. I'm on board at 6:33 and it's still loading vehicles.

But, it also says that the 6:10 ferry already departed 38 minutes ago at 5:49. That's clearly incorrect.

Tokitae (scheduled 6:40 PM) is shown as having departed 32 minutes late at 7:12 PM but is still docked as of 7:20 PM.

If the API lies about departure times, maybe we could learn actual departure times from vessel position data instead?

Auth0

Way to view terminal details. UI unclear

PWA splash icons has darkened corners

On the 4th of July, ferry.fyi showed a regular weekday schedule instead of the holiday schedule. The extra evening runs were not shown.

https://web.dev/wake-lock/

https://capacitorjs.com/

(probably a duplicate of #31 )

Steps to Repro
While viewing Bainbridge -> Seattle

1. Select Seattle (left)
2. Select Bremerton (right)

Expected
Shows Seattle -> Bremerton

Actual
Shows Bainbridge -> Seattle