Using Google Weather API in a VoiceXML Application

In this post I will show you how to use the Google Weather API to retrieve current weather conditions that can be voiced back to callers.  In a previous post I showed how to use VoiceModel to create a simple VoiceXML application that asks the caller for their zip code, looks up the the weather conditions for that zip, and then voices the information back to the caller; but I used a mock-up for the service that retrieves the weather information for easier testing.  This time I will demonstrate how to swap out the mock-up for a functioning service to get the current weather.  Since the underlying architecture for VoiceModel is ASP.NET MVC this method would work just as well in a web application.

The way I implemented the Weather Application the service to retrieve the weather information implements the interface IWeatherService. This allows me to easily insert a mock-up for testing or any version of a service that I wish to.  I chose the Google Weather API because it is free, easy to use, and does not require setting up a special account.  The downside to this approach is that it is not supported by Google and therefore is not well documented.  Google uses this API for it's own internal applications but for some reason has not released it to the public.  You can search the web and get a lot of information on how others are using it, but since it is not public you do risk the chance that it could change without notice.  But after seeing how I implemented this you could implement another weather service API if you so choose.

Here is the code change in WeatherCallFlowBuilder.cs that implements my new service in the class GoogleWeatherService.  I commented out the line that implemented the mock-up for comparison and easily changing back to the mock-up.  The proper way to implement this would be to use a dependency injector tool like Ninject but that is for another post.

public static CallFlow Recreate()
{
   CallFlow flow = new CallFlow();
   flow.AddStartState(new State("greeting", "getZip"));
   flow.AddState(new State("getZip", "getWeather"));
   //Uncomment next line and comment the following if you want to use the mockup 
   //instead of the Google service
   //flow.AddState(new GetWeather("getWeather", "voiceWeather", new DAL.WeatherServiceMockup()));
   //This implementation uses the Google Weather API to get the current weather conditions
   flow.AddState(new GetWeather("getWeather", "voiceWeather", new DAL.GoogleWeatherService()));
   flow.AddState(new State("voiceWeather", "goodbye"));
   flow.AddState(new State("goodbye"));
   return flow;
}

The IWeatherService interface has one method that needs to be implemented and here is the implementation for GoogleWeatherService.

public Weather getWeather(string zipcode)
{
    string weatherSerializedXml = getResponseFromGoogle(zipcode);
    Weather w = parseXml(weatherSerializedXml);
    return w;
}

The Google Weather API returns an XML document.  Here is how I retrieve that document as a string.

private string getResponseFromGoogle(string zipcode)
{
    StringBuilder sb = new StringBuilder();
    byte[] buf = new byte[8192];

    HttpWebRequest request = (HttpWebRequest)
        WebRequest.Create("http://www.google.com/ig/api?weather=" + zipcode);

    HttpWebResponse response = (HttpWebResponse)
        request.GetResponse();

    Stream resStream = response.GetResponseStream();
    string tempString = null;
    int count = 0;

    do
    {
        count = resStream.Read(buf, 0, buf.Length);
        if (count != 0)
        {
            tempString = Encoding.ASCII.GetString(buf, 0, count);
            sb.Append(tempString);
        }
    }
    while (count > 0);

    return sb.ToString();
}

Once we have the XML document we need to parse it out for the relevant information for our voice application.

private Weather parseXml(string xmlWeather)
{
    Weather w = new Weather();
    XmlDocument weatherDoc = new XmlDocument();
    weatherDoc.LoadXml(xmlWeather);
    XmlNode wNode = weatherDoc.SelectSingleNode("/xml_api_reply/weather/current_conditions/condition");
    w.conditions = wNode.Attributes["data"].Value;
    wNode = weatherDoc.SelectSingleNode("/xml_api_reply/weather/current_conditions/temp_f");
    w.temp = wNode.Attributes["data"].Value;
    wNode = weatherDoc.SelectSingleNode("/xml_api_reply/weather/current_conditions/wind_condition");
    string windCondition = wNode.Attributes["data"].Value;
    char[] delims = { ' ' };
    string[] windParts = windCondition.Split(delims);
    w.windDirection = windParts[1];
    w.windSpeed = windParts[3];
    return w;
}

You can get the full source code for this example on CodePlex.  If you do not have an IVR to test this application on you can test this example using Voxeo's free IVR.  Look at my previous posts on how to test with Voxeo's IVR as either a hosted service or installed on your workstation.

Comments

Post a Comment

Popular posts from this blog

Using Claims in ASP.NET Identity

Claims can simplify and increase the performance of authentication and authorization processes. I wrote about how you can use the roles stored as claims to eliminate back-end queries every time authorization takes place .  ASP.NET Identity has good support for claims-based identity and it creates several claims for you automatically when you create a new identity.  Here is how we create the identity for a new user during the log-in process UserManager<applicationuser> userManager = new UserManager<applicationuser>(new UserStore<applicationuser>(new SecurityContext())); ClaimsIdentity identity = userManager.CreateIdentity(user, DefaultAuthenticationTypes.ApplicationCookie); If you inspect the Claims property of ClaimsIdentity after calling CreateIdentity you will see that there are there are three or more claims. There is a claim for the user ID, user name, identity provider and one for each role assigned. So what if you want to add some more claims? Here is an ex
Keep reading

Customizing Claims for Authorization in ASP.NET Core 2.0

Image
There have been some major changes to ASP.NET Identity with the release of Core 2.0, which you can read about here .  One of the major changes is that it does not rely on using middleware anymore to customize it.  Instead dependency injection is used by configuring via services in the ConfigureServices method of StartUp.cs .   There is not much documentation or examples on how to do this so I am going to explore how to customize ASP.NET Identity and publish some examples in this blog.  First I wanted to look at how you would add custom claims to the identity and then use those claims for authorization. To begin create a new ASP.NET Core Web Application  project in Visual Studio 2017.  Be sure to select . NET Core and ASP.NET Core 2.0 in the two drop downs at the top.  Select the template for Web Application (Model-View-Controller) and Change the Authentication to Individual User Accounts .  When the project is created you are ready to add some code. For this example we are s
Keep reading

Seeding & Customizing ASP.NET MVC SimpleMembership

Image
In ASP.NET MVC 4 Microsoft introduced a new membership provider that is referred to as SimpleMembership.  SimpleMembership makes it easier to customize user profiles and incorporates  OAuth support.  I have seen a lot of questions on StackOverflow on how to customize SimpleMembership and seed it with data and in this post I will discuss some methods for achieving both . SimpleMembership uses Entity Framework (EF) 5 and the code-first model. To initialize the database that contains the users and roles a filter is used called  InitializeSimpleMembershipAttribute.   This attribute is decorated on the AccountController as shown here: [Authorize] [InitializeSimpleMembership] public class AccountController : Controller { ... } This is setup this way so that the initialization code is only called when accessing the actions on the AccountController .  If you look at the code for  InitializeSimpleMembershipAttribute you will see a lot of code to setup initialization which is basically
Keep reading