<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by DM Heli on Medium]]></title>
        <description><![CDATA[Stories by DM Heli on Medium]]></description>
        <link>https://medium.com/@shiela.mms?source=rss-865166471550------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*kxGOAAqFuqZe_XDeDlpMcQ.png</url>
            <title>Stories by DM Heli on Medium</title>
            <link>https://medium.com/@shiela.mms?source=rss-865166471550------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 15:29:33 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shiela.mms/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Geopandas for mapping university locations]]></title>
            <link>https://medium.com/@shiela.mms/geopandas-for-mapping-university-locations-9455307c5791?source=rss-865166471550------2</link>
            <guid isPermaLink="false">https://medium.com/p/9455307c5791</guid>
            <category><![CDATA[geopandas]]></category>
            <category><![CDATA[geographic-data]]></category>
            <category><![CDATA[education-technology]]></category>
            <category><![CDATA[data-visualization]]></category>
            <dc:creator><![CDATA[DM Heli]]></dc:creator>
            <pubDate>Mon, 19 Sep 2022 22:26:33 GMT</pubDate>
            <atom:updated>2022-09-19T22:26:33.176Z</atom:updated>
            <content:encoded><![CDATA[<h4>Create a map of the counties of top universities in the United Kingdom</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VEVX6p0VjTOMs4oH6-SIWA.png" /></figure><p>Geopandas is a python library extending the <a href="https://pypi.org/project/pandas/">Pandas</a> library to enable manipulation of geographic dataframes. These dataframes are called GeoDataFrames, which contain standard dataframe properties as well as a <em>geometry</em> column to store geographic elements such as point coordinates. In this article, we’ll explore geopandas to manipulate and visualise education data taken from publicly accessible websites and data repositories. The first section will walk you through the problem that we want to explore, and the rest of the article details the steps to create a sample geopandas map in the context of the given problem.</p><p>All the code and data in this article can be found in my Github repository <a href="https://github.com/shielamms/geopandas-education-data"><strong>geopandas-education-data</strong></a><strong>. Checkout the Jupyter notebook here:</strong></p><p><a href="https://github.com/shielamms/geopandas-education-data/blob/master/Where%20are%20the%20top%20UK%20universities%3F%20Geopandas.ipynb">geopandas-education-data/Where are the top UK universities? Geopandas.ipynb at master · shielamms/geopandas-education-data</a></p><h3>‘Where are the top universities in the UK?’</h3><p>Working in the higher education sector, I work closely on engineering pipelines to collect and process university data worldwide. Sometimes we are able to obtain location data of university campuses, especially in the US and UK. Location is particularly important to prospective undergraduate students when shortlisting universities that they are interested in. The prestige of universities is also a big factor for international students’ choice of which university to go to, and the UK is not lacking in these high-performing institutions.</p><p>With the idea that prospective students are more likely to consider prestigious universities, we would want to give them more information about the environment that they will be in. This could be done in several ways, one of which is getting geographical data about these universities, like the town or county and some description about the culture and cost of living. The first step here is finding where those universities are located and which areas have the highest concentrations of top universities so that we may improve our supporting data about them. This method would help us focus our data collection efforts on the locations that we think would provide the highest value to students. Moreover, we’ll limit this question only to UK universities.</p><h4>Data Sources</h4><p>All the datasets listed below were renamed and uploaded into the <a href="https://github.com/shielamms/geopandas-education-data/tree/master/datasets/UK"><strong>datasets folder of the Github repository</strong></a>.</p><ol><li><strong>Base Map of UK</strong></li></ol><p>First, we’ll need data to create our base map of the UK. This could be a map of region or county divisions. Geopandas has a small collection of built-in maps, but its features are quite limited that we won’t be able to see more granular data within the UK. For example, the code below plots a simple map of the UK using the naturalearth_lowres dataset within geopandas.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/1fe75081e64a41e53522fd79a94de737/href">https://medium.com/media/1fe75081e64a41e53522fd79a94de737/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*7x2kcJPNxlEMLk6gfL-zWA.png" /><figcaption><strong>Figure 1: </strong>A basic map of UK from the `naturaleath_lowres` dataset</figcaption></figure><p>Luckily, with a quick google search, we were able to find a shapefile for UK county boundaries: <a href="https://www.ukpostcode.net/shapefile-of-uk-administrative-counties-wiki-16.html">Shapefile of UK Administrative Counties in ukpostcode.net</a>. This shapefile contains polygons of UK administrative areas by county.</p><p>2. <strong>List of universities</strong></p><p>Next, we’ll need to get a list of UK universities and their locations. The most reliable source I could find was the Universities and Colleges Admissions Service (UCAS), which is the UK’s main service for higher education applications. The comprehensive university list can be found in the <a href="https://www.ucas.com/explore/unis?letter=a">UCAS websit</a>e.</p><p>Notice that each university in that list has the county on the bottom of its name (e.g., “Anglia Ruskin University” is in Cambridge). You can also click on a university and check its full address in its profile page. For simplicity, we can just take the county name from the address, since we can match these to our counties data from above.</p><p>For this particular data, there are no data files to download, so we’ll have to scrape the website instead. I’ve written a utility script in Python to scrape the university names and addresses via the `requests` and `BeautifulSoup` libraries. You can check the <a href="https://github.com/shielamms/geopandas-education-data/tree/master/utils">scraper code in my repository</a> (scraper.py). The output of this scraper is a csv file called `<a href="https://github.com/shielamms/geopandas-education-data/blob/master/datasets/UK/ucas_universities_2022.csv">ucas_universities_2022.csv</a>`.</p><p>3. <strong>List of Top universities</strong></p><p>There are plenty of online sources that provide a list of “top” universities in the UK, but which one you’ll need would depend on how you define the criteria of a <em>top university</em>. Most ranking systems assess institutions based on admissions standards, quality of research programmes, or a combination of many different factors. For this exercise, I’ve chosen the <a href="https://www.thecompleteuniversityguide.co.uk/league-tables/rankings">University League Tables in the Complete University Guide</a>, which ranks universities based on their entry standards. <a href="https://www.thecompleteuniversityguide.co.uk/sector/insights/university-and-subject-league-tables-methodology">According to their website</a>, these entry standards are measured by the average<em> UCAS tariff score</em>, a standard grade conversion scale in the UK, of new undergraduate students.</p><p>The University League tables can be downloaded from the <a href="https://www.thecompleteuniversityguide.co.uk/league-tables/rankings">Complete University Guide website</a> for free as CSV files.</p><h3>Building a map with Geopandas</h3><p>Now that we have some data, it’s time to look into the dataframes and assess what we can use for our analyses.</p><h4>Base Map: UK Counties</h4><p>The first layer of our map will show the boundaries of counties within the UK. There are various coordinate reference systems (or CRS) to represent a location or an area on a map, so when first reading the shapefile from the data source mentioned above, as a standard practice, we’ll first want to know its CRS.</p><pre>import geopandas as gpd<br>counties = gpd.read_file(&#39;datasets/UK/UK_counties/Map_UK.shp&#39;)<br>counties.crs</pre><p>The output of the crs property looks something like this:</p><pre>&lt;Derived Projected CRS: EPSG:32630&gt;<br>Name: WGS 84 / UTM zone 30N<br>Axis Info [cartesian]:<br>- E[east]: Easting (metre)<br>- N[north]: Northing (metre)<br>Area of Use:<br>- name: ...<br>- bounds: (-6.0, 0.0, 0.0, 84.0)<br>Coordinate Operation:<br>- name: UTM zone 30N<br>- method: Transverse Mercator<br>Datum: World Geodetic System 1984 ensemble<br>- Ellipsoid: WGS 84<br>- Prime Meridian: Greenwich</pre><p>The output shows that the geometry data in the shapefile follows the EPSG 32630 standard. This information will be useful for us later when we’re adding more layers to our map.</p><p>For now, we can plot of the counties dataset to see what it looks like. I usually format my base maps with neutral colours at first, but you can play with other colours as much as you want.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/2d58d4301e2cb11fd84596458fcdb035/href">https://medium.com/media/2d58d4301e2cb11fd84596458fcdb035/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nj4CJXSEQeW_i08IPMmb-Q.png" /><figcaption><strong>Figure 2:</strong> Sample plot output of the UK counties dataset</figcaption></figure><p>You can do some additional plotting just to see how well the shapefile represents smaller counties, for example, the counties in the Greater London area. In the code snippet below,</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/65ddb38c7781b09a970cc750550e8cb7/href">https://medium.com/media/65ddb38c7781b09a970cc750550e8cb7/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*r3LZXGbE6P-xsaolx30bbQ.png" /><figcaption><strong>Figure 3:</strong> London counties highlighted in the map of England. Since the metropolitan counties are quite small areas clustered within Greater London, it might be worth just treating all of London as a single “county” in our dataset.</figcaption></figure><h4>UK Universities from UCAS</h4><p>As stated in the data sources above, the list of universities were scraped from the UCAS website and saved into a csv file. To read the csv file and work on the data as a dataframe, we’ll need to use pandas for standard dataframe creation:</p><pre>import pandas as pd</pre><pre>ucas_unis = pd.read_csv(&#39;datasets/UK/ucas_universities_2022.csv&#39;)<br>ucas_unis.head()</pre><p>The head() outputs the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IhaD-uzHNaV1xKdyVvunhQ.png" /><figcaption><strong>Figure 4: </strong>First 5 rows of the ucas universities dataset</figcaption></figure><p>So now that we have the county data of each university, we can already use this to map with our counties dataset. We can either join the two dataframes right away (where all universities will be inner joined with counties), or filter the top universities first before joining with the counties dataframe (only top universities will be involved in the join — a smaller dataset). If we’re working on much large datasets, the latter option may be better. We won’t need the former option anyway since we don’t want to map all universities. But for the sake of exploring the dataset, let’s take a look at the first option and see if we can map all university counties.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f98b145ed6a8ed37d955a8d6edeab22a/href">https://medium.com/media/f98b145ed6a8ed37d955a8d6edeab22a/href</a></iframe><p>Notice that from line 37, there is a whole section for setting annotations, which can be text or arrows as additional visual guides. To add an annotation to a plot, you’ll need the x and y coordinates on which you want geopandas (with matplotlib plotting styles under the hood) to put your annotation. In the example above, the plt.annotate() takes the following distinctive parameters:</p><ol><li>xy parameter to specify the location of the annotation on the map;</li><li>arrowprops to specify that we want to add an arrow to point to the xy</li><li>xytext to specify the x and y coordinates of the text at the end of the arrow.</li></ol><p>The code above outputs the following:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xnFPBgySq1kmmFKyhv0AbA.png" /><figcaption><strong>Figure 5: </strong>Heat map of university counts per county in the UK</figcaption></figure><p>The output above does not make it any easier for us to compare concentrations of universities in particular counties. A lot of the data is in yellow (around 10 universities), but the maximum value is 60. This signals that there must be an outlier somewhere in our data — a county that’s quite small that it’s hardly recognisable in the map. We can easily find that out by checking which counties have the most number of universities:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0lLD03jefyJ7kPsFLUB6WQ.png" /><figcaption><strong>Figure 6: </strong>Top 5 UK “counties” with the most number of universities</figcaption></figure><p>And true enough, there is one “county” — London, that is skewing our visualisation. It may have been caused by the limitation in our universities dataset. In fact, London is not technically a county. It’s just that the data we have scraped from the UCAS website assumes that all university addresses contain the real county name. It turns out that London universities’ addresses do not contain that information. Here’s an example in the website:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9MAPGk300cGg9Yqx8Vc2Sw.png" /><figcaption><strong>Figure 7: </strong>Sample location details of a university in London taken from the <a href="https://www.ucas.com/explore/unis/36dc6feb/london-metropolitan-university?studyYear=current">UCAS website</a></figcaption></figure><p>We can either improve our data collection (modifying our UCAS website scraper, for example), or just provisionally take it as a data limitation to improve on in your next development iteration. For simplicity, let’s take the 2nd option and move on.</p><p>We can take care of the skewness by just removing London from our map when we’re plotting <em>all </em>university counties in the UK, like this filter below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WRZ46DzuN48BReHK7grVOA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lFm4pB-hL_0Ho7WAiVhl8A.png" /><figcaption><strong>Figure 8: </strong>Heat map of university counts per county in the UK, excluding London</figcaption></figure><p>Now we can see that the maximum count is 12, and that there are more areas in the map on the darker gradient. You’ll be able to intuitively say that the highest concentrations of universities in the UK are along Yorkshire and the Midlands. Also, if you’re already familiar with UK city locations, notice that there are more universities along metropolitan areas, like Edinburgh (compared to the rest of Scotland), and Cardiff (compared to the rest of Wales).</p><h4>Top UK universities from University League Tables</h4><p>I chose to use the University League Tables just because it’s the easiest to obtain in csv format on the internet and the one with the clearest criteria for ranking.</p><pre>rankings = pd.read_csv(&#39;datasets/UK/university_ranks.csv&#39;)<br>rankings.head()</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U5uMMYRT21GZESpZ0hpDwg.png" /><figcaption><strong>Figure 9: </strong>First 5 rows in the rankings dataset</figcaption></figure><p>Now that we have the universities dataframe with counties data, we can then join this with the rankings dataframe. The code snippet below shows that after we’ve merged all universities and rankings data, we may want to plot only a certain X number of universities on the map. For example, we usually just want to know where the top 50 or top 100 universities are located. The top_X variable on line 6 filters only up to the top 50 universities.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/f98b145ed6a8ed37d955a8d6edeab22a/href">https://medium.com/media/f98b145ed6a8ed37d955a8d6edeab22a/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Et3MuQUCkTq3RuYCBrNZEg.png" /><figcaption><strong>Figure 10: </strong>Heat map of top university counts per county in the UK</figcaption></figure><p>Again, the output seems to be skewed to the yellow colours. Looking at the legend, the maximum number is 7 (at colour red), but the rendered map hardly has any red at all. Similar to what we’ve done a previous steps ago, London looks to be causing the skew, so we can simply remove London from our map and compare the results.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/cba945d94d99a707b1e3232e4197acde/href">https://medium.com/media/cba945d94d99a707b1e3232e4197acde/href</a></iframe><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ycLShZPfrwzFTMzdFnJo9w.png" /><figcaption><strong>Figure 11: </strong>Heat map of top university counts per county in the UK, excluding London</figcaption></figure><p>The final output shows that apart from London which has 7 of the top 50 universities, there are 6 other locations in the UK that each house 2 top-ranking universities. This could potentially be important information when we’re trying to personalise university recommendations to students who look into prestige or rankings. For example, a student looking into top universities in London and Edinburgh may want more information about these locations to compare how they might fit the culture and their budget for cost of living.</p><p>There are plenty of other ranking institutions that are free and open to download from the internet (QS rankings, for example). You can try out different versions of the map with different university ranking systems.</p><p>As we have seen, Geopandas is a powerful library for manipulating dataframes containing geographic data, and it’s much easier to learn if you’re already familiar with pandas dataframe operations. The current map is not the prettiest, I admit (it always takes me forever to choose map colours, only to end up with the blandest of styles), so feel free to fork <a href="https://github.com/shielamms/geopandas-education-data">my code repository</a> and change the styles on your own!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9455307c5791" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Understanding True Colour and False Colour Composites]]></title>
            <link>https://medium.com/@shiela.mms/understanding-true-colour-and-false-colour-composites-546455becda1?source=rss-865166471550------2</link>
            <guid isPermaLink="false">https://medium.com/p/546455becda1</guid>
            <category><![CDATA[remote-sensing]]></category>
            <category><![CDATA[visible-light]]></category>
            <category><![CDATA[google-earth-engine]]></category>
            <category><![CDATA[python]]></category>
            <dc:creator><![CDATA[DM Heli]]></dc:creator>
            <pubDate>Sat, 19 Mar 2022 23:17:45 GMT</pubDate>
            <atom:updated>2022-03-26T15:27:13.555Z</atom:updated>
            <content:encoded><![CDATA[<h4>A simple exploration of RGB and NIR Bands from Landsat Images using Google Earth Engine Python SDK</h4><p>Our eyes can only see a very small portion of the spectrum of light that surrounds us. This portion is called the “visible spectrum”, for which we have assigned names to the various shades of colour that we can see. Scientific instruments onboard satellites have sensors of light outside of our visible range in the electromagnetic spectrum, like infrared and ultraviolet light. But of course, even if we can produce an image from an infrared sensor, our eyes can’t see infrared. To visualise what objects look like with infrared eyes, we have to use colours from our visible spectrum and map them to what the infrared sensors detect.</p><p>An image is a <strong>“True Colour” </strong>composite if the colours in the image are the same colours that we see with our eyes — that is, a combination of red, green, and blue (RGB) light intensities. Our computer screens can represent one pixel as a set of RGB values, where each band is an integer from 0 to 255. For example, the following shade of green is represented as Red=229, Green=255, and Blue=204.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zwdgzZ9UWPbK_byW.png" /><figcaption>Check out the complete colour chart in <a href="https://www.rapidtables.com/web/color/RGB_Color.html">RapidTables</a></figcaption></figure><p>Meanwhile, an image is a <strong>“False Colour”</strong> composite if the colours in the image are a representation of the invisible band of light that was captured.</p><p>Remote sensors in satellites can “see” the invisible light from the sun’s radiation to the earth by measuring how much of that light is reflected from the earth’s surface. As a classic example, infrared light bounces off surfaces with higher levels of vegetation, but is absorbed by water. That means that a remote infrared sensor will see brighter light in a forested area, but oceans and other bodies of water on earth will appear dark.</p><p>Now, if we were to display that image in the infrared band, we can only do so with the colours in our visible bands. There are two ways to do this:</p><ol><li>Display infrared in one visible band, like greyscale, such that higher infrared reflectance would show as lighter grey, while lower infrared reflectance would appear darker grey to black; or</li><li>Display infrared as a combination of three visible bands: Red, Green, and Blue.</li></ol><p>The image on the left below is a true colour composite of an area on earth. The image on the right is a greyscale composite image of that same area captured in infrared. Most of the time, it is difficult for the naked eye to clearly identify the boundary between bodies of water and land from a true colour composite because of the mixing of colours. With false colour composites, these boundaries are much sharper because different types of surfaces reflect invisible light at much varied levels.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*WVOSBQlobJrCDX2D.png" /><figcaption>Composite images of Metro Manila and its neighbouring Laguna Lake. On the left: a true colour composite shows the water as green as its surrounding land areas, which could make the lake difficult to spot when we zoom out the map. On the right: The same image in the infrared band, represented by greyscale, which shows the higher contrast of the lake with its surrounding land area because of the difference in reflectiveness of infrared light on water and on land.</figcaption></figure><p>Let’s explore this a bit deeper using the Google Earth Engine API and the Surface Reflectance data from the Landsat 8 satellite.</p><h3>Let’s build a map from Google Earth!</h3><p>For this example, I’m going to get image data from the <a href="https://developers.google.com/earth-engine/datasets/catalog/LANDSAT_LC08_C02_T1_TOA#bands">Landsat 8 Satellite</a>, and get the median composites in true colour, false colour, and greyscale infrared in the year 2021. The subject of my image is the Taal Lake and Taal Volcano, situated some kilometres south of Manila, Philippines. The lake and its surrounding areas are a popular tourist destination close to the capital. The lake surrounds the the volcano, which is the 2nd most active volcano in the country.</p><p>Here’s the complete code if you want to go straight at it. Otherwise, feel free to skip past this next code block and into the walkthrough.</p><h4>Complete Code</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/bc1df1dd49b302d72b73483d43d4b76b/href">https://medium.com/media/bc1df1dd49b302d72b73483d43d4b76b/href</a></iframe><h4><strong>Walkthrough</strong></h4><p>First, we import the needed Google Earth Engine libraries and the Folium library to create an interactive map.</p><pre>import ee</pre><pre>import folium</pre><pre>import geehydro</pre><pre>ee.Initialize()</pre><p>Now let’s import the Landsat Image Collection. You can find more info about this dataset from the <a href="https://developers.google.com/earth-engine/datasets/catalog/LANDSAT_LC08_C02_T1_TOA#description">Google Earth Engine catalog page for Landsat 8</a>. We then filter only the images in the year 2021.</p><pre>images = ee.ImageCollection(&#39;LANDSAT/LC08/C02/T1_TOA&#39;)</pre><pre>date_filter = ee.Filter.date(&#39;2021-01-01&#39;, &#39;2022-01-01&#39;)</pre><pre>image = (images</pre><pre>         .filter(date_filter)</pre><pre>         .filter(ee.Filter.lt(&quot;CLOUD_COVER&quot;, 30))</pre><pre>        .median())</pre><p>The second filter is needed because we need to discard images where the clouds are covering the area we want to analyse. This filter (and by the way, there are “cloud masking” techniques in image composition which can be a subject for another article) is especially important when processing images from sensors that detect visible light. In other words, a satellite hovering on top of a cloudy area will see only clouds in visible light, which makes land and water surface analyses nearly impossible.</p><p>ee.Filter.lt(&quot;CLOUD_COVER&quot;, 30)</p><p>The above filter means that we’re getting images in the collection where the cloud cover is less than 30% of an image. Without it, the median composite would look like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HTpGFJfR337PeNk9.png" /><figcaption>Clouds significantly covering the region of interest in the composite</figcaption></figure><p>The next step is initialising the folium map. We tell folium to centre the map to the given [latitude, longitude] coordinates, and then zoom in to 11.5 levels. This area will be our region of interest.</p><pre>l8_map = folium.Map(location=[13.9999502, 121.011384], zoom_start=11.5)</pre><pre>l8_map.setOptions(&#39;SATELLITE&#39;)   #optional</pre><p>Calling setOptions is optional — it’s just mainly to tell folium to load a Google Maps Satellite layer. Without this, the map would just use the default OpenStreetMap base layer, which doesn’t matter in our current example.</p><p>We now have the base layer and filtered the dataset. The median() function gives us the composite, but we still need to separate the bands of light for our visualisation. Let’s start by visualising the image in true colour.</p><p><strong>Adding the True Colour Layer</strong></p><pre>true_color_params = {</pre><pre>    &#39;bands&#39;: [&#39;B4&#39;, &#39;B3&#39;, &#39;B2&#39;],</pre><pre>    &#39;min&#39;: 0,</pre><pre>    &#39;max&#39;: 0.4,</pre><pre>}</pre><pre>map_l8.addLayer(image, true_color_params, &#39;true color&#39;)</pre><p>The bands parameter in the above code snippet means the band or bands that we want to visualise. We can assign it a single band or a list of bands. If we provide only one band, the image will be represented in greyscale showing the relative intensities of the given band on our region of interest. If we provide a list of bands, each band will be mapped to a palette in Red, Green, and Blue, in that order. (If that sounds confusing, please read along. These thing can get counterintuitive).</p><p>According to the <a href="https://developers.google.com/earth-engine/datasets/catalog/LANDSAT_LC08_C02_T1_TOA#bands">Landsat 8 TOA Reflectance Data Documentation</a>, the Red, Green, and Blue optical bands can be referenced by the names B4, B3, and B2, respectively. So providing it as a list in the bands parameter, the B4 band will be represented by the Red colour palette, B3 will be represented by the Green palette, and B2 will be represented by the Blue palette. Take good care of the ordering of these bands on the list, as switching B4 and B3 positions would mean that the B4 (red light) will be represented by green colours, while B3 (green light) will be represented by red colours — which is confusing.</p><p>You may be asking — why do we need to do this mapping if red would just be represented by the red colour, green by the green colour, and blue by the blue colour? While it does sound like an overkill to do this for the visible spectrum, it would make a lot more sense for the invisible spectrum, which we can’t see and therefore need to represent with colours that we can see. We’ll get to that more in a little while.</p><p>Our next concerns are the min and max parameters. What are they? I was puzzled about them myself when I was starting out with the Google Earth Engine API, as there doesn’t seem to be any good documentation about them. The best resource I found about it was <a href="https://www.google.com/earth/outreach/learn/introduction-to-google-earth-engine/#earth-engine-explorer-0#data-range-4-12">an obscure article from Google Earth Outreach</a>. Here’s a quote from the page:</p><blockquote>Visualisation of data requires that a given value range be scaled between 0 and 255 for each band being displayed. The range parameter (min and max) allows you to adjust the range of values to display. The defined min value will be drawn to 0 and the max to 255, all data values in between the defined min and max range are scaled linearly. Data outside the min and max range are set to either 0 or 255, depending on whether they are less than or greater than the provided range.</blockquote><p>So there are two things I can infer from this paragraph:</p><ul><li>Optical band data from a satellite sensor can take on a range of values, which are presumably the intensity of the reflected light from that band. Whatever those ranges are depend on the type of instrument that measures it, and sadly there’s not an easily accessible online resource to tell us the min and max values of each band from each remote sensing instrument out there. Mostly we’re going to have to do some guess work and playing around with the min and max values. Fortunately for Landsat 8 images, a lot of online examples show values between 0 and 1, so I concluded that bands B4, B3, and B2 from Landsat 8 are values between 0 and 1.</li><li>If we set min=0 and max=1 for a particular band (say, B4 which is mapped to the Red palette), then all the B4 values between 0 and 1 will be interpolated to values between 0 and 255 of the red colour palette.</li></ul><p>To understand this in a simplified world, let’s say we have a hypothetical colour palette with only 5 colours (0 to 4). And then we have a hypothetical band whose values can range from 0 to 9. If we want to visualise all 0 to 9 values, only the first 5 values can be uniquely represented by the hypothetical colour palette. All other band values from 5 to 9 will be pulled down to the maximum value of the palette that represents it, which is 4. This would cause our image to be skewed towards the darker colours. For example, if more values of a band are mapped to the max Red palette colour, the image would be darker.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eAMlERZeByIht4_0M8UuzQ.png" /></figure><p>However, if we reduce the range of band values that we want to visualise, then these range of values would fit the palette colour range. Back to our hypothetical 5-colour palette example, if we set the desired band values to just be min=0 and max=3, then this will only utilise the same relative range from the colour palette.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pCS_Y9aUlUo3ksuuyL4Trg.png" /></figure><p>Phew! That was a long explanation about min and max band parameters! Let’s go back to the code for true colour parameters:</p><pre>true_color_params = {</pre><pre>    &#39;bands&#39;: [&#39;B4&#39;, &#39;B3&#39;, &#39;B2&#39;],</pre><pre>    &#39;min&#39;: 0,</pre><pre>    &#39;max&#39;: 0.4,</pre><pre>}</pre><pre>map_l8.addLayer(image, true_color_params, &#39;true color&#39;)</pre><p>Okay, so we want to represent three bands B4, B3, and B2 with values scaled within the RGB values of 0 to 255. But we provided only one value for each of min and max while we provided a list of bands. Technically, we could have written it this way for clarity and it would mean the same thing:</p><pre>true_color_params = {</pre><pre>    &#39;bands&#39;: [&#39;B4&#39;, &#39;B3&#39;, &#39;B2&#39;],</pre><pre>    &#39;min&#39;: [0, 0, 0],</pre><pre>    &#39;max&#39;: [0.4, 0.4, 0.4],</pre><pre>}</pre><p>Technically each band can have different min and max values, but we don’t want to complicate our visualisation too early, so we can just leave them as they are.</p><p>The output of this is a map with the true colour layer. Note that there’s still some wisps of cloud there, since we only did a simple cloud filter on the image collection. There are other ways to effectively remove clouds from the composite computation, which we won’t cover in this article.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*rNkg46hashtThcOp.png" /><figcaption>Taal Volcano surrounded by Taal Lake in true colour. The colours are what we would see ourselves if we were on the satellite looking at this region on earth.</figcaption></figure><p><strong>Adding the Infrared Layer</strong></p><p>Now let’s add in a layer showing the median composite in the infrared band. The <a href="https://developers.google.com/earth-engine/datasets/catalog/LANDSAT_LC08_C02_T1_TOA#bands">Landsat 8 TOA Reflectance Data Documentation</a> tells us that Infrared Bands are B7, B6, and B5. For now, we can just use B5, which is the Near-Infrared band or NIR. In the bands parameter, we set only one value B5, and then set the range of NIR values from 0 to 0.4 to be represented in the image. This would mean that surfaces with lower near-infrared reflectance would appear brighter than they would if we represented all values from 0 to 1.</p><pre>near_infrared_params = {</pre><pre>    &#39;bands&#39;: &#39;B5&#39;,</pre><pre>    &#39;min&#39;: 0,</pre><pre>    &#39;max&#39;: 0.4,</pre><pre>}</pre><pre>l8_map.addLayer(image, near_infrared_params, &#39;greyscale infrared&#39;)</pre><p>The output is a new layer on our map showing near-infrared represented in greyscale:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*dw0J6BaDeC0yF5yi.png" /><figcaption>Taal Volcano surrounded by Taal Lake viewed in near infrared represented by greyscale. Vegetation reflects infrared light while water absorbs it, which is the reason why the surrounding forested land area appears bright grey, while the lake appears very dark. The volcano in the middle of the lake doesn’t have much vegetative cover, but it does reflect some amount of infrared, which gives it a dark grey colour in this image.</figcaption></figure><p><strong>Adding the False Colour Layer</strong></p><p>The False Colour composite is where you can unleash your artistic side. Since we’re representing invisible light (or a combination of invisible and visible) using a ‘visible colour’, we can pretty much use any colour we want to represent certain reflective surfaces on the map. However, the industry has its standards when we’re presenting these maps for official use, as explained by <a href="http://gsp.humboldt.edu/olm/Courses/GSP_216/lessons/composites.html">this article</a>, so do be conscious of the colours and bands that you use for non-experimental use cases. In our example of false colour composite, we’ll represent the B5 band (NIR) with the red palette, B4 with the green palette, and B3 with the blue palette. At this point, it gets counterintuitive since we’re representing B4 (red) with green colours and B3 (green) with blue colours.</p><p>I’ve set the max value to 0.5, but as I’ve mentioned, it takes a bit of playing around with the min and max to get the right brightness and contrast that’s pleasing to the eyes.</p><pre>false_color_params = {</pre><pre>    &#39;bands&#39;: [&#39;B5&#39;, &#39;B4&#39;, &#39;B3&#39;],</pre><pre>    &#39;min&#39;: 0,</pre><pre>    &#39;max&#39;: 0.5</pre><pre>}</pre><pre>l8_map.addLayer(image, false_color_params, &#39;false color infrared&#39;)</pre><p>The result of the code above is a layer showing the lake’s surrounding forested areas in shades of bright red, since these areas are reflecting infrared much more than the lake and the volcano. The volcano itself reflects a tiny amount of infrared at its edges, but its colour is mostly a combination blue and green colours representing reflected visible red and green lights, respectively.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*piKE46ZYGnUJyi9e.png" /><figcaption>Taal Volcano surrounded by Taal Lake viewed in near infrared represented by RGB colours. The reflected infrared light from the forested areas are shown in red.</figcaption></figure><h3>Conclusion</h3><p>In this article, we’ve differentiated true colour composites and false colour composites by understanding the reflectance of certain bands of light on various surfaces on earth. We can produce composites of the same region of interest using different bands of light to study the surface features on that region. This is especially important when we want to detect geophysical anomalies or huge changes to the region, like loss of forested areas over time, and we want to see them beyond the limitations of our human eyes.</p><h3>References and Further Reading:</h3><ul><li><a href="http://gsp.humboldt.edu/olm/Courses/GSP_216/lessons/composites.html">Natural and False Color Composites</a> by <a href="http://gsp.humboldt.edu/">http://gsp.humboldt.edu</a>.</li><li><a href="https://www.google.com/earth/outreach/learn/introduction-to-google-earth-engine/#earth-engine-explorer-0#data-range-4-12">Introduction to Google Earth Engine</a> by Google Earth Outreach:</li><li>The <a href="https://developers.google.com/earth-engine/datasets/catalog/landsat">Landsat data catalog</a> on Google Earth Engine</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=546455becda1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Visualising Remotely Sensed Data from Google Earth Engine in Python]]></title>
            <link>https://medium.com/@shiela.mms/visualising-remotely-sensed-data-from-google-earth-engine-in-python-c12fced85b72?source=rss-865166471550------2</link>
            <guid isPermaLink="false">https://medium.com/p/c12fced85b72</guid>
            <category><![CDATA[remote-sensing]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[google-earth-engine]]></category>
            <dc:creator><![CDATA[DM Heli]]></dc:creator>
            <pubDate>Sat, 12 Mar 2022 12:58:13 GMT</pubDate>
            <atom:updated>2022-03-18T10:32:41.186Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LiwDuBu8Pys-Fnsg8ENJqQ.png" /><figcaption>More than an interactive web application, Google Earth publicly provides a whole suite of data and tools to analyse images from satellites that are orbiting the earth.</figcaption></figure><p>If you’ve ever tinkered with Google Earth, you’d have probably been as amazed as I was looking at the earth from the view of satellites that have been encircling the planet for decades. In fact, the data from these satellites are neatly catalogued for us in Google Earth Engine to create our own visualisations and analyses of the particular properties and activities in the earth that we are concerned about, like rainforest cover, wildfire spread, temperatures, and ice cover. This becomes a very powerful tool in observing and analysing the manifestations of climate change or environmental degradation.</p><p>In this article, we’ll go through a code-first approach in Python to learn the basics of using satellite imagery from Google Earth Engine datasets and presenting them on static and interactive maps. The data catalog is huge, and you’ll find loads of references detailing each component of each dataset. The particular example I’m going to do is visualising the mean land surface temperature of a particular region of interest in 2021 using data from <a href="https://terra.nasa.gov/about/terra-instruments/modis">MODIS</a>, one of the scientific instruments aboard NASA’s Terra satellite.</p><p>There are two main ways we can render satellite imagery in Python:</p><ul><li>By loading a static image from Google Earth Engine datasets</li><li>By using a Python library called <em>folium</em> to create an interactive map</li></ul><p>Google Earth Engine provides an API to load and process satellite data in distributed servers so that we don’t need to worry about the computational limits of our personal computers to process these big imagery data. On top of the API, Google Earth Engine also supports Javascript and Python SDKs, so that developers can easily integrate Google Earth images into their applications. While Javascript gets a lot more online support, the Python SDK is much more extensible because of its data manipulation capabilities.</p><h4>Pre-requisite knowledge and tools</h4><ol><li>Intermediate Python knowledge and programming skills</li><li>Python 3 environment setup, particularly Jupyter notebook installation</li><li>Basic understanding of Google Earth</li></ol><p>It’s best to use Jupyter notebooks (or Google Colab) with Google Earth Engine Python SDK, as the images can be readily displayed on your browser.</p><h4>Google Earth Engine Python SDK setup</h4><p>With the assumption that you can read and write intermediate-level Python code, I’ll go ahead and just <a href="https://developers.google.com/earth-engine/guides/python_install">link to the Google Earth Engine Python installation page</a> to get you started on your environment setup. Basically, you need to:</p><ul><li>Install the Python client library for Google Earth Engine</li><li>Create Google Earth Engine credentials to authenticate to the API (free!)</li></ul><h3>Part 1: Rendering a static map</h3><p>In this exercise, we’ll render a static map of the land surface temperature of the Philippines in 2021 using the <a href="https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MOD11A1#description">MODIS Terra Land Surface Temperature dataset</a> in Google Earth Engine.</p><h4>Complete Code</h4><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/abb717e1bc96d872ca139ca6da1cd23b/href">https://medium.com/media/abb717e1bc96d872ca139ca6da1cd23b/href</a></iframe><h4>Walkthrough</h4><p>First, let’s identify the point on earth that we want to visualise. I’ve chosen coordinates that centre to the Philippines. We use `ee.Geometry.Point` to specify a point in the earth using a [longitude, latitude] pair.</p><p>poi = ee.Geometry.Point([122.1247, 13.2735])</p><blockquote><strong>More info: Footnote 1.1.</strong> Where to get location coordinates</blockquote><p>A point alone would not be able to show us an entire country. So, we’ll need to “zoom out” of that point using a buffer, which expands the geometry by the given distance in meters (by default). In our example, let’s <em>zoom out</em> to a radius of 9.2 x 10⁵ meters (or 920 km) from the point of interest. You can adjust this buffer by as much as you like.</p><p>roi = poi.buffer(distance=9.2e5)</p><blockquote><strong>More info: Footnote 1.2.</strong> Geometry.Point buffer</blockquote><p>Now that we’ve established the region that we want to see, let’s grab some satellite data from the Google Earth Engine datasets. In this example, I’ll use a dataset from a satellite called MODIS, which provides an Image Collection of Global Land Surface Temperature with a spatial resolution of 1 kilometre.</p><p>dataset = ee.ImageCollection(&quot;MODIS/006/MOD11A1&quot;)</p><p>dataset = dataset.select(&#39;LST_Day_1km&#39;)</p><blockquote><strong><em>More info: Footnote 1.3. </em></strong><em>Information about the MODIS dataset</em></blockquote><blockquote><strong><em>More info: Footnote 1.4.</em></strong><em> Google Earth Engine Images, Features, ImageCollections, and FeatureCollections</em></blockquote><p>We can filter the ImageCollection by a range of dates. Let’s say we want to get the land surface temperature of the Philippines in the year 2021. We use the ee.Filter object to define a date filter, and then pass this to the filter() function of dataset.</p><p>date_filter = ee.Filter.date(&#39;2021-01-01&#39;, &#39;2022-01-01&#39;)</p><p>dataset = dataset.filter(date_filter)</p><p>The first date parameter is the initial date of observation (inclusive), while the second date parameter is the day after the last day of observation. This filter gives us the whole range of dates in the year 2021.</p><p>We’re still left with a bunch of images from the dataset. By default, these images are sorted by date, and they are stacked on top of each other, the latest image being at the top of the stack. This is called a <em>mosaic</em>. We want an image that could show us the average (or sometimes, the median) of all these images. This combination of images is called a <em>composite, </em>and this is one of the most useful ways we can visualise a collection of raster data over date ranges.</p><p>In this example, we’ll create the composite image of the Philippines’ 2021 Land Surface Temperature by calculating the mean of the overlapping pixels of its images.</p><p>image = dataset.mean()</p><p>image = image.multiply(0.02).add(-273.15)</p><p>The second line in the above code snippet looks like an arbitrary transformation, but fear not. There is an explanation to it by looking back at the <a href="https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MOD11A1#bands">dataset description</a>, a portion of which is below. Under the Scale column, you’ll find the value 0.02. This means that in order to render the LST_Day_1km band in a 256x256 pixel image, we need to scale it by 0.02 (thus, image.multiply(0.02)). Next, under the Units column, notice that the temperature data is provided in Kelvin, which is not normally used in everyday conversation. We can convert this to a more familiar measurement unit like Celsius or Fahrenheit. I’ve chosen to convert it to Celsius through add(-273.15).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Szy1kQ6cy2KEmZJC.png" /><figcaption>Bands of MOD11A1.006 Terra Land Surface Temperature and Emissivity Daily Global 1km dataset</figcaption></figure><ul><li><strong><em>More info: Footnote 1.5.</em></strong><em> How images are scaled in Google Earth Engine</em></li></ul><p>The last part of the code is setting up the visualisation parameters. These specify what ranges of the temperature data we want to visualise, what colours to use, and what the size of the final image will be.</p><pre>visualisation_params = {</pre><pre>  &#39;min&#39;: 8,</pre><pre>  &#39;max&#39;: 40,</pre><pre>  &#39;dimensions&#39;: 620,</pre><pre>  &#39;region&#39;: roi,</pre><pre>  &#39;palette&#39;: [&#39;blue&#39;, &#39;yellow&#39;, &#39;red&#39;]</pre><pre>}</pre><pre>url = image.getThumbUrl(visualisation_options)</pre><pre>Image(url=url)</pre><p>Let’s put a bit more detail into the visualisation_params variable:</p><ul><li><em>min</em>: the minimum temperature value that we want to visualise in the region</li><li><em>max: </em>the maximum temperature value that we want to visualise in the region</li><li><em>dimensions</em>: the size (in pixels) of the output image</li><li>region: the region that we want to apply the visualisation to</li><li>palette: the colours that we want to use to indicate the different temperature levels</li></ul><p>So, given these definitions, setting <em>min: 8,</em> <em>max: 40</em> and <em>palette: [‘blue’, ‘yellow’, ‘red’] </em>roughly means that areas with temperatures from 8 to around 18 degrees on average will appear bluish, then as temperatures increase, they appear more yellow. When the temperatures are up to around 28 degrees, they start to appear orange (because of the mix of yellow and red), and then as temperatures increase even more until the max temperature of 40 degrees, the areas appear red. See the example of the northern part of the Philippines, wherein the mountainous areas have blue streaks as the mean temperatures there are cooler. The area encompassing Metropolitan Manila is completely red, indicating the hottest temperatures on average.</p><h3>Output</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/620/0*mhz9mvKHbF4muf78.png" /><figcaption>Mean land surface temperature of the Philippines in 2021 showing temperature ranges from 8 degrees to 40 degrees Celsius. The bluish spots indicate the cooler temperatures in the mountainous regions; Yellow areas correspond to relatively mild temperate regions; Meanwhile, orange to red areas indicate the hottest regions throughout the year. The reddest area is, as expected, the densest city in the country — Metro Manila.</figcaption></figure><h3>Part 2: Rendering an interactive map</h3><p>In the previous exercise, we were able to render a static image of the Philippines using the MODIS Land Surface Temperature dataset. In this next part, we’ll render the same image but on an interactive map using Google Earth. To create a Google Earth interactive map, we can use a library called <em>folium </em>which provides the abstractions to manipulate a Google Earth satellite image and add the MODIS satellite dataset as another layer on top.</p><h3>Complete Code</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/421a46c7e9db69c1f12ab8224d83e9a7/href">https://medium.com/media/421a46c7e9db69c1f12ab8224d83e9a7/href</a></iframe><h4>Walkthrough</h4><p>The code for the interactive map looks very similar to the one in the previous exercise on rendering a static image. Let’s focus on the main differences.</p><pre>coords = [13.2735, 122.1247]  # [lat, long]</pre><pre>Map = folium.Map(location=coords, zoom_start=6)</pre><pre>Map.setOptions(&#39;SATELLITE&#39;)</pre><p>First, Folium accepts geographic coordinates as latitude and longitude pairs (note: latitude comes first). To load the Google Earth map, we pass the coordinates and an initial zoom value to the folium.Map object. Note that we no longer need to use a <em>buffer</em> to zoom out to the region of interest, since an interactive map does that for us.</p><p>Once we’ve instantiated our folium map, we can set the base map type. Here I’ve chosen to use the SATELLITE map type.</p><blockquote><strong>More info: Footnote 1.6. </strong>Supported map types</blockquote><p>Skipping over to the next difference: the visualisation_params variable.</p><pre>visualisation_params = {</pre><pre>  &#39;min&#39;: 8,</pre><pre>  &#39;max&#39;: 40,</pre><pre>  &#39;palette&#39;: [&#39;blue&#39;, &#39;yellow&#39;, &#39;red&#39;]<br>}</pre><p>Unlike the previous static map’s `visualisation_params`, there is no need to specify the dimensions and region properties, since we’re no longer rendering a static image of certain dimensions, and the region of interest would have to be added as a <em>layer</em> on top of the map. We add the layer by using the addLayer() function, which takes as arguments the image data, the visualisation parameters, and the name that we want to give to the layer.</p><p>Map.addLayer(image, visualisation_params, &#39;Land Surface Temperature&#39;)</p><p>Interactive maps on Google Earth typically have control buttons in addition to the zoom buttons (which appear by default). The following code adds a layer control button (to show/hide map layers), and a full screen control button to the map.</p><p>Map.setControlVisibility(layerControl=True, fullscreenControl=True)</p><h3>Output</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*lL9edgMYqzxD7ivm.png" /><figcaption>The Modis Land Surface Temperature image of the Philippines as a layer on top of the Google Earth satellite interactive map. When the code is run on Jupyter notebook, you can drag around the output area to see how the temperature data is visualised in other countries. Notice the button on the top right — this allows you to show or hide layers on the map.</figcaption></figure><h3>Summary</h3><p>In this post, we created the same map using two ways: by rendering a static image, and then by creating an interactive map. We used the Google Earth Engine API to get remotely sensed image data (particularly from the MODIS dataset) on our region of interest so that we can analyse a feature of that region aggregated over a period of time (particularly average land surface temperature in 2021). Although other datasets on the Google Earth Engine catalog have different spectral bands and different use cases, we can perform roughly same pattern of data manipulation for other types of analyses.</p><h3>Footnotes and References</h3><p><strong>1.1. Where to get location coordinates</strong></p><ul><li>You can use Google Maps to quickly obtain the coordinates of a certain location (at least that’s what I usually do). Wherever you are on Google Maps, the geographic coordinates of the place at the centre of the screen appears on the address bar. You can copy these coordinates, but remember which one is latitude and which one is longitude. In Google Maps, the latitude value comes first.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*0z1aT2YxEUutBlPq.png" /></figure><p><strong>1.2. Geometry.Point buffer</strong></p><ul><li>The <a href="https://developers.google.com/earth-engine/apidocs/ee-geometry-point-buffer">Earth Engine API docs</a> provides more details about buffer.</li></ul><p><strong>1.3. Information about the MODIS dataset</strong></p><ul><li>MODIS (Moderate Resolution Imaging Spectroradiometer) is an instrument aboard NASA’s Terra and Aqua Satellites, which are low-earth orbiting satellites that measure properties of land and oceans. MODIS can measure atmospheric conditions as well as photosynthetic activity, making it useful for measurements of the impact of environmental changes to the earth’s climate.</li><li>One of the datasets collected from MODIS is the Daily Global Land Surface Temperature and Emissivity dataset. It has a 1200km spatial resolution, meaning that each grid in an image covers 1200km of the earth’s surface.</li><li>Further reading about MODIS: Thanh Noi Phan &amp; Martin Kappas (2018), “<a href="https://www.spiedigitallibrary.org/journals/journal-of-applied-remote-sensing/volume-12/issue-04/041501/Application-of-MODIS-land-surface-temperature-data--a-systematic/10.1117/1.JRS.12.041501.full?SSO=1">Application of MODIS Land Surface Temperature Data: a systematic literature review and analysis</a>”</li><li>Further reading from <a href="https://terra.nasa.gov/about/terra-instruments/modis">NASA’s article about MODIS</a></li><li>Google Earth data reference of <a href="https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MOD11A1#description">MODIS Land Surface Temperature and Emissivity dataset</a></li></ul><p><strong>1.4. Data from Google Earth Engine can be <em>images</em>, <em>collections</em>, or <em>features</em>.</strong></p><ul><li>An <em>image</em> is any raster data (gridded/pixelated data where each pixel refers to a geographic location)</li><li>A <em>feature</em> is data about the attributes of a certain area (e.g. vegetation)</li><li>A <em>collection</em> is set of images or features</li></ul><p><strong>1.5. How images are scaled in Google Earth Engine</strong></p><ul><li>Further reading: <a href="https://developers.google.com/earth-engine/guides/scale">Google Earth Engine reference about scale</a></li></ul><p><strong>1.6. Supported map types</strong></p><ul><li>Further reading: <a href="https://developers.google.com/maps/documentation/javascript/maptypes">Google Maps reference on supported map types</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c12fced85b72" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>