API Web Service vs NDFD Web Services #290
Replies: 2 comments
-
...but seriously, MDL is focused on reasearch and development, and weather.gov is focused on dissemination. Their REST service was developed to share their research, which includes a forecast product. Both are based on the forecast netcdf created by the field offices. Similarly, you can get also observations directly from MADIS, but the user experience is not optimal. The API is more inclusive, we dissiminate all products, including text, alerts, observations, etc. using modern technologies. It was designed to be highly efficient with our CDN, which is why there are two steps. The NWS doesn't issue forecasts by points, but only by a series of grids; where hundreds of thousands of points reduce to the same forecast. Once you know what grid point you need, you no longer have to make two queries. |
Beta Was this translation helpful? Give feedback.
-
Thanks for the excellent summary, and for the LOL... I'm thankful that I'm using the right API and don't have to rewrite everything 😂 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
What is the difference between the API Web Service and the NDFD Web Services? Both can provide a timeseries forecast for a particular lat/long via an API call, for example this for the NDFD API, while for the former one there is a two-stage process, e.g. this then this. Are they based off the same underlying data? Which one should I be using?
Beta Was this translation helpful? Give feedback.
All reactions