You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Example response is below. The response may change: I mentioned to the WRDS team that "nws_station_id" is used instead of "nws_lid", which makes it inconsistent with other APIs. I was told they would look into that.
When asked why data is obtained by NWS lid and not NWM feature, I was told that's how they receive the data. In the netCDF they are given SCHISM node ids which they associate with NWS location ids through a mapping of some kind. Its all magic to me.
No user is currently asking for this capability, so its low priority. If a user asks for it, we'll up the priority.
Example data in netCDF can be found in Nomads (is this public?):
https://nomads.ncep.noaa.gov/pub/data/nccf/com/nwm/prod/
Look for "coastal" data sets for example netCDF files. For WRDS, they serve the data by NWS location id. A request looks like this:
https://[WRDS]/api/nwm_twl/v1.0/total_water_level/medium_range/nws_lid/THOM1/
Example response is below. The response may change: I mentioned to the WRDS team that "nws_station_id" is used instead of "nws_lid", which makes it inconsistent with other APIs. I was told they would look into that.
When asked why data is obtained by NWS lid and not NWM feature, I was told that's how they receive the data. In the netCDF they are given SCHISM node ids which they associate with NWS location ids through a mapping of some kind. Its all magic to me.
No user is currently asking for this capability, so its low priority. If a user asks for it, we'll up the priority.
Thanks,
Hank
==========
The text was updated successfully, but these errors were encountered: