I’ve been working on moving my husband’s weather data pages from our old hosting system to our new hosting system. As part of the new look I’m adding links to some of the sources of weather information that he uses regularly. One of these is the NOAA local forecast page. A few days after he sent me the URL he sent me an updated one:
I’d always kept a favorite link to the NOAA web site, where I get weather forecasts. they have a little clickable map where you can click your specific location and get a specific forecast. but it’s a little map, and accuracy is difficult, so I just clicked around ’til it said ‘5 miles east of duvall’ and figured that was close enough. But no (OCD? me? not a chance, baby!). a few days ago I happened to notice that the URL is obviously encoding the decimal lat‐long in a simple to read (and modify!) format:
textField2are obviously latitude and longitude, in decimal format. so I went to our local county GIS system, found my house, got the exact lat/long and customized the URL in my favorites folder. tada: a url that is customized ‘exactly’ for our location. not that it makes much difference, but it illustrates the usefulness of transparent URLs.
Pretty slick huh? The URL is probably not easily readable to most people to to a weather geek the latitude and longitude numbers are both meaningful and recognizable.