• After witnessing the continued decrease of involvement in the SpotterNetwork staff in serving SN members with troubleshooting issues recently, I have unilaterally decided to terminate the relationship between SpotterNetwork's support and Stormtrack. I have witnessed multiple users unable to receive support weeks after initiating help threads on the forum. I find this lack of response from SpotterNetwork officials disappointing and a failure to hold up their end of the agreement that was made years ago, before I took over management of this site. In my opinion, having Stormtrack users sit and wait for so long to receive help on SpotterNetwork issues on the Stormtrack forums reflects poorly not only on SpotterNetwork, but on Stormtrack and (by association) me as well. Since the issue has not been satisfactorily addressed, I no longer wish for the Stormtrack forum to be associated with SpotterNetwork.

    I apologize to those who continue to have issues with the service and continue to see their issues left unaddressed. Please understand that the connection between ST and SN was put in place long before I had any say over it. But now that I am the "captain of this ship," it is within my right (nay, duty) to make adjustments as I see necessary. Ending this relationship is such an adjustment.

    For those who continue to need help, I recommend navigating a web browswer to SpotterNetwork's About page, and seeking the individuals listed on that page for all further inquiries about SpotterNetwork.

    From this moment forward, the SpotterNetwork sub-forum has been hidden/deleted and there will be no assurance that any SpotterNetwork issues brought up in any of Stormtrack's other sub-forums will be addressed. Do not rely on Stormtrack for help with SpotterNetwork issues.

    Sincerely, Jeff D.

Web usability: keep data URLs consistent

  • Thread starter Thread starter Dan Robinson
  • Start date Start date

Dan Robinson

This is more of an open request to anyone involved in maintaining weather data and information web sites (NOAA, NWS, model data, obs, radar, satellite, etc).

If at all possible, please keep the URLs the same when a product is updated. I've noticed many products get an update, but get moved to a different folder on the same server. This causes all of your users to have to update their bookmarks and data links. For example, the 4KM WRF has moved twice in the past few months on the same domain, and NOAA satellite imagery links have been changed.

When multiple agencies do this (as is the case now), the result is bookmarked links continuously ceasing to work for your primary end users, the result is having to go searching for the new link and manually update the bookmark. Since a good weather bookmark list can be extensive, maintaining this list is daunting when it is so dynamic.

From a web usability standpoint, new products should be beta-tested in a new folder or directory, then when it is ready for introduction, moved into the location of the current product. Even server moves can be kept 'transparent' with DNS and folder aliasing. The "this page has moved" redirect is considered an outdated and web-unfriendly tactic to be avoided.

For government agencies, I would have this request added as a line item to your web contracts so that this gets some attention during implementation. Your end users will be forever grateful!
 
By "this page has moved redirects" I assume you are talking about the meta tag http-equiv refresh method.

The preferred ("right") method that is SEO-and-user-friendly is to create a 301 (permanent) redirect.
YouTube: Why you should create 301 redirects
Advantages (and how to do it on different web servers and/or different languages)

Simply naming your files/folders exactly the same thing is not always possible/practical (for example when you are changing your site from .html to .shtml or .php).
 
Back
Top