My cousins from Toronto came over to ski and snowboard at Whistler over the last month. I had the opportunity to pick up skiing again and accompany them up at Whistler a few times.
Whistler Blackcomb is pretty big, so one would usually look at a map to find suitable runs. This is a sample of what is provided in the “Mountain Atlas”:
It looks nice and is mostly useful. But for all the map geeks out there, can we find anything better?
Turns out that Google Maps conveniently has the ski runs in its map. But there’s more: Google Maps in Terrain mode shows the contour lines like a topographic map!
Beautiful! The top-down view makes it easy to see the actual orientation of the run and “behind” the mountains, and the contour lines makes the rate of descent visible. So from here you can see there is a green run from the Peak—Mathew’s Traverse—whereas it’s not depicted on the trail map.
How do you get to the map?
Here’s the link: Google Maps Terrain @ Whistler
Alternatively you can search for the location you want in Google Maps, then open the menu at the top left, then select “Terrain” mode.
The site wasn’t really designed for day-to-day navigation, but more for transit enthusiasts who are looking to find specific buses (e.g., the double decker test buses we have on the streets right now, 1008 and 1009). In addition, I’ve also heard that bus drivers also use the site to locate their bus as it arrives to their pick up point.
I wish I took some time to polish up the site over Christmas, since it’s pretty much still running on the same code base (both in the user interface, and behind the scenes) as when I created it six years ago! Nevertheless, it’s cool that the site’s been found and mentioned by some local online media, and to spread some “transit geekery” out there.
Since TransLink released their new mobile Next Bus site with real-time GPS updates of bus locations, I’ve been trying to find ways to get the data and rehash it into something that Metro Vancouver transit enthusiasts (more specifically, enthusiasts who chase buses and monitor the transit system’s operation) will find useful.
There were two main shortcomings of TransLink’s site from the viewpoint of a transit enthusiast:
Can’t search for a specific bus. Often times transit enthusiasts “chase” a particular bus, usually a new bus, a fresh bus after a midlife refurbishment, or a bus with a new advertisement wrap.
Can’t see the entire system as a whole. This one’s pretty self explanatory. It’s just fun to be able to see where all the buses are.
So I created a system which gleaned information from the TransLink site and aggregated it into a useful interface which I called “T-Comm”.
This is named after CMBC’s Transit Communications centre which has an interface similar to what I created. Using the information I was also able to add additional functionality like grabbing the bus’s schedule for the current trip and even the entire day.
Since most transit enthusiasts would be using this on the go, I knew I had to make this site mobile-friendly. The enthusiasts I knew used a myriad of mobile devices including Blackberries, iPhones, and Androids, so it would not have made sense for me to create a native app for each of the platforms; it would have killed me in terms of time and energy. I chose to use jQuery Mobile and Google Maps API as the basis of the frontend. The backend is powered by PHP/MySQL. I was amazed at the ease I was able to make something mobile-friendly using jQuery Mobile. It was actually fun too. More importantly testers reported positively on their mobile devices.
I’m hoping that TransLink will release the GPS data officially for developers. They’ve said after April 2012 on Twitter, so I’m crossing my fingers.
Contact me if you would like access to the site. Since the current site hammers TransLink’s servers I’m trying to tread lightly. Once official GPS data is used I will open it to the public, but I don’t really see this being used by the public as it is quite enthusiast-oriented.