In [ ]:
import geoviews as gv
import geoviews.feature as gf
from geoviews import opts
from cartopy import crs
gv.extension('bokeh', 'matplotlib')
The GeoViews package provides a library of HoloViews Element types which make it very easy to plot data on various geographic projections and other utilities to plot in geographic coordinate systems.
Elements are very simple wrappers around the data along with some declaration about its dimensions. The only thing that distinguishes a GeoViews element from a HoloViews one is the addition of a crs parameter. The crs parameter defines a cartopy coordinate reference system declaring the coordinate system of the data. This allows GeoViews to automatically project the data to the displayed projection. The crs therefore serves a dual purpose:
Element.crs defines which coordinate system is defined in.projection defined as a plot option defines what coordinate system to display the data in.By default all elements assume a PlateCarree projection (also sometimes known as the equirectangular projection), and therefore expects longitudes and latitudes.
To start with let's declare two Points objects, one using the default PlateCarree crs, the other using the GOOGLE_MERCATOR coordinate system. Just looking at the difference in the coordinates for NYC or Beijing and London we can immediately tell they are very different units but by declaring the crs we can make it possible to automatically translate between them:
In [ ]:
nyc, beijing = (-74.0, 40.7, 'NYC'), (116.4, 39.9, 'Beijing')
london = (14471.53, 6712008., 'London')
cities_lonlat = gv.Points([nyc, beijing], vdims='City')
cities_mercator = gv.Points([london], crs=crs.GOOGLE_MERCATOR, vdims='City')
(gv.tile_sources.Wikipedia * cities_lonlat * cities_mercator).opts(
opts.Points(global_extent=True, width=500, height=475, size=12, color='black'))
As we can see we overlaid the above plot on a WMTS tile source, letting us interactively zoom in and out of the plot. This functionality is only available when using a Web Mercator projection, which is what the bokeh backend uses by default. When using matplotlib on the other hand the plot will automatically use the crs declared on the plotted element (in this case PlateCarree):
In [ ]:
features = gv.Overlay([gf.ocean, gf.land, gf.rivers, gf.lakes, gf.borders, gf.coastline])
gv.output(features, backend='matplotlib', fig='svg', size=300)
When using bokeh a custom plot projection may also be used. The same behavior as matplotlib can be enabled with the infer_projection parameter or an explicit projection can be set:
In [ ]:
(features * cities_lonlat * cities_mercator).options(
opts.Points(projection=crs.Mollweide(), width=800, height=400, size=12, color='black'))
GeoViews supports all projections defined in the cartopy.crs module, which are laid out in detail in the cartopy documentation. Here we list a representative collection of these coordinate systems (skipping PlateCarree and Mercator which we have already seen):
In [ ]:
projections = [crs.RotatedPole, crs.LambertCylindrical, crs.Geostationary,
crs.AzimuthalEquidistant, crs.OSGB, crs.EuroPP, crs.Gnomonic,
crs.Mollweide, crs.OSNI, crs.Miller, crs.InterruptedGoodeHomolosine,
crs.SouthPolarStereo, crs.Orthographic, crs.NorthPolarStereo, crs.Robinson,
crs.LambertConformal, crs.AlbersEqualArea]
If we want to display the plot in a different coordinate system than the data is defined in we can declare the projection as a plot option:
In [ ]:
proj_layout = gv.Layout([gf.coastline.relabel(group=p.__name__).opts(projection=p(), backend='matplotlib')
for p in projections])
gv.output(proj_layout, backend='matplotlib')
When working with bokeh, as we saw above, it defaults to a web Mercator projection. So if we want to override the plot projection we have to explicitly declare it as a plot option:
In [ ]:
opts = dict(width=200, height=225, global_extent=True, axiswise=True)
gv.Layout([gf.coastline.relabel(group=p.__name__).opts(projection=p(), **opts) for p in projections]).cols(4)
Many coordinate reference systems provide various parameters to customize certain aspects of the projection, e.g. the Orthographic CRS allows overriding the central_longitude and central_latitude to change the view of the globe:
In [ ]:
features.opts(projection=crs.Orthographic(central_longitude=-90, central_latitude=30), global_extent=True)
This is particularly important when the data is specified in the longitudes of the data are defined in the range 0 to 360 rather than the default -180 to 180. In this case ensure that the crs of the element declares the actual central_longitude, e.g. 180 degrees rather than the default 0 degrees. Let us draw the same polygon with the default crs (centered on 0) and a custom crs centered on 180 degrees:
In [ ]:
poly_data = [(180, 0), (270, 45), (360, 0)]
features * gv.Polygons(poly_data) * gv.Polygons(poly_data, crs=crs.PlateCarree(central_longitude=180)).opts(global_extent=True)
As we can see the default projection wraps the values above 180, while the custom projection automatically translates the polygon by the central_longitude.
As we have discovered the plotting system will project data to the desired coordinate system automatically. However in certain cases this can be quite expensive especially if it occurs multiple times. Therefore GeoViews makes a high-level operation available to project most types of data from their native crs to the declared projection. Here we will declare a Points element containing the longitude/latitude locations of a number of cities. Using the gv.project operation we can easily project the data to Mercator coordinates:
In [ ]:
cities = gv.Points([(-74.01, 40.71, 'New York'), (0.13, 51.51, 'London'), (116.40, 39.9, 'Beijing')], vdims='City')
projected = gv.operation.project(cities, projection=crs.GOOGLE_MERCATOR)
print(projected.crs)
projected.dframe()