aeharding / ppg.report Goto Github PK

For example, Air Quality Alerts could probably just be an exclamation point icon without yellow background.

Creating this issue to track this.

And persist preference locally.

Once the weather api is updated, remove the hack in src/services/weather.ts

weather-gov/api#573

https://ppg.report/44.7712,-69.6829

On mobile this would be a nice usability thing

And if scrollLeft === 0, then take the user back home.

It would be cool to have a button to automatically scroll ("animate") the 24 hour RAP

https://stackoverflow.com/a/62308482

This is a critical issue, hotfix pending

It might be cool to investigate showing a "feels like" temperature as an option

https://ppg.report/37.6225,-122.384

@tippyjs/react was last updated 2 years ago. It's also fun to try new things, and pop over UI is changing all the time (see: CSS overflow-anchor)

https://floating-ui.com/docs/react

Currently blocked by stipsan/react-spring-bottom-sheet#227

axios cache middleware is buggy when offline (cache age doesn't work)

need to implement our own offline caching mechanism.

Error: https://harding.dev:23435/@fortawesome%2ffontawesome-pro/-/fontawesome-pro-5.15.4.tgz: Request failed "401 Unauthorized"

I'd just like to contribute a few low-hanging UX tweeks, but would like to avoid having to pay for a fontawesome pro subscription to do so.

Quick question though: how is the site figuring ground level for a given location?

Check out https://ppg.report/45.685,-111.051 Actual ground elevation at those coordinates is 4,805’ MSL, but PPG.report shows 6,348’ elevation. This is confusing as the default being ‘AGL’ is actually showing elevations ~1,500 higher, and therefore exaggerating the down-mixing in the airmass.

First off -- LOVE the TFR integration!!! I also love the weather, the METARs, and the Discussion and Report Metadata sections!!!

So the TFR for Washington DC really is not temporary, it's considered permanent. TFR FDC 1/1155

The problem is that many of the sites I fly are outside of the DC TFR 30nm ring (Called a SFRA, Special Flight Restriction Area), yet PPG.report continues to show the red warning sign.

KEZF, Shannon Airport, in Fredericksburg, VA, is both outside of the 30nm ring, as well as south of its southern-most border, yet ppg.report continues to show that TFR. I realize this is because the site is within 20 miles of my selected location, but truly, 80% of my flights are within 20 miles of the permanent flight restrictions.

I understand Washington DC is an exception here, maybe provide an option to ignore Permanent SFRAs? I still absolutely want to know about truly temporary TFRs, but the DC SFRA is not one of them! I took the FAA course, I have the certificate, I can fly in the 30-60nm SFRA Ring.

Thanks!

This will provide a better offline experience, instead of displaying coordinates

It would be nice to be able to copy the coordinates from the meta-data of the report. When the app is installed to the home screen, there is currently no way to get the coordinates of any given location.

When less than a month old, show "20d" with baby face