- That "weather website" has to serve all of Australia.
- It's got to be usable on big screen desktops, tablets, smartphones.
- It has to have an uptime of what I estimate to be 99.99%. As the article says, farmers will pitchfork you if you can't tell them when rain will hit their fields.
- It has to be slinging dynamic image data to (about) every visitor.
- The data comes from somewhere. You're lucky if they have that under control already. Probably not.
I came up with these aspects, not knowing anything about what the "Bureau of Meteorology" actually needs in a website. It's just common sense speculation.
This seems like a classic case of the whole "once we have all the data building this is easy". Yeah that's the easy part, that's why building a weather dashboard is one of the classic beginner projects.
The issue is aggregating the data. Same for supermarket systems, transport and logistics, and other systems tied to external data that requires physical interaction.
- That "weather website" has to serve all of Australia.
- It's got to be usable on big screen desktops, tablets, smartphones.
- It has to have an uptime of what I estimate to be 99.99%. As the article says, farmers will pitchfork you if you can't tell them when rain will hit their fields.
- It has to be slinging dynamic image data to (about) every visitor.
- The data comes from somewhere. You're lucky if they have that under control already. Probably not.
I came up with these aspects, not knowing anything about what the "Bureau of Meteorology" actually needs in a website. It's just common sense speculation.