The link is still on my work computer but doesn't work. It was called "VDOT's Drive It"
My memory of it was that it was extremely slow.
That's it. Perhaps it was rendered obsolete by Street View?
Kentucky now has something similar.
StreetView might have provided a convenient excuse to phase it out, but I'd suspect the real reasons had to do with usability and bandwidth. There are some exceptions (e.g. Florida DOT's
photolog), but in my experience online photolog viewers have a painfully slow frame rate and no "pin on map" method for selecting a starting point, which makes them awkward to search for features from a location with known map position but unknown milepoint.
The best use case for state DOT photologs, at least for road enthusiasts, is actually to download the full-size imagery (not the thumbnails) for a given route in advance, and scroll through it rapidly on the local hard disk using an image browser and a smooth-scrolling mouse, effectively "driving" the route by computer. That is how I compiled lists of mileage sign destinations for various Interstates in Colorado and Utah; I could not have done this nearly as efficiently with StreetView because I had no advance knowledge of the location of each mileage sign.
However, this works only when the full-size imagery has a low enough resolution that it can be displayed on the screen without resampling, otherwise the image browser can't keep up and you see mostly a black screen with occasional flickers of image. On my computer (1920 x 1080 screen resolution), this isn't a problem with WSDOT SRView (1376 x 1032) or Oregon DOT's videolog (640 x 480), but it is with some KyTC photolog imagery (older images are 1600 x 1200, while newer is often 2400 x 1800) and recent Utah DOT Roadview imagery (2012 vintage; older UDOT imagery is 1280 x 1024, newer is 3296 x 2472). Florida DOT (1900 x 1426) is right at the margin where it becomes impossible, at least for my screen (I have to choose "Show actual size" to avoid the screen going black).
The bandwidth consumption associated with photologs is significant. The industry standard is 200 images per mile per camera position (always front and right; some state DOTs, like KyTC, use three in a left-center-right configuration). Depending on the pixel count per image, the disk storage burden for a complete primary state highway system can be quite large. When I discovered Colorado DOT's photolog in 2013, I estimated the total storage requirement at 1.8 TB (1280 x 960 images, center-right configuration, both directions, 9144 miles of state highway: that is, 7.3 million images at 0.25 MB per image, or 1.8 TB). Even if you restrict yourself to one position and one direction (as I have tried to do to limit sun shadow on signs), a download of photologging for a full primary state highway system can easily be several multiples of a typical monthly bandwidth usage cap for a residential cable Internet account (mine, for example, is capped at 250 GB).