Lab Session: Weather Data: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 9: | Line 9: | ||
#* Make sure you're using JSONP to make this request. | #* Make sure you're using JSONP to make this request. | ||
# Upon receiving the response, you should parse the response into the various Value labels on frmMain. The format of the response is described here: http://bugs.openweathermap.org/projects/api/wiki/Weather_Data | # Upon receiving the response, you should parse the response into the various Value labels on frmMain. The format of the response is described here: http://bugs.openweathermap.org/projects/api/wiki/Weather_Data | ||
== Bonus == | |||
* The [http://bugs.openweathermap.org/projects/api/wiki/API_2_5 weather API] has a lot of functionality that we aren't using. Create new forms and fields to return and display either forecast data, historical data, or both. | |||
* The city field requires a fairly exact name. If you'd like to allow for mistakes and abbreviations, you can integrate the [http://bugs.openweathermap.org/projects/api/wiki/Api_2_5_searhing city search api]. This returns a list of possible city matches. One way to use this is to present a list that the user can choose from in a new form. | |||
Revision as of 22:44, 18 December 2013
In this lab you will pull in some weather data from http://openweathermap.org/API.
Student Outline
- Open LabWeather.nsx.
- Add a click event to btnLoad on frmMain
- Have the click event use the value from txtCity to query OpenWeatherMap's API: http://api.openweathermap.org/data/2.5/weather?q=Riyadh,sa&callback=weatherData
- Keep in mind that you should URL encode any user entered parameters, like city, using encodeURIComponent
- Make sure you're using JSONP to make this request.
- Upon receiving the response, you should parse the response into the various Value labels on frmMain. The format of the response is described here: http://bugs.openweathermap.org/projects/api/wiki/Weather_Data
Bonus
- The weather API has a lot of functionality that we aren't using. Create new forms and fields to return and display either forecast data, historical data, or both.
- The city field requires a fairly exact name. If you'd like to allow for mistakes and abbreviations, you can integrate the city search api. This returns a list of possible city matches. One way to use this is to present a list that the user can choose from in a new form.