Roads - The standard roads layer displays interstate and U.S. Names are filtered at varying zoom levels to reduce overlap and visual clutter. If two assets are close enough together that their names overlap on the map, only one will be shown.Ĭities - The cities layer displays the names of over 25,000 cities and towns obtained from a U.S. It requires a WeatherOps enterprise account. Derived contours cover only the United StatesĪssets - The assets layer displays asset locations defined in the WeatherOps Commander portal used by WDT enterprise customers. They provide good indicators of where hail and wind shear occurred during recent severe weather events and, when combined with the 30-day archive in Tier Two, are useful for post-event analysis. Contours cover a 24-hour period and are updated about twice an hour. They are available via a RadarScope Tier Two subscription. Storm tracks are available only for the United States.ĭerived Contours - Derived contours indicate the probability of hail, estimated hail size, and azimuthal wind shear as determined by processing real-time radar data through custom algorithms. An alternative feed is available to AllisonHouse subscribers. Storm tracks are available to everyone via a NOAA feed. The storm track layer shows the expected position of the storm in 15 minute increments. Storm Tracks - The storm tracks layer displays projected storm paths determined by NWS storm-tracking algorithms. Lightning data are currently available for the United States and Canada. The AllisonHouse lightning feed displays both cloud-to-cloud and cloud-to-ground strikes, but it doesn’t animate with the radar. Strikes are animated in sync with the radar loop and fade out with age. The RadarScope Pro lightning feed displays cloud-to-ground strikes. Lightning data requires a RadarScope Pro subscription or an AllisonHouse data plan. Lightning data is refreshed once a minute. Lightning - The lightning layer displays lightning strike locations within the coverage area of the selected radar over the past 30 minutes. This is true on both Spotter Network (the link at the top of all pages) and also in RadarScope in the spot where the Spotter Network credentials are configured.Some of the layers that haven't yet been defined within this user guide are explained below: in a number of places, the Support link goes to which is a "Free parked" site for GoDaddy. I do have another thing to report (admittedly a lot more minor). If I still have problems, I will contact the author for further assistance. It is different because it still uses the Application ID instead of the User/Password combination to access SpotterNetwork. I am still working to get Radar Alive! Pro to work. thanks with the help with that (maybe less than intuitive, since you set up the account in one spot and enable position reporting in another area in the settings, with a headline of "Advanced"). I was able to get RadarScope to send a position report last night. Since it is no longer a supported product, unless there is something that has changed on SpotterNetwork, I guess this will be an unexplained issue. That has stopped working with the JSON error I mentioned. If I wasn't clear, this was working fine for years using PYK元Radar.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |