title | authors | date | reviewers | layout | ||
---|---|---|---|---|---|---|
Web Mapping with Python and Leaflet |
|
2015-10-19 |
|
default |
In this lesson, you will learn how to create a web map based on that data. By the end of this lesson, you will be able to:
- Manipulate tabular data progammatically to extract geonames and create location-based data
- Convert tabular data into a meaningful geographic data structure
- Understand and apply the basic concepts of web mapping to design your own web map
This lesson uses:
- python (pip, geopy, pandas)
- leaflet
- jquery
Optional in this lesson:
- GDAL
- Mapbox
Optional: If you wish to follow along with pre-made scripts you can download them from https://github.com/kimpham54/proghist-mappingAPI
To set up your working environment:
- Create a directory that you will work from
- Import your folder in a text editor such as TextWrangler for OS X, Notepad++ for Windows, or Sublime Text.
We're going to start with a plain comma-separated values (CSV) data file and create a web map from it.
The original data file can be downloaded here: https://github.com/Robinlovelace/Creating-maps-in-R/blob/master/data/census-historic-population-borough.csv. The original source of this data is from the Greater London Authority London Datastore.
Now that we have data, the next step is sometimes the hardest part: we need to figure out what to do with it. In this case, we know what our end goal is: to make a web map with this data. You can work backwards from here to figure out what steps you need to take to achieve your goal.
Web maps typically represent locations and features from geographic data formats such as geoJSON and KML. Every location in a geographic data file can be considered to have geometry (such as points, lines, polygons) as well as additional properties. Web maps typically understand locations as a series of coordinates. For example, 43.6426,-79.3871 would represent the exact coordinates of the CN Tower in Toronto.
In our data file, we have a list of placenames in our CSV data (the Area Name column), but no coordinates. What we want to do then is to somehow generate coordinates from these locations. This process is called geocoding.
So here is our first problem to solve: how can we geocode placenames? How could we take an entry such as "CN Tower" and add the coordinates 43.6426,-79.3871 to it automatically?
To clarify, we need to figure out how to gather coordinates for a location for each row of a CSV file in order to display these locations on a web map.
There's a simple way to do this: you can look up a coordinate online in Google Maps and put each coordinate in your spreadsheet manually. But, if you had 5000 points the task becomes a little bit more daunting. If you're faced with a repetitive task, it might be worthwhile to approach it programmatically.
If you're familiar with Programming Historian, you might have already noticed that there there are many lessons available on how to use Python. Python is a great beginner programming language because it is easy to read and happens to be used a lot in GIS applications to optimize workflows. One of the biggest advantages to Python is the impressive amount of libraries which act like pluggable tools to use for many different tasks. Knowing that this is a good programmatic approach, we're now going to build a Python script that will automate geocode every address for us.
Geopy is a Python library that gives you access to the various geocoding APIs. Geopy makes it easy for Python developers to locate the coordinates of addresses, cities, countries, and landmarks across the globe using third-party geocoders and other data sources. Geopy includes geocoders built by OpenStreetMap Nominatim, ESRI ArcGIS, Google Geocoding API (V3), Baidu Maps, Bing Maps API, Yahoo! PlaceFinder, Yandex, IGN France, GeoNames, NaviData, OpenMapQuest, What3Words, OpenCage, SmartyStreets, geocoder.us, and GeocodeFarm geocoder services.
Pandas is another python library that we will use. It's very popular library amongst scientists and mathmaticians to manipulate and analyse data.
Finally, Pip is a very useful package manager to help you install things like Geopy and Pandas! If you've already installed Python and pip, run type 'pip list' to see if you already have the geopy and pandas packages installed. If you do not have pip installed, the instructions here are very straightforward.
To install Geopy and Pandas, open your command line (using this lesson as a guideline if necessary) and install the Geopy and Pandas libraries:
On OS X or Linux, the following commands will install the necessary packages:
pip install numpy
pip install python-dateutil
pip install pytz
pip install geopy
pip install pandas
For Windows, you may need to install Microsoft Visual C++ Compiler for Python (for 2.7, you can download it from Microsoft). Set the environmental variables to recognize python and pip from the command line:
setx PATH "%PATH%;C:\Python27"
setx PATH "%PATH%;C:\Python27\Scripts"
If you keep getting an error when you're tring to install these libraries, you may need to use 'sudo pip install' instead of just 'pip install'. You may also need to upgrade your libraries if you've installed them earlier and you find that you're encountering an error when using Python (i.e. an ImportError). In order to do so, the following command works:
pip install python --upgrade
Repeat for the other dependencies listed above.
Next, Open your text editor and save your blank document as a python script (name it geocoder.py). For the first part of your Python script, you will want to import your libraries and your data:
import geopy
import pandas
from geopy.geocoders import Nominatim, GoogleV3
# versions used: geopy 1.10.0, pandas 0.16.2, python 2.7.8
In the code above, we are importing the different Python libraries that we will need to use later on in our script. We import geopy, specifically the geopy.geocoders that we will call on later which is Nominatim and GoogleV3, and we import pandas.
Then you want to create a function main() that reads your input CSV.
def main():
io = pandas.read_csv('census-historic-population-borough.csv', index_col=None, header=0, sep=",")
We are first using pandas' pre-existing read_csv() function to open the CSV file. We pass the filepath to our data file in the first parameter, 'census-historic-population-borough.csv'. If it was in a folder called 'data', you would put 'data/census-historic-population-borough.csv'. The second parameter, 'index_col=None', will number the rows to generate the index without using any column. If we use 'index_col=0', it indexes the first column in your data as the row name. The third parameter, 'header=0', indicates that there is a header row, which is the first line of the spreadsheet (Note: programmers like to use "0" instead of "1" to indicate the first value in an index). The fourth parameter 'sep=","' is where yu indicate delimiter symbol that is used to split data into fields. Since are using a comma separated values data format, we need to indicate that we are using a comma to split our data.
There are many other parameters you can use. A full list is available in the pandas documentation on the read_csv() function.
Next, select the geolocator you want to use. Here we're creating two geolocators: Open Street Map's Nominatim and Google's Geocoding API. Here's a quick comparison:
Geolocator | Nominatim() | GoogleV3() |
---|---|---|
affiliation | OpenStreetMap | |
application use | single-threaded applications | can upgrade for better performance |
capabilities | user-input | static (Google's non-static geocoding service not in geopy) |
request limit | 1 request/s or timeout | 5 requests/s, 2500/day |
performance test on census data | 33.5s | 11.6s |
You can also choose a different geolocator from the list found in the geopy documentation:
geolocator = Nominatim()
# geolocator = GoogleV3()
# uncomment the geolocator you want to use
Finally, using pandas you want to create a column in your spreadsheet called 'latitude'. The script will read the existing 'Area_Name' data column, run the geolocator, and generate a latitude coordinate in that column. The same transformation will occur in the 'longitude' column. Once this is finished it will ouput a new CSV file with those two columns:
io['latitude'] = io['Area_Name'].apply(geolocator.geocode).apply(lambda x: (x.latitude))
io['longitude'] = io['Area_Name'].apply(geolocator.geocode).apply(lambda x: (x.longitude))
io.to_csv('geocoding-output.csv')
To finish off your code, it's good practice to make your python modular, that way you can plug it in and out of other applications (should you want to use this script as part of another program):
if __name__ == '__main__':
main()
Do you have a script ready? Good. Run the script from your command line by typing:
python geocoder.py
It takes a few seconds and may take longer depending on the geolocator you use. Once the script finishes running, you should have coordinates for every Area Name.
Tip 1: If you want to pass the filenames from the command line rather than changing the input file name in the python script everytime, you can import the python 'sys' library to pass through arguments.
Tip 2: If you run it too many times because you get a timeout error, like this if you use the GoogleV3 geocoder
'The given key has gone over the requests limit in the 24'
geopy.exc.GeocoderQuotaExceeded: The given key has gone over the requests limit in the 24 hour period or has submitted too many requests in too short a period of time.
Now that you have a spreadsheet full of coordinate data, we can convert the CSV spreadsheet into a format that web maps like, like GeoJSON. GeoJSON is a web mapping standard of JSON data. There are a couple of ways to make GeoJSON:
Option 1 - The easiest, recommended way is to use a UI tool developed by Mapbox: http://geojson.io. All you have to do is click and drag your csv file into the data window (the right side of the screen, next to the map), and it will automatically format your data into GeoJSON for you. You can select the 'GeoJSON' option under 'Save.' Save your GeoJSON file as 'census.geojson'.
{% include figure.html src="../images/webmap-01-geojsonio.gif" caption="Adding data to geojson.io" %}
Image Credit: with permission from Mauricio Giraldo Arteaga, NYPL Labs
Option 2 - To do it programmatically, you can use ogr2ogr. You'll need to install GDAL, a commonly used GIS library that is frequently used to automate processes in python. If you want to batch convert 500 CSV files into GeoJSON, this will be the way to go. [8]
Using ogr2ogr
Once you have GDAL installed, set the path:
export PATH=/Library/Frameworks/GDAL.framework/Programs:$PATH
for Windows:
setx PATH “%PATH%;C:\OSGeo4W\bin”
setx GDAL_DATA “C:\OSGeo4W\share\gdal”
Create a VRT file
VRT is an XML-based template that is used to convert non geographic data into a geographic data format without creating intermediate files. Make sure that OGRVRTLayer, SrcDataSource have the same name as your filename (census_geocoded.vrt). Indicate all of the properties based on the column name such as the population values for every census to include your geojson. This is what your VRT file will look like:
<OGRVRTDataSource>
<OGRVRTLayer name="census_geocoded">
<SrcDataSource>census_geocoded.csv</SrcDataSource>
<GeometryType>wkbPoint</GeometryType>
<LayerSRS>WGS84</LayerSRS>
<GeometryField encoding="PointFromColumns" x="longitude" y="latitude"/>
<Field name="ID" src="ID" type="String"/>
<Field name="Area_Name" src="Area_Name" type="String"/>
<Field name="Area_Code" src="Area_Code" type="String"/>
<Field name="Pop_1801" src="Pop_1801" type="Integer"/>
<Field name="Pop_1811" src="Pop_1811" type="Integer"/>
<Field name="Pop_1821" src="Pop_1821" type="Integer"/>
<!-- etc...not all of the columns are included here -->
<Field name="Pop_1971" src="Pop_1971" type="Integer"/>
<Field name="Pop_1981" src="Pop_1981" type="Integer"/>
<Field name="Pop_1991" src="Pop_1991" type="Integer"/>
<Field name="Pop_2001" src="Pop_2001" type="Integer"/>
</OGRVRTLayer>
</OGRVRTDataSource>
Run ogr2ogr to output your geojson
ogr2ogr -f GeoJSON census.geojson census_geocoded.vrt
Your GeoJSON output should look something like this:
{
"type": "FeatureCollection",
"crs": { "type": "name", "properties": { "name": "urn:ogc:def:crs:OGC:1.3:CRS84" } },
"features": [
{ "type": "Feature", "properties": { "ID": "1000", "Area_Name": "City of London", "Area_Code": "00AA", "Pop_1801": 129000, "Pop_1811": 121000, "Pop_1821": 125000, "Pop_1831": 123000, "Pop_1841": 124000, "Pop_1851": 128000, "Pop_1861": 112000, "Pop_1871": 75000, "Pop_1881": 51000, "Pop_1891": 38000, "Pop_1901": 27000, "Pop_1911": 20000, "Pop_1921": 14000, "Pop_1931": 11000, "Pop_1939": 9000, "Pop_1951": 5000, "Pop_1961": 4767, "Pop_1971": 4000, "Pop_1981": 5864, "Pop_1991": 4230, "Pop_2001": 7181 }, "geometry": { "type": "Point", "coordinates": [ -0.1277583, 51.5073509 ] } },
{ "type": "Feature", "properties": { "ID": "1001", "Area_Name": "Barking and Dagenham", "Area_Code": "00AB", "Pop_1801": 3000, "Pop_1811": 4000, "Pop_1821": 5000, "Pop_1831": 6000, "Pop_1841": 7000, "Pop_1851": 8000, "Pop_1861": 8000, "Pop_1871": 10000, "Pop_1881": 13000, "Pop_1891": 19000, "Pop_1901": 27000, "Pop_1911": 39000, "Pop_1921": 44000, "Pop_1931": 138000, "Pop_1939": 184000, "Pop_1951": 189000, "Pop_1961": 177092, "Pop_1971": 161000, "Pop_1981": 149786, "Pop_1991": 140728, "Pop_2001": 163944 }, "geometry": { "type": "Point", "coordinates": [ 0.1293497, 51.5464828 ] } },
Test this data out in http://geojson.io. You should see points generated in the preview window. That's your data!
If you've tested your GeoJSON data, you might notice that not every point is geolocated correctly. We know that every area name is a borough of London, but points appear all over United Kingdom, and some aren't located even in the country.
To make the results more accurate, you should save another copy of the census-historic-population-borough.csv file and include an additional column called 'Country' and put 'United Kingdom' in every row of your data. For even greater accuracy add 'City' and put 'London' in every row of your data to provide additional context for your data.
{% include figure.html src="../images/webmap-02-countrycolumn.png" caption="Add a new Country column to your spreadsheet" %}
Now change your python script to combine the Area Name and Country or City column to geocode your data:
io['helper'] = io['Area_Name'].map(str) + " " + io['Country']
io['latitude'] = io['helper'].apply(geolocator.geocode).apply(lambda x: (x.latitude))
io['longitude'] = io['helper'].apply(geolocator.geocode).apply(lambda x: (x.longitude))
Turn your data into GeoJSON and test it out in http://geojson.io. Do the results look better now? Good!
Setup a test web server to test out our maps. A web server is used to serve content from your directory to your browser.
If you're in your working directory, from the command line, run
python -m SimpleHTTPServer
SimpleHTTPServer is a Python module. If you want to change the server to port 8080 (or any other port), use
python -m SimpleHTTPServer 8080
In your browser go to http://localhost:8000 and you should see the files you've been working with so far.
Now in your text editor open a new document and save it as an html file (mymap.html). If you want to do a quick test, copy and paste the text below, refresh your http://localhost:8000 and open the html file in your browser.
<!DOCTYPE html>
<head>
<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.css" />
<script src="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.js"></script>
<script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
<style>
#my-map {
width:960px;
height:500px;
}
</style>
</head>
<body>
<div id="my-map"></div>
<script>
window.onload = function () {
var basemap = L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
attribution: '© <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'
});
$.getJSON("census.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.Area_Name);
}
});
var map = L.map('my-map')
.fitBounds(geojson.getBounds());
// .setView([0.0,-10.0], 2);
basemap.addTo(map);
geojson.addTo(map);
});
};
</script>
</body>
</html>
Do you see a map now? Good! If not, you can troubleshoot by inspecting the browser, or by going back and retracing your steps.
You made a web map! Web maps use map tiles, which are pixel based images (rasters) of maps that contain geographical data. This means that each pixel of a map tile has been georeferenced, or assigned a coordinate based on the location that they represent. When you zoom in and out of a web map, you are getting a whole new set of tiles to display at each zoom level. GeoJSON (which you are now familiar with) is a widely used data standard for web mapping. In our example, we are using an open-source Javascript library called Leaflet to help us build our web map. With frameworks like Leaflet or Google Maps Javascript API, you're not building a map completely from scratch, rather, you're using pre-written functions and controls that helps you customize your own map in code.
Lets go through what each part of the code is doing. But first, it's best practice to maintain your html, css, js in different files so that the web map's content, presentation and behaviour layers are kept separate (though it's not always possible). This adds a bit more structure to your code, making it easier for you and others to understand. It will be easier to focus on certain parts of the code when you're going back and making changes. So here is our code split into three files:
mymap.html
<!DOCTYPE html>
<head>
<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.css" />
<script src="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.js"></script>
<script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
<link rel="stylesheet" href="style.css" />
</head>
<body>
<div id="my-map"></div>
</body>
<script src='leafletmap.js'></script>
</html>
style.css
#my-map {
width:960px;
height:500px;
}
leafletmap.js
window.onload = function () {
var basemap = L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
attribution: '© <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'
});
$.getJSON("census.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.Area_Name);
}
});
var map = L.map('my-map')
.fitBounds(geojson.getBounds());
basemap.addTo(map);
geojson.addTo(map);
});
};
Seems a bit easier to undestand now, doesn't it? Now lets look at what the html file is doing.
<!DOCTYPE html>
<head>
<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.css" />
<script src="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.js"></script>
<script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
<link rel="stylesheet" href="style.css" />
</head>
The above code is the first section, or header of your html document. We are linking to the external javascript library and css stylesheets provided by leaflet. We're also linking to our own stylesheet, style.css.
<body>
<div id="my-map"></div>
</body>
<script src='leafletmap.js'></script>
</html>
Next, we're declaring the body and where you want the map to go on your page. We're also linking to our own javascript file, leafletmap.js.
style.css
#my-map {
width:960px;
height:500px;
}
There's a bit of CSS styling here to specify the size of your map. Some optional styling will happen in your javascript file if you're using the Leaflet library.
window.onload = function () {
var basemap = L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
attribution: '© <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'
});
The javascript file is what provides the behaviour, or functionality of our web map. It's what makes our web map come alive! In the code above, we're telling the javascript to load when the browser loads. We're creating our first map layer, which is your basemap. The basemap is the tiles provided by OpenStreetMap that provides places and streetnames found on maps.
$.getJSON("census.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.Area_Name);
}
});
Next, we're loading our data as another map layer, census.geojson. This data will have additional properties: each poit of data is represented by an icon. It will look and behave like a popup so that when you click on the icon it will load information from your data file (in this case, the Area_Name).
var map = L.map('my-map')
.fitBounds(geojson.getBounds());
basemap.addTo(map);
geojson.addTo(map);
});
};
Now we're creating the view for our map. The boundary for our map will be based on the range of our data points in census.geojson. You can also manually set your your viewport by using the setView property. For example, if you're using .setView([0.0,-10.0], 2), the viewport coordinates '[0.0,-10.0], 2' means that you're setting the centre of the map to be 0.0, -10.0 and at a zoom level of 2.
{% include figure.html src="…/images/webmap-03-result.jpg" caption=“Final Result: Your Web Map!” %}
Finally, the map layers you created will be added to your map. Put it all together and congratulations, you've got your web map! Now lets play around with it.
Change the map to use a viewport to 51.505 latitude, -0.09 longitude with a zoom level 9.
Add the 1981 and 1991 population property to each marker popup. You can use HTML to style your popup window.
Change the data source to stations.geojson.
Change your data source back to census.geojson. Change your basemap layer to a mapbox tileset. You need to get a Mapbox account, create a map or style and get your Mapbox API access token.
{% include figure.html src="…/images/webmap-04-mapboxAPI.png" caption=“Final Result: Your Web Map!” %}
Add a custom leaf icon, found in the images folder. Or use your own!
mymap.html - No Edits
style.css - No Edits
leafletmap.js
window.onload = function () {
var basemap = L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
attribution: '© <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'
});
$.getJSON("census.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.Area_Name);
}
});
var map = L.map('my-map')
//.fitBounds(geojson.getBounds());
.setView([51.505,-0.09], 9);
//EDIT HERE
basemap.addTo(map);
geojson.addTo(map);
});
};
{% include figure.html src="…/images/webmap-05-exercise01.jpg" caption=“Exercise 01 Map Result” %}
mymap.html - No Edits
style.css - No Edits
leafletmap.js
window.onload = function () {
var basemap = L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
attribution: '© <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'
});
$.getJSON("census.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.Area_Name + '<p><b> 2001 Population: ' + feature.properties.Pop_2001 + '</b></p>' + '<p><b> 1981 Population: ' + feature.properties.Pop_1981 + '</b></p>' + '<p><b> 1801 Population ' + feature.properties.Pop_1801 + '</b></p>');
//EDIT HERE
}
});
var map = L.map('my-map')
//.fitBounds(geojson.getBounds());
.setView([51.505,-0.09], 9);
basemap.addTo(map);
geojson.addTo(map);
});
};
{% include figure.html src="…/images/webmap-06-exercise02.jpg" caption=“Exercise 02 Map Result” %}
mymap.html - No Edits
style.css - No Edits
leafletmap.js
window.onload = function () {
var basemap = L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
attribution: '© <a href="http://osm.org/copyright">OpenStreetMap</a> contributors'
});
$.getJSON("stations.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.name + '<p><b> Line: ' + feature.properties.line + '</b></p>');
//EDIT HERE
}
});
var map = L.map('my-map')
.fitBounds(geojson.getBounds());
// .setView([51.505,-0.09], 9);
// EDIT HERE
basemap.addTo(map);
geojson.addTo(map);
});
};
{% include figure.html src="…/images/webmap-07-exercise03.jpg" caption=“Exercise 03 Map Result” %}
mymap.html
<!DOCTYPE html>
<head>
<link rel="stylesheet" href="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.css" />
<script src="http://cdn.leafletjs.com/leaflet-0.6.4/leaflet.js"></script>
<script src="https://code.jquery.com/jquery-2.1.4.min.js"></script>
<!-- EDIT HERE -->
<script src='https://api.mapbox.com/mapbox.js/v2.2.1/mapbox.js'></script>
<link href='https://api.mapbox.com/mapbox.js/v2.2.1/mapbox.css' rel='stylesheet' />
<link rel="stylesheet" href="style.css" />
</head>
<body>
<div id="my-map"></div>
</body>
<script src='leafletmap.js'></script>
</html>
```
style.css - No Edits
leafletmap.js
```javascript
window.onload = function () {
// EDIT HERE: get an access token, replace 'YOURTOKENHERE' with something like "pk.eyJ1Ijoia2ltcGhhbTU0IiwiYSI6IkdJX0tvM2cifQ.fVsdGC_QJrFYZ3SxZCsvhQ"
L.mapbox.accessToken = 'YOURTOKENHERE';
// EDIT HERE: add the new baselayer style, replace 'YOURLINKHERE' with something like "kimpham54.au2i6bt9"
var basemap = L.tileLayer('https://api.mapbox.com/v4/kimpham54.au2i6bt9/{z}/{x}/{y}.png?access_token=' + L.mapbox.accessToken, {
attribution: '<a href="https://www.mapbox.com/tos/">Mapbox</a>'
});
$.getJSON("stations.geojson", function(data) {
var geojson = L.geoJson(data, {
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.name + '<p><b> Line: ' + feature.properties.line + '</b></p>');
}
});
var map = L.map('my-map')
.fitBounds(geojson.getBounds());
//.setView([51.505,-0.09], 9);
basemap.addTo(map);
geojson.addTo(map);
});
};
```
![Image: Exercise 04 Answer](images/webmap-08-exercise04.jpg "Exercise 04")
{% include figure.html src="…/images/webmap-08-exercise04.jpg" caption=“Exercise 04 Map Result” %}
### Exercise 5 Answer
mymap.html - No Edits
style.css - No Edits
leafletmap.js
```javascript
window.onload = function () {
L.mapbox.accessToken = 'YOURTOKENHERE';
var basemap = L.tileLayer('https://api.mapbox.com/v4/YOURLINKHERE/{z}/{x}/{y}.png?access_token=' + L.mapbox.accessToken, {
attribution: '<a href="https://www.mapbox.com/tos/">Mapbox</a>'
});
$.getJSON("stations.geojson", function(data) {
var geojson = L.geoJson(data, {
//EDIT HERE
pointToLayer: function (feature, latlng) {
var smallIcon = L.icon({
iconSize: [27, 27],
iconAnchor: [13, 27],
popupAnchor: [1, -24],
iconUrl: 'leaf.png'
});
return L.marker(latlng, {icon: smallIcon});
},
onEachFeature: function (feature, layer) {
layer.bindPopup(feature.properties.name + '<p><b> Line: ' + feature.properties.line + '</b></p>');
}
});
var map = L.map('my-map')
.fitBounds(geojson.getBounds());
//.setView([51.505,-0.09], 9);
basemap.addTo(map);
geojson.addTo(map);
});
};
```
![Image: Exercise 05 Answer](images/webmap-09-exercise05.jpg "Exercise 05")
{% include figure.html src="…/images/webmap-09-exercise05.jpg" caption=“Exercise 05 Map Result” %}
### Ideas to explore
- Try other plugins and APIs. There's Stamen, CartoDB, MarkerCluster, and more
- Try time based visualizations
- Use other types of data and geometries. For instance, county boundaries, https://github.com/martinjc/UK-GeoJSON