We can choose the startup layer and location. I’d also like to choose the forecast model to be NAM for example instead of always ECMWF.

@Suty Highlands Peak Station is run by DRI. The correct Highlands Peak station web page is https://wrcc.dri.edu/weather/hipk.html

My contact there said, "I’d suspect they are pulling it either from our pages or maybe from one of the NOAA sources that we send the data too. Yep. Looking at their pages, they indicate it is coming from Madis. That is the NOAA national mesonet data system we send the data too. And looking at the second (southern) Highlands Peak station it is from the Highlands Peak station but the location is wrong and the data is slightly older. I’m guessing that is coming through the NOAA HADS system. They try to decode the satellite transmitted data and that’s where it would be coming from…and why it would be a little older."

@Suty I'm not the technical endpoint on the data stuff. I just know for a fact there no weather station at N36d3'2", W121d33'33" -Mark

Highlands Peak station is correct and in the correct location at N 36d4'3", W121d33'33". There is a second station on the map, looks like same longitude but just a bit south in latitude called "Highlands Peak Met Station N" which appears to be a duplicate and is in a location where there is not station in reality. I manage the property where these WRCC stations are located and can confirm we don't have a station in the bottom of Vicente Creek.

@idefix37 same with satellite. Saving satellite or radar does not also save the forecast model choice. Wondering if there could be independence there?

@idefix37 aha, I see. I didn’t notice because I usually have the radar as the overlay, which doesn’t seem to trigger the forecast model choice. If you have radar, go to a location and look at the NAM forecast, then close and reopen the app, it comes back as radar and ECMWF

We can choose the startup layer and location. I’d also like to choose the forecast model to be NAM for example instead of always ECMWF.