Maine Power Outages Map
Working in a NOC, I often consult the two Maine power companies that have online outage information (there is a third that does not have such a feature). If I see many circuits go down at the same time I’ll check to see if there is an outage in the area by checking both those websites, then going to Google maps to see how far away the sites are from the current outages. This is a tedious process and I finally decided to do something about it by creating my own Google map with their wonderful API. I’d never used it before so this proved a great way to learn how to use it as well. After setting up the screen scraping to pull info off the power companys’ websites, getting the app to do just what I wanted, and working around some minor speed bumps, it’s done!
Google’s API is quite easy to work with, and I’m very pleased with the results. For most people this map isn’t very useful, and at any one time there are only a few markers plotted on it, but for myself it will be quite useful, and it was a great learning process. You can view the Maine Power Outages map at http://euicho.com/power
Tags: maine, maps, programming, projects, utility




B 12:04 am on 3/10/2009 Permalink
Well I love anything with Google Maps, though ironically I’m not using it as my major map view on my application at the moment, that may change if I get tired of OpenLayers issues with loading after being hidden (I’m already using GoogleMaps base layers on it anyway). Overall I love OpenLayers abilities to handle lots of projections seamlessly but I love the responsiveness of GoogleMaps (to use GoogleMaps i have to use a script to fit data on their projection). Anyhoo.
Big Hans 1:10 pm on 6/12/2011 Permalink
I work in a NOC, too, and I love this map. It looks like BHE changed the format…any chance of an update?
euicho 9:35 pm on 6/12/2011 Permalink
Thanks for the comment! I just noticed this as well last week. Should be a quick fix, I’ll update it early this week.
euicho 11:24 am on 8/2/2011 Permalink
Sorry I’ve been crazy busy, but I finally fixed it today!