1 00:00:00,270 --> 00:00:03,960 In this video we're going to continue to explore our request. 2 00:00:03,960 --> 00:00:08,160 We're going to learn how a request can automatically pass the Jason for us. 3 00:00:08,160 --> 00:00:13,680 We're also going to figure out how we can actually print a forecast using the response data. 4 00:00:13,890 --> 00:00:20,400 And finally we're going to explore some options for the dark sky API allowing us to do things like change 5 00:00:20,400 --> 00:00:27,150 the language from something like English to French and change the units from something like Imperial 6 00:00:27,150 --> 00:00:33,660 over to as I say you could get the temperature back in Celsius as opposed to Fahrenheit. 7 00:00:33,660 --> 00:00:39,710 Let's get started by having the request module automatically pass the Jason response for us. 8 00:00:39,750 --> 00:00:46,140 We can do this by customizing the options object and there is a list of all available options over in 9 00:00:46,140 --> 00:00:47,600 the documentation. 10 00:00:47,640 --> 00:00:54,150 So if I head back over to the request module page and scroll down to the table of contents way near 11 00:00:54,150 --> 00:00:56,990 the bottom we have all available options. 12 00:00:57,000 --> 00:01:01,620 If we click this this is going to list out all of the options we can use. 13 00:01:01,620 --> 00:01:06,180 Now up top we already have the you are Al option which we've already used. 14 00:01:06,180 --> 00:01:11,550 If we scroll down the list a little ways we're going to see a Jason option. 15 00:01:11,550 --> 00:01:19,350 Jason in lower case can get set to equal True or false in our case we're going to set Jason to true 16 00:01:19,590 --> 00:01:23,450 which is going to have the request module automatically pass. 17 00:01:23,490 --> 00:01:25,860 Jason responses for us. 18 00:01:25,860 --> 00:01:28,540 So over inside of our code what do we need to do. 19 00:01:28,590 --> 00:01:31,500 We're going to add a second property onto this object. 20 00:01:31,500 --> 00:01:36,720 So right here alongside of you are L we'll set up Jason in lower case. 21 00:01:36,720 --> 00:01:38,070 This is important. 22 00:01:38,160 --> 00:01:40,700 If you use uppercase it's not gonna work. 23 00:01:40,920 --> 00:01:47,010 Then we're going to set it equal to the Boolean true saying we would like a request to pass this as 24 00:01:47,280 --> 00:01:48,160 Jason. 25 00:01:48,300 --> 00:01:50,520 Now from here that means response. 26 00:01:50,520 --> 00:01:53,100 That body is already going to be an object. 27 00:01:53,100 --> 00:01:56,130 There is no need to actually pass it. 28 00:01:56,130 --> 00:01:59,690 So let's go ahead and change what we're doing inside of our function. 29 00:01:59,760 --> 00:02:06,390 Right here I am going to use console dialog to print the same stuff using our new setup. 30 00:02:06,510 --> 00:02:14,060 That would be first up response response dot body still exists though since we've set Jason to true 31 00:02:14,230 --> 00:02:15,460 is no longer a string. 32 00:02:15,500 --> 00:02:22,520 It is now the past object from there we're going to access currently which is what we were already accessing 33 00:02:22,610 --> 00:02:23,270 and dumping. 34 00:02:23,330 --> 00:02:25,920 That's what we're seeing down below. 35 00:02:25,940 --> 00:02:31,040 This is Andrew with another interruption as I mentioned in the last lesson of the current weather data 36 00:02:31,070 --> 00:02:33,230 for Dark Sky was on currently. 37 00:02:33,290 --> 00:02:37,100 But the current weather data for weather stack is on current. 38 00:02:37,100 --> 00:02:44,150 So if you're using the weather stack API you would want to access response dot body dot current as shown 39 00:02:44,150 --> 00:02:46,410 below. 40 00:02:46,410 --> 00:02:48,070 Now we can save app dot and J. 41 00:02:48,060 --> 00:02:51,450 S I can rerun the program and what do we get. 42 00:02:51,450 --> 00:02:53,510 We get the exact same response. 43 00:02:53,520 --> 00:02:59,670 I have my object showing up with my current information it's still clear and the temperature has increased 44 00:02:59,670 --> 00:03:04,340 a little bit to fifty seven point five five degrees. 45 00:03:04,470 --> 00:03:10,020 So now that request is passing the Jason for us we don't have to manually add that code every single 46 00:03:10,020 --> 00:03:15,080 time we're trying to make an H TTP request from node j as a firm here. 47 00:03:15,090 --> 00:03:18,770 I want to focus on printing a forecast to the user. 48 00:03:18,840 --> 00:03:24,030 Now that means we have to figure out what data to include and what to leave off and that can be tricky 49 00:03:24,030 --> 00:03:28,200 to do when you're looking at a dump of your data from the terminal. 50 00:03:28,200 --> 00:03:35,230 I find it much easier to use the browser to explore what data I want to include from a Jason response. 51 00:03:35,230 --> 00:03:41,250 Now currently the information we're seeing is very hard to pass since it is just a Jason string. 52 00:03:41,250 --> 00:03:47,480 There are chrome extensions out there though that allow you to see nice past formatted data. 53 00:03:47,490 --> 00:03:52,870 There are extensions for other browsers as well like Chrome Firefox and Internet Explorer. 54 00:03:52,890 --> 00:04:00,560 So what I'm going to do is search chrome extension and the one we're going to use is called Jason for 55 00:04:00,560 --> 00:04:04,840 matter though there are literally dozens of different options out there. 56 00:04:04,880 --> 00:04:09,540 Right here I have the chrome extension and all I'm going to do is install it. 57 00:04:09,590 --> 00:04:16,860 I'll take a quick moment to add it to Chrome and once we have it installed successfully we can go ahead 58 00:04:16,860 --> 00:04:20,250 and move back to that page refresh things. 59 00:04:20,250 --> 00:04:26,250 And this time the chrome extension is going to notice that Jason has been returned and it's going to 60 00:04:26,250 --> 00:04:27,640 pass it for us. 61 00:04:27,840 --> 00:04:32,810 Now over here with this particular extension I can also view the raw data should I want to. 62 00:04:33,090 --> 00:04:36,090 But the whole goal is to view the past data. 63 00:04:36,090 --> 00:04:41,070 Now we can collapse the various properties easily navigating what we have here. 64 00:04:41,160 --> 00:04:42,830 So we have this root object. 65 00:04:42,840 --> 00:04:50,610 It starts up here on line 1 and it gets closed way way down below at the very end of this object. 66 00:04:50,640 --> 00:04:56,930 So way down here on the last line everything inside of there is part of that object. 67 00:04:56,940 --> 00:05:01,320 Now this object is accessible to us as body. 68 00:05:01,350 --> 00:05:08,790 So an IMAX guessing response dot body I am accessing this object from there I can grab any of its properties 69 00:05:08,820 --> 00:05:09,880 like currently. 70 00:05:09,930 --> 00:05:16,500 Which is the fourth one listed that's why response dot body dot currently works. 71 00:05:16,500 --> 00:05:23,460 I could also use response dot body dot time zone as shown here to get the time zone for the current 72 00:05:23,640 --> 00:05:24,810 location. 73 00:05:24,810 --> 00:05:30,390 So now we have a slightly better idea as to how we're accessing this information below. 74 00:05:30,390 --> 00:05:35,240 Currently we have a minute early so we can get a minute by minute forecast. 75 00:05:35,280 --> 00:05:41,790 If I was to collapse that we have hourly below that we have daily and below that we have some flags 76 00:05:41,940 --> 00:05:47,100 and we also have the offset which are not particularly useful for our purposes. 77 00:05:47,100 --> 00:05:48,870 Now what are we trying to do here. 78 00:05:48,870 --> 00:05:54,450 Well currently we're just going to use the currently property that we do have other forecast information 79 00:05:54,450 --> 00:05:58,710 we could use to get even more data which we'll explore a little later. 80 00:05:58,710 --> 00:06:05,040 So for now we're just going to focus on this object and all of the properties are values we can use. 81 00:06:05,070 --> 00:06:10,020 Let's go ahead and talk about exactly what type of forecast we'd like to print down below. 82 00:06:10,020 --> 00:06:12,210 I have some challenged comments. 83 00:06:12,210 --> 00:06:17,970 It's going to be up to you to use the information on currently to print a little message using that 84 00:06:18,000 --> 00:06:19,800 actual information. 85 00:06:19,830 --> 00:06:22,490 So in general the goal is to print something like this. 86 00:06:22,590 --> 00:06:29,880 It is currently fifty eight point five five degrees out there is a zero percent chance of rain. 87 00:06:29,910 --> 00:06:36,480 Now this piece of information the current temperature and this piece of information the chance of precipitation. 88 00:06:36,510 --> 00:06:39,420 They're both available on that currently object. 89 00:06:39,420 --> 00:06:41,020 I have a temperature property. 90 00:06:41,130 --> 00:06:46,380 This is where I get the temperature from and I also have properties related to precipitation. 91 00:06:46,380 --> 00:06:51,580 Right here I have pre sip probability currently at zero. 92 00:06:51,700 --> 00:06:54,870 This is Andrew from the future with another quick interruption. 93 00:06:54,880 --> 00:06:59,230 So with the weather stock API we have access to a different set of weather data. 94 00:06:59,380 --> 00:07:04,840 So let's talk about what's going to need to change and we'll get started by exploring the root properties 95 00:07:04,840 --> 00:07:07,540 we have on our Jason response. 96 00:07:07,540 --> 00:07:09,290 So right here there are three. 97 00:07:09,400 --> 00:07:15,340 We get started with the request property which contains information about the request that weather stack 98 00:07:15,340 --> 00:07:16,340 processed. 99 00:07:16,420 --> 00:07:18,790 We have the latitude and longitude. 100 00:07:18,790 --> 00:07:21,520 We also have the language and the units. 101 00:07:21,520 --> 00:07:23,560 We're not going to use any of that data. 102 00:07:23,590 --> 00:07:25,080 So let's collapse it. 103 00:07:25,090 --> 00:07:30,160 Next up we have information about the location that we're viewing the weather data for. 104 00:07:30,220 --> 00:07:30,740 Right here. 105 00:07:30,820 --> 00:07:33,590 I can see this is for North Beach California. 106 00:07:33,610 --> 00:07:35,780 Let's collapse location as well. 107 00:07:35,890 --> 00:07:41,830 That leaves the last property of the third one which is current current contains the current weather 108 00:07:41,830 --> 00:07:42,520 data. 109 00:07:42,520 --> 00:07:46,060 And this is the property that you'll need to work with for the challenge. 110 00:07:46,060 --> 00:07:52,040 Now if we head over to visual studio code I've made some changes to what you're supposed to do. 111 00:07:52,060 --> 00:07:54,920 So this right here should be exactly what you have. 112 00:07:54,940 --> 00:08:00,390 I have my weather stack U.R.L. setup and I'm accessing response dot body dot current. 113 00:08:00,400 --> 00:08:04,220 All I've done is changed the challenge comments down below. 114 00:08:04,240 --> 00:08:09,790 So what you'll end up doing is printing something like the following it is currently 9 degrees out. 115 00:08:09,790 --> 00:08:11,650 It feels like five degrees out. 116 00:08:11,950 --> 00:08:17,800 So here we are using the temperature and the apparent temperature the feels like temperature for when 117 00:08:17,800 --> 00:08:20,800 we account for things like wind and humidity. 118 00:08:20,920 --> 00:08:27,100 So you can access both of the temperature and the feels like temperature on that current property. 119 00:08:27,100 --> 00:08:32,830 So right over here we have current you can access the temperature on temperature right here and you 120 00:08:32,830 --> 00:08:37,590 can access the apparent temperature on fields like which we have down below. 121 00:08:37,630 --> 00:08:41,460 So for this forecast I can see the temperature is 10. 122 00:08:41,470 --> 00:08:43,370 Well the feels like is eight. 123 00:08:43,420 --> 00:08:46,950 So there must be some windchill factoring into the difference. 124 00:08:47,020 --> 00:08:52,210 So this is what you'll end up working with you'll end up printing something like this using the weather 125 00:08:52,210 --> 00:08:53,290 stack API. 126 00:08:53,680 --> 00:08:55,800 OK that is it for the update. 127 00:08:55,810 --> 00:09:02,930 Let's jump back into the original lesson so using these two pieces of information we want to generate 128 00:09:02,930 --> 00:09:04,680 the following forecast. 129 00:09:04,730 --> 00:09:10,760 That means you're going to comment out this line or remove it and add another council dot log call in 130 00:09:10,850 --> 00:09:12,220 to print your forecast. 131 00:09:12,320 --> 00:09:14,770 From there you're going to test your work. 132 00:09:14,810 --> 00:09:20,630 So you want to run the script and make sure you're seeing your string with the correct values added 133 00:09:20,810 --> 00:09:21,730 inside. 134 00:09:21,830 --> 00:09:27,650 Take as much time as you need to generate this string using those two pieces of dynamic information. 135 00:09:27,710 --> 00:09:31,820 And when you're done come back and click play and we'll work through it together 136 00:09:35,830 --> 00:09:36,550 how that go. 137 00:09:36,550 --> 00:09:39,700 Let's get things started by working with our message. 138 00:09:39,700 --> 00:09:45,220 So I'm going to use console dot log to print something and that something is the string right here with 139 00:09:45,220 --> 00:09:47,310 those two dynamic values included. 140 00:09:47,620 --> 00:09:51,350 So we start off with some static text I'll create that in a string. 141 00:09:51,370 --> 00:09:54,660 It is currently followed by a space. 142 00:09:54,820 --> 00:09:58,020 Then we're going to concatenate on the actual temperature. 143 00:09:58,300 --> 00:09:59,580 So like we did before. 144 00:09:59,650 --> 00:10:03,680 That's going to be response dot body dot currently. 145 00:10:03,910 --> 00:10:07,090 That's going to bring us to this object right here. 146 00:10:07,090 --> 00:10:11,500 And on that object we have the temperature property which is the one we're looking for. 147 00:10:11,530 --> 00:10:15,260 So dot temperature excellent. 148 00:10:15,280 --> 00:10:21,730 Now after the temperature we go back to some static text so I'll concatenate on another string and we 149 00:10:21,730 --> 00:10:26,710 will start with a space the space between the temperature and the D in degrees. 150 00:10:26,710 --> 00:10:33,240 Now I'll start typing out degrees out period followed by the start of the next sentence. 151 00:10:33,260 --> 00:10:37,970 There is a space and in here we have to insert the. 152 00:10:37,970 --> 00:10:40,190 Percent chance of rain. 153 00:10:40,220 --> 00:10:49,350 So once again I'm going to concatenate on a value that will be a response dot body dot currently dot. 154 00:10:49,430 --> 00:10:52,950 And right here we are looking for preset probability. 155 00:10:53,090 --> 00:10:57,360 So precision using these shorthand for the word probability. 156 00:10:57,470 --> 00:11:05,300 And finally we can concatenate on the closing static text so after our probability it's percent chance 157 00:11:05,360 --> 00:11:06,030 of rain. 158 00:11:06,050 --> 00:11:11,740 So right here a percent chance of rain. 159 00:11:12,100 --> 00:11:13,050 Excellent. 160 00:11:13,060 --> 00:11:20,210 Now we have this really long string created and we can go ahead and actually test our work I'm back 161 00:11:20,210 --> 00:11:21,770 with another quick interruption. 162 00:11:21,770 --> 00:11:26,960 If you're working with the weather stack API let's go over the console log call for that. 163 00:11:27,320 --> 00:11:33,470 So we start off with it's currently the string followed by the current temperature right here. 164 00:11:33,470 --> 00:11:40,700 You should have access that firm response dot body dot current dot temperature after the current temperature. 165 00:11:40,700 --> 00:11:43,700 We move on to more static text right here. 166 00:11:43,700 --> 00:11:50,240 I have degrees out which finishes up the first sentence from there we start our second sentence with 167 00:11:50,300 --> 00:11:57,230 it feels like and then we get the apparent temperature on a response dotted body dot current dot feels 168 00:11:57,230 --> 00:12:03,260 like from there we wrap up the second sentence with degrees out in eight period. 169 00:12:03,260 --> 00:12:05,720 So this is the solution you should have come up with. 170 00:12:05,720 --> 00:12:11,990 If you were working with the weather stack API now we can test our work down below by just rerunning 171 00:12:12,010 --> 00:12:20,450 app dot J.S. so I'll use node space app dot J.S. and if I run things I would expect to get the correct 172 00:12:20,450 --> 00:12:21,910 result right here. 173 00:12:22,010 --> 00:12:24,620 I get it is currently 10 degrees out. 174 00:12:24,620 --> 00:12:28,340 It feels like seven degrees out which is fantastic. 175 00:12:28,340 --> 00:12:35,380 With that change made let's head back into the regular video so I'm going to rerun the program from 176 00:12:35,380 --> 00:12:42,760 the terminal down below to start I'll use clear to clear the current output then node space act J asked 177 00:12:42,760 --> 00:12:49,300 to rerun the program and what do I get I get it is currently fifty eight point two two degrees out there 178 00:12:49,300 --> 00:12:57,340 is a zero percent chance of rain which is fantastic we were able to make an H TTP request for data parts 179 00:12:57,340 --> 00:13:04,000 that data into a format that was usable and actually use it inside of our node J.S. application in a 180 00:13:04,000 --> 00:13:10,890 meaningful way or this update what we'll end up doing is figuring out how we can change the units for 181 00:13:10,890 --> 00:13:12,370 the data that comes back. 182 00:13:12,450 --> 00:13:18,390 So right now we're seeing the temperature in Celsius but if we want to we could request that temperature 183 00:13:18,390 --> 00:13:21,610 from weather stack in Kelvin or Fahrenheit. 184 00:13:21,690 --> 00:13:27,600 Now in the original lesson what we did is we explored the dark sky API to figure out how to get that 185 00:13:27,600 --> 00:13:28,150 done. 186 00:13:28,260 --> 00:13:34,740 Then we changed our U.R.L. and we watched the data change in the response we'll end up doing that exact 187 00:13:34,740 --> 00:13:36,700 same thing for weather stack. 188 00:13:36,720 --> 00:13:41,870 So first up let's check out the documentation so we can figure out how to get this done. 189 00:13:42,090 --> 00:13:47,420 I'll switch over to the browser I'll switch over to the quick start guide we explored earlier. 190 00:13:47,550 --> 00:13:53,030 Then I'll scroll to the top and right here we can head over to whether stacks documentation. 191 00:13:53,400 --> 00:13:58,890 So I'll head over to the documentation page and right here we can learn all the different ways we can 192 00:13:58,890 --> 00:14:01,500 work with the weather stack API. 193 00:14:01,500 --> 00:14:07,640 Now what we're looking for can be found in the left hand side bar so down below we have getting started. 194 00:14:07,650 --> 00:14:12,210 We have API features and we have options under options. 195 00:14:12,240 --> 00:14:14,880 We are looking for the units parameter. 196 00:14:15,060 --> 00:14:21,750 So for our particular U.R.L. you'll remember that we set up our API key and we also set up our query 197 00:14:21,990 --> 00:14:24,390 what we'll do here is set up something else. 198 00:14:24,390 --> 00:14:31,200 We will set up units so I'll click on units parameter that will bring me down to the documentation. 199 00:14:31,200 --> 00:14:38,310 And right here I can see that I can set units equal to one of the following values if I set units equal 200 00:14:38,310 --> 00:14:39,110 to m. 201 00:14:39,180 --> 00:14:41,820 I'll see my data using the metric system. 202 00:14:41,820 --> 00:14:43,760 Now this is the default option. 203 00:14:43,830 --> 00:14:47,090 So we're already seeing our temperature in Celsius. 204 00:14:47,190 --> 00:14:53,100 If I switch the value over to S for scientific I would see my temperature in Kelvin. 205 00:14:53,100 --> 00:14:59,860 And finally if I switched units over to F for Fahrenheit I could view the temperature in Fahrenheit. 206 00:14:59,910 --> 00:15:02,680 So right here let's explore how we can get that done. 207 00:15:02,760 --> 00:15:08,550 And since I live in the States I'll be switching things over to Fahrenheit so I'll head back over to 208 00:15:08,610 --> 00:15:13,920 visual studio code and what we'll end up doing is adding another query parameter. 209 00:15:13,920 --> 00:15:16,700 So right here I have my first one access key. 210 00:15:16,860 --> 00:15:24,180 If I scroll over I have my second one query will add a third one so right at the end I'll use an ampersand. 211 00:15:24,180 --> 00:15:27,230 Then we can set up a another key value pair. 212 00:15:27,240 --> 00:15:32,490 So right here I'll go ahead and use the key of units followed by the value. 213 00:15:32,490 --> 00:15:34,530 So units equals right here. 214 00:15:34,530 --> 00:15:41,880 I'll use f once again you can use m intensity the temperature in Celsius s to see it in Kelvin or F 215 00:15:41,940 --> 00:15:43,820 to see it in Fahrenheit. 216 00:15:43,890 --> 00:15:47,970 So with units set up let's say you've asked J.S. down below. 217 00:15:47,970 --> 00:15:55,320 All I'm going to do is rerun the program so I'll run apt J ask through node once again and if I do right 218 00:15:55,320 --> 00:15:57,930 here I can see my data looks pretty different. 219 00:15:58,020 --> 00:16:01,140 Right here I am seeing my temperatures and Fahrenheit. 220 00:16:01,140 --> 00:16:05,430 It's currently 45 degrees and it feels like 41. 221 00:16:05,430 --> 00:16:10,700 So now we know how we can customize the units that are coming back from our API. 222 00:16:10,770 --> 00:16:16,290 Now at this point in the original lesson we had added just one additional piece of information to our 223 00:16:16,290 --> 00:16:19,070 weather forecast and that was it for the lesson. 224 00:16:19,110 --> 00:16:24,290 So we added that additional piece of information as the very first thing we render. 225 00:16:24,450 --> 00:16:30,480 So to explore what will end up adding let's head back over to our API request in the browser so I'll 226 00:16:30,480 --> 00:16:32,500 switch back over to the browser. 227 00:16:32,610 --> 00:16:38,700 I'll head over to our API response and right here what we'll end up doing is starting things off with 228 00:16:38,700 --> 00:16:41,080 a general description of the weather. 229 00:16:41,130 --> 00:16:43,650 Now we could collapse at the request property. 230 00:16:43,650 --> 00:16:49,320 We could also collapse the location property right here that just leaves us with current and what will 231 00:16:49,320 --> 00:16:52,740 end up doing is printing the weather description. 232 00:16:52,740 --> 00:16:56,460 So right here that would be overcast and that will show up first. 233 00:16:56,460 --> 00:17:02,010 Now it will always be overcast sometimes it will be sunny or partly cloudy whatever it is. 234 00:17:02,070 --> 00:17:06,670 That's what we'd like to show up so we can access that data on current. 235 00:17:06,750 --> 00:17:11,320 Then from there we would access it on the weather descriptions array. 236 00:17:11,430 --> 00:17:17,080 What we'll do is pull in the first weather description and render that as part of our forecast. 237 00:17:17,220 --> 00:17:23,910 We can get that done by heading over to app J.S. and adding that as the very first thing in console 238 00:17:24,110 --> 00:17:24,980 dialogue. 239 00:17:24,990 --> 00:17:32,370 So right here that would be response dot body from here we will pull something off of the current property 240 00:17:32,670 --> 00:17:34,520 right here as we just explored. 241 00:17:34,590 --> 00:17:38,840 That was Dot whether underscore descriptions. 242 00:17:38,850 --> 00:17:41,820 Now remember that is an array of strings. 243 00:17:41,820 --> 00:17:45,900 So I'll use bracket notation to grab the first item by its index. 244 00:17:45,900 --> 00:17:48,310 That would be an index of 0. 245 00:17:48,330 --> 00:17:54,630 Next up right after that what I'll do is use the plus operator to concatenate the rest of my string 246 00:17:54,660 --> 00:17:55,860 onto the end. 247 00:17:55,860 --> 00:18:02,460 Now in this case if we used the current data what we would see right here is the word overcast followed 248 00:18:02,460 --> 00:18:03,870 directly by it. 249 00:18:03,900 --> 00:18:09,260 There wouldn't even be a space in between what I'll end up doing is starting this string off with a 250 00:18:09,260 --> 00:18:10,970 period end of space. 251 00:18:10,970 --> 00:18:15,820 So this data looks like it's in its own sentence now that we have that in place. 252 00:18:15,860 --> 00:18:19,550 We can save things and test our work now in the original video. 253 00:18:19,610 --> 00:18:23,480 We added something similar though it came from a different property. 254 00:18:23,480 --> 00:18:27,500 So when you do watch the original video you'll see something different right here. 255 00:18:27,560 --> 00:18:30,910 But this is what we need for the weather stack API. 256 00:18:31,070 --> 00:18:34,730 So down below let's just rerun our program once again. 257 00:18:34,730 --> 00:18:38,780 And if I do right here we can see exactly what we had before. 258 00:18:38,900 --> 00:18:42,720 Now it looks like in the last couple of minutes the weather did indeed change. 259 00:18:42,740 --> 00:18:48,030 So right here I see partly cloudy followed by It is currently 45 degrees out. 260 00:18:48,050 --> 00:18:50,530 It feels like 41 degrees out. 261 00:18:50,600 --> 00:18:51,760 So this is awesome. 262 00:18:51,800 --> 00:18:53,770 We now have a summary of the weather. 263 00:18:53,870 --> 00:18:59,510 Then we have the actual temperature followed by the apparent temperature when we factor in humidity 264 00:18:59,720 --> 00:19:00,900 and wind. 265 00:19:00,920 --> 00:19:04,660 So in the original video that's where we had stopped for this one. 266 00:19:04,760 --> 00:19:10,670 What we'll end up doing is moving on to the next lesson where it will be up to you to work with a completely 267 00:19:10,670 --> 00:19:12,140 different API. 268 00:19:12,140 --> 00:19:17,870 Now the good news is that when it comes to these big updates because of the API change we're basically 269 00:19:17,870 --> 00:19:18,560 done. 270 00:19:18,560 --> 00:19:23,510 There's a couple of small updates throughout the next several lessons but there's actually nothing that 271 00:19:23,510 --> 00:19:25,400 needs to change in the next one. 272 00:19:25,430 --> 00:19:31,310 It was really just the last one and this one that required some more substantial changes now that we 273 00:19:31,310 --> 00:19:34,000 have that code in place though we are good to go. 274 00:19:34,040 --> 00:19:40,400 So let's jump right into the next one which is a challenge for you to fetch data from a new API.