Weather.gov 2.0
github.com
github.com
> The fundamental problem that we’ve observed is that weather.gov reflects its organizational silos (Conway's Law) more than its users’ needs. A lack of overall strategy, feedback/monitoring, and tools have perpetuated this problem.
Wow, my org would not have the guts to write that down in a public README!
Building trust and relationships is an underrated component of these transformation efforts.
Silos happen. I'm not willing to spread blame. I will aside some of my frustration if I know it's an acknowledged problem and there's willingness to address it.
This makes me worried that they're going to add some "analytics" tracking scripts in there that come with those damned annoying cookie pop-ups.
Details here: https://digital.gov/guides/dap/common-questions-about-dap/
So, no cookie popup
I remember about 8 years ago there was an "experimental" site for one of the US government's aviation weather products. And it was so very good, designed modern and usable and clean. Didn't look at all like the usual awkward government website. The team seemed like nice folks too but were caught up in some multi-year government funding system. It eventually got shut down and IIRC, none of their work ever got promoted to the main site.
We are very lucky in the US to have a fantastic weather service and a mandate for their products to be free and public domain. Unfortunately there's also a lot of political pressure on them to not be too good so that some commercial company can profit. AccuWeather was one such company, at least back in 2005: https://www.onthecommons.org/privatizing-weather/index.html
https://github.com/weather-gov/weather.gov/tree/main/.github...
https://github.com/weather-gov/weather.gov/blob/smh--researc...
Nit: it redirected me to San Diego weather after a few seconds after I had already put in a different location. Maybe because I block the location request?
There is a GitHub for government [0] but it relies on contribs and isn’t very complete.
GSA started code.gov under the Obama administration with the aim to create a single index of all government projects. It withered under Trump and was basically defunded under Biden so they don’t really do much other than link out to major agencies and there’s no longer a requirement to timely index.
My org has like a 1000 repos and we’re one of hundreds of agencies so I can’t imagine collecting all these together without a little effort. The original code.gov worked pretty well as everyone just dropped a code.json file onto their web site and GSA scooped them up and combined them into a single. So it’s a real shame they stopped doing that, and stopped asking people to publish their code.jsons as it was a good idea.
Merely as a point of reference, https://github.com/orgs/microsoft/repositories cites they currently have 6100 repos with another 2200 in /orgs/Azure so 10000 in an GH org wouldn't be unprecedented. I couldn't readily find any way to cough up their other top-level brands, and the "topics" seem to apply only to the repos themselves, not to the GH Organizations
My point stands though as it’s really impossible to try to standardize an organization as massive as a government into a single code management system, much less a single org, even if it has fantastic hierarchical management.
The government can host their own GitHub instance if they want to. I think the point is that there are probably thousands of “servers” with government repos. And consolidating to one “server” is a horrible idea.
A catalog is good though.
But for a universal (any host, any government) dataset contributing to wikidata would be helpful, and in the fullness of time I'd like to use that to cross-validate and identify missing entries https://github.com/github/government.github.com/issues/877 but the properties available probably need work to get there, right now there's e.g., https://www.wikidata.org/wiki/Property:P1324 https://www.wikidata.org/wiki/Property:P2037 https://www.wikidata.org/wiki/Property:P8827
Example: https://forecast.weather.gov/MapClick.php?lat=37.7771&lon=-1...
https://tgftp.nws.noaa.gov/data/forecasts/zone/
I just looked through my state to find the right file but it looks like the "More Local Wx" link from the 7 day forcast page has the right name for the file (ORZ006 in my case).
I also have a few icat aliases to show radar; one for current, one for sequential, and one looping from this page (radar name same as on radar.weather.gov):
https://radar.weather.gov/ridge/standard/
However, I find the one hour accumulation view to be best and I couldn't find a way to get images for that view so I usually look at radar.weather.gov if it works (it has been working better lately but sometimes just doesn't work for me).
I haven't ended up looking at them often but I also made some icat aliases for 6-10 day and monthly temperature and precipitation outlook from:
sharing in hopes it's helpful, not to be pedantic
We are building some emergency management tools here (genAI first: continuous monitoring -> alerting, chatbots, tailored sitrep reports: feel free to reach out!), and as many agencies, utilities, etc, need specialized variants, I've come to appreciate the last mile data & UI difficulties that weather.gov must be solving internally and would benefit other agencies.
Weather.gov afaict is run by NWS under NOAA, so interesting it's not in the mission revamp here..
https://forecast.weather.gov/MapClick.php?FcstType=graphical...
just wish it could do the same layout historically in the past
https://forecast.weather.gov/MapClick.php?lat=33.4503&lon=-1...
I'll definitely end up using the broadcasting/eventing API for push notifications.
Something went wrong
I think they've got you covered. Maybe not directly porting over, but it sounds like they're aware of the non-emergency use cases.
I always tell tech savvy people to look at the forecast discussion and not the infographics. For example, look at Spokane:
https://forecast.weather.gov/MapClick.php?lat=47.65726000000...
Then select 'Forecast Discussion' and read the discussions. They are usually updated a few times a day at the minimum, but during active weather events they are generally updated every 3 to 4 hours with new information (more data from the 850mb layer, for example).
And the most frustrating thing is that the links to the https://radar.weather.gov/ 'lite' version are only visible if you sucessfully execute JS. So the no-JS version is invisible to no-JS browsers. Whoever they had designing this front end had never heard of graceful degredation, let alone progressive enhancement. It remains an accessibility nightmare.
Weather.gov 2.0 will be more of the same.
I usually use the local radar gif though. My local office forecast pages link to the lite radars.
It's straightforward to take a peak at the available gifs:
And thank you for being persistent about raising awareness about how useful that national loop is.
Those are the wrong links for that purpose. What you want is e.g.
https://radar.weather.gov/station/knkx/standard
Reach these by scrolling down your local forecast.weather.gov e.g.
https://forecast.weather.gov/MapClick.php?lat=32.95528450000...
This isn't difficult. Keep the better thing running and run the new showy thing in parallel for whomever wants that.
The ridge gif loops load faster than the more complicated map starts to fill in...
The gif for an area covering a 2 hour drive in any direction loads in about a quarter second.
I probably got a little soured on it when they made it the primary path from forecast pages at a time when it was still quite slow.
https://www.acquia.com/blog/drupal-for-government
https://www.drupal.org/industries/government
https://www.zyxware.com/article/6229/top-7-reasons-why-drupa...
https://www.drupal.org/openplus
https://www.applytosupply.digitalmarketplace.service.gov.uk/...
Now most may be a stretch, it's a hard metric to calculate without going around and counting every gov site. But for English speaking countries, it is very popular enough so that I'd say most gov/state/department websites are Drupal.
That and I am a Drupal consultant. So I may be biased.
Tell us more. (A lot more. "Extraordinary claims require extraordinary proof".)
Modules/themes on drupal.org which show "Stable releases for this project are covered by the security advisory policy" are written by trusted users. There is no other protection from rogue code because they are inherently able to access the database. It utterly doesn't matter what extension points the code supports and how because of that. In very broad strokes, if you are using any CMS which a) accesses a database b) allows installing additional code and it runs that in the same process as the CMS code accessing the database -- then you are vulnerable to rogue code. Like, a headless CMS where the frontend only talks to it via an API is protected from rogue code in the frontend part but that's about it.
This means the Drupal ecosystem is vulnerable to a supply chain attack, yes but ... um ... that doesn't make Drupal design insecure, does it?
And once again, what does rogue code has to do with Drupal? Nothing. The same would happen with almost any system. Name any CMS which is actually used in the wild and doesn't get compromised if you install rogue code right into the codebase.
I mean if you built a site from scratch in Spring or Next.js and you start using third-party libraries or UI frameworks, all those third-party bits have full access to everything too.
You can even see it in the mission statement in the link: >Because the mission and culture at NWS is built around serving, preparing, and protecting people, the site must do the same.
This generally seems impossible, what if people have conflicting feedback?
Not my experience: forecast.weather.gov works just great for me as it is now.
Anyone else getting flashbacks of the Reddit/Gnome/KDE/... UI renovations?
Some other kind soul <https://news.ycombinator.com/item?id=39574022> found the staging (and eric and greg, heh) manifests <https://github.com/weather-gov/weather.gov/blob/6e98dcff73bc...>, which led to <https://weathergov-api-proxy.app.cloud.gov> which led to https://weathergov-design.app.cloud.gov/point/35.198/-111.65... containing the banner "This is a beta site. https://weather.gov/ remains the authoritative source of weather information." so chances are it's that
https://weathergov-staging.app.cloud.gov/point/35.198/-111.6... also works, but was slower. I didn't try eric or greg's copy :-P
“Strategy for prioritization: … Add complexity, ASAP”