This repository explains how to make a geologic map of the moon using open-source data from the USGS, IAU, and NASA. Software used includes Python 3.7.1, GDAL 2.4.1, bash, Illustrator CC 2019 and Photoshop CC 2019. If you have comments or suggestions for this tutorial, please let me know on my blog! You can also buy the finished map here if you like.
Python dependencies: pandas cartopy matplotlib os numpy shapefile jupyter. Dependencies can be installed with pip install -r requirements.txt.
Software Carpentry has great tutorials for installing Python (scroll down and follow the directions in the Bash Shell and Python sections), getting starting with Jupyter Notebooks, and beginner-friendly Python programming. After you've installed Python using these tutorials, you can use Git Desktop and the instructions in this tutorial to download the code and data in this tutorial. For the code in this repository you will also need to install GDAL. The instructions in this document under the "Conda" section are probably the most relevant if you've installed Python as described above.
You'll need software for editing raster and vector images (this article explains the difference). I use Adobe Photoshop and Illustrator, but you can also use the free open-source programs Gimp and Inkscape. There is no perfect software that fits everyone's needs, so you'll want to understand the pros and cons for the different raster and vector programs before choosing.
- Gathering and processing data
- Map design in Python
- Map design in Illustrator and Photoshop
- References
- License
Although I already made a geologic map of Mars and open-sourced the code, this moon map was much more difficult because the geologic data was split into six different datasets. Each dataset had unique labels (and sometimes different data formats) so I spent a lot of time piecing the data together to create a cohesive map.
One complication with having six datasets was that some geologic categories were described differently in each dataset, like Basin Material, Rugged vs. Material of Rugged Basin Terrain. So I decided to combine closely related terms into a single color, using unit_descriptions_from_files.csv.
This moon data was also challenging because the geologic timescales weren’t very precise. Some areas were described with uncertainty - like plains from the Imbrian or Nectarian era. And some geologic categories combined many time periods, like craters from Imbrian, Nectarian, and pre-Nectarian time periods. I thought it was too complicated to show all these uncertain aggregations in one map, so I decided to omit timescale data entirely. The map features are colored only by geologic category (craters, basins, etc.) and not by age.
The end result is a summarized geologic map rather than a precise replication of the original data. You may want to skip this step in 1_process_moon_data.ipynb to reproduce the data exactly. To adapt this existing code to plot each geologic unit separately, you can edit the Moon_geologic_unit_colors.csv data file to use a different color for each geologic unit.
Digital Elevation Models (DEMs) are data files that provide height information about different locations on a planet or moon. In this project I used a DEM for the moon provided by the United States Geologic Survey. Each pixel in this GeoTIFF file is a signed 16-bit integer that describes the elevation at that specific location on the moon.
Note: Many software programs can't read this kind of file, so it's normal if the DEM looks strange in Preview or other default image applications. I work with these DEM files in GDAL (short for Geospatial Data Abstraction Library).
To map a 3D object in 2D space, the surface must be transformed using a map projection. There are many different projections, and for the maps in the Atlas of Space series I used Eckert IV, Orthographic, and Plate Carrée projections. To compare these different map projections, you can use a Tissot's indicatrix - a set of circles of the same size plotted at different places on the globe. All map projections distort space, but the effects are quite different depending on the projection:
The choice of projection depends on the purpose of the map. For example, the Eckert IV projection preserves area measurements, so I used Eckert IV in the main geologic map to show how much area on the planet was made up of each type of rock. For the smaller inset maps in each corner, I used an Orthographic projection to visualize what each hemisphere of the planet might look like when seen from outer space.
Changing the Map Projection of a DEM File: The original DEM data file uses a Plate Carrée projection, so I used the command line installation of GDAL to transform the map into Eckert IV and Orthographic projections. The code below uses the original intif file to create a new file outtif using the eck4 (Eckert IV) projection:
gdalwarp -t_srs "+proj=eck4" ./path_to_intif.tif ./path_to_outtif.tifNext I downsample the DEM by decreasing the resolution of each pixel to 1500x1500 meters using the average method. It's useful to decrease file size to lower computation times, and it's much faster to downsample at this point than to scale images later on in the process.
gdalwarp -tr 1500 1500 -r average ./path_to_intif.tif ./path_to_outtif.tifNext, I used the downsampled DEM to generate hillshade and slope maps for each hemisphere of the moon.
Hillshade maps show the shadows cast by a hypothetical light source suspended above the map. It’s hypothetical because in the real world, a single light source would cast different shadow angles at different places on a globe. The GDAL hillshade calculation sets the light source angle to be the same everywhere. In this hillshade I set z, or the vertical exaggeration, to 20. This multiplies the real elevation values by 20 to increase visual contrast and help the hillshade show up under all of the other map elements.
gdaldem hillshade -z 20 ./path_to_intif.tif ./path_to_hillshade.tifSlope maps emphasize the steep parts of a map, and adds more information to the topographic hillshade (which emphasizes absolute height rather than steepness).
gdaldem slope ./path_to_intif.tif ./path_to_slope.tif
In addition to the main Eckert IV map, I also mapped the four hemispheres of the moon (North, South, East, and West). The Eckert IV map isn't great for visualizing the North and South poles, so those two insets were particularly important for understanding the polar regions. To make the hillshade and slope for each of the four corner maps, I repeated the same code as above, modified slightly for the ortho (Orthographic) projection and specifying the center latitude and longitude for each map (North:+lat_0=90 +lon_0=90, South :+lat_0=-90 +lon_0=90, East:+lat_0=0 +lon_0=90, West:+lat_0=0 +lon_0=270).
gdalwarp -t_srs "+proj=ortho +lat_0=90 +lon_0=0" ./path_to_intif.tif ./path_to_outtif.tif
gdalwarp -tr 1500 1500 -r average ./path_to_intif.tif ./path_to_outtif.tif
gdaldem hillshade -z 20 ./path_to_intif.tif ./path_to_hillshade.tif
gdaldem slope ./path_to_intif.tif ./path_to_slope.tifWhile making the maps in this series I ran these GDAL commands many times for different planets and moons. To make this process simpler, I created the two bash scripts eckert_iv_dem.sh and ortho_dem.sh to automate the steps described above for each planetary body. eckert_iv_dem.sh will convert the original Plate Carrée DEM into an Eckert IV projection, downsample the file, and create a hillshade and slope. ortho_dem.sh will do the same for the Orthographic projection, for each of four hemispheres. These scripts aren't necessary for making the map (the code explained above will be fine) but I'm including them here as a reference for anyone who wants to automate similar code. To run the bash scripts, type the following into your Terminal window:
bash ./path_to/eckert_iv_dem.sh
bash ./path_to/ortho_dem.shThe International Astronomical Union is responsible for naming features of extraterrestrial objects. You can download a CSV file of all features from the moon from the IAU website. To do this, use the Advanced Search Function to download All Feature Types from your Target (Moon) of only an Approval Status of Adopted by IAU. In the Columns to Include section, select Feature ID, Feature Name, Clean Feature Name, Target, Diameter, Center Lat/Lon, Feature Type, and Feature Type Code. You can also include Origin if you'd like additional information about each feature, such as who it is named after. The Output Format should be CSV.
A geologic map shows different rock types and other features like fault lines and riverbeds. The USGS has a beautiful Geologic Map of Moon, which I'm going to recreate from the same data in a different style. To work with this data, download the 280MB Database ZIP from the USGS Geologic Map. The next section on Map Design in Python explains how to access and plot each type of data in this database.
Next, I made Python plots with geologic units, geologic structures, geologic features, text labels, and gridlines. I often split up data for plotting so I can easily apply section-specific effects in Photoshop or Illustrator. In matplotlib I used gridspec to set up my figures so that each of my subplots occupy the exact pixel locations inside my decorative border.
Geologic units are the different types of rock that make up the surface of the planet. Different rock units are usually represented by different colors. The USGS dataset tags each unit by a 2~3 letter code identifying the rock type. I assigned a color to each letter code by making a table of code-color pairs in Moon_geologic_unit_colors.csv. I referenced this file when plotting each unit in cartopy and matplotlib. Saving my graphics parameters in a separate file makes it easier to try different color schemes, and compartmentalizes the design from the code. I save each of the datasets as a separate figure, so that I could figure out later which order to place them in Photoshop.
Geologic contacts are the boundaries between geologic units. Some geologic boundaries are approximate or hidden under dust. Similar to the geologic units, I use the Moon_geologic_boundaries.csv configuration file to map each type of geologic contact in a different color. In the final map I customized some of the geologic contacts into dotted lines by opening the PDF in Illustrator and selecting all objects of the same color (Select -> Same -> Stroke color). In this project I plotted the Certain contact lines in a separate file from Uncertain and Hidden / Other types of contact lines.
Geologic features are other visible lines on the surface, like channels, crater rims, or ridges. To map each of them in a distinct style, I plotted each one in a different color, and then stylized the lines in Illustrator. The geologic features data was particularly different between datasets, so in the end I only incuded features that were present in more than one dataset. The USGS also has helpful scientific publishing guidelines for geologic maps, if you'd like to use more conventional parameters.
Nomenclature: I downloaded the official feature names for the moon from the IAU. The label sizes are plotted approximately according to the size of the object, though I changed the font sizes substantially in Illustrator after plotting them in Python.
Gridlines and Data boundaries: I used cartopy to plot gridlines for each map projection. I also plotted the borders of each of the six datasets, to give an idea of where geologic contacts and structures overlapped.
Landing sites: To map the landing sites of rovers and other spacecraft on the moon, I used a digitally enhanced image of the moon from the open-source astronomy tool Stellarium as the backdrop. To show all four hemispheres of the moon, I reprojected this image into four Orthographic projections in 3_plot_landing_sites.ipynb.
Data sources: Because there was some visible discrepancies at the borders between the six datasets, I decided to add a key showing the age and area coverage of each of the six scientific studies used in this map. To make this key I plotted just the outline of the map for each dataset, from the perspective of each of the four hemispheres of the moon.
Plotting polar datasets: One additional issue with this data was that the shapes in the two polar datasets were encoded in meters, while the rest of the data was encoded in degrees. The default cartopy globe is based on Earth, which has a much larger circumference than the moon - so data plotted in meters looked very squished and didn't cover the expected amount of space. To fix the issue I declared a custom sphere of the correct dimensions in order to plot the polar data.
# Create globe with radius of the moon, in meters (EckertIV in Cartopy does not support ellipses)
axis = 1737.1 * 1000
globe = ccrs.Globe(semimajor_axis=axis, semiminor_axis=axis, ellipse=None)
large_proj = ccrs.EckertIV(globe=globe)I usually save figures as a PDF so I can edit the text and shapes in Illustrator. There are a couple standard commands I use to export Matplotlib figures so they're easy to edit:
import matplotlib
import matplotlib.pyplot as plt
import matplotlib.backends.backend_pdf as pdf
# Export text as editable text instead of shapes:
matplotlib.rcParams['pdf.fonttype'] = 42
# Preserve the vertical order of embedded images:
matplotlib.rcParams['image.composite_image'] = False
# Remove borders and ticks from subplots:
ax.axis('off')
# Remove padding and margins from the figure and all its subplots
plt.margins(0,0)
plt.subplots_adjust(top=1, bottom=0, right=1, left=0, hspace=0, wspace=0)
plt.gca().xaxis.set_major_locator(plt.NullLocator())
plt.gca().yaxis.set_major_locator(plt.NullLocator())
# Save the Matplotlib figure as a PDF file:
pp = pdf.PdfPages('./savename.pdf', keep_empty=False)
pp.savefig(fig)
pp.close()
# If I don't need to edit vector paths I save the file as a
# PNG so I can import it directly into Photoshop:
plt.savefig('./savename.png', format='png', dpi=600, pad_inches=0, transparent=True)After saving the figure, the PDF file needs to be edited so that each object can be manipulated individually. In Illustrator, select everything in the file and then go to Object --> Clipping Mask --> Release. At this point you can also delete the background and axis border objects, if you included them in the output file.
I export Python figures to Illustrator and Photoshop because several great design features are impossible or very time-consuming in Matplotlib. I'm linking tutorials here for the features I use most often - font alternates and ligatures, custom brushes, layering effects, blur effects, gradients along a path, variable width paths, type on a path, and selecting objects by characteristic.
This project didn't have many special text effects, so the editing in Illustrator and Photoshop was minimal compared to some of my other maps.
I've included a small section of the map in the figures folder as the Photoshop file moon_geology_sample.psd. The file is small enough to upload online, but since it still has the original layers you should be able to use it as a reference for layering effects.
To create a shadow effect around the text labels, duplicate the annotation layer and go to Filter --> Blur Gallery --> Field Blur. For shadow text I usually create two blur layers set to 20% opacity - one with a Blur of 4px and the other 10px.
I wanted the maps in this series to look cohesive, so I made a palette of ~70 different colors and picked from these choices in every map. I also used the same two fonts (Redflowers and Moon) in all maps. You're welcome to use the color palette and font styling if you'd like.
To develop this set of colors, I started the project by designing 14 different color schemes. My initial idea was to have a unique color palette for every planet, but in the end I used the same collection of colors throughout all of the projects to make the maps look more cohesive.
Each color palette is shown in several different ways, because I wanted to design versatile color schemes that could work as discrete elements, or as pieces of a complex pattern, or as a gradient in topographic maps. I updated these three visualizations while designing to make sure each color scheme would work for each application.
For this project I wanted to combine large datasets with the hand-crafted design style of artists like William Morris or Alphonse Mucha. To organize my thoughts I collected a big folder of inspiration images from sources like the New York Public Library Digital Database:
When I started this project I initially wanted to design different border decorations for every topic. I sketched a collection of 18 different repeated patterns, each meant to go alongside a unique astronomy theme like planets, galaxies, space missions, or satellites.
But as the project continued I realized there was so much data that the detailed borders made the maps look too cluttered. In the end I removed all of the borders and designed just one scrollwork illustration to wrap around rounded map projections. In these round maps I thought the shift from detailed map to blank paper was a bit too abrupt, so this was a good compromise between data-heavy and illustrative design styles.
For this scrollwork design I started with a pencil sketch, and tried a couple different iterations of leafy scrolls before finally picking a less botanically inspired design. When I paint decorations like these in Photoshop, I begin each design as a solid white shape and then gradually break away pieces into detailed chunks. Next, I brush away pieces of each section with the brush eraser tool until the pieces look like a fully-shaded monochrome design. I wait to add color until the very last step, where I use many different colors and overlay layers for a richer effect.
I've included two different examples of these painted Photoshop illustrations in the figures folder as scrollwork_sample.psd and decorations_sample.psd. These files still have the original layers, so you should be able to use it as a reference for layering, painting, and color effects.
- Astronomy. Andrew Fraknoi, David Morrison, Sidney C. Wolff et al. OpenStax 2016.
- Gazetteer of Planetary Nomenclature. International Astronomical Union (IAU) Working Group for Planetary System Nomenclature (WGPSN) 2019.
- Planetary Symbology Mapping Guidelines. Federal Geographic Data Committee.
- LRO LOLA Elevation Model 118m (LDEM GDR). NASA PDS and Derived Products Annex. LOLA Science Team 2018.
- Lunar 5M Geologic Map Renovation. NASA PDS and Derived Products Annex. USGS Astrogeology Science Center 2016.
- Missions to the Moon. The Planetary Society.
- Fonts: Moon by Jack Harvatt and RedFlower by Type & Studio.
- Advice: Thank you to Henrik Hargitai, Oliver Fraser, Chloe Pursey, and Leah Willey for their helpful advice in making this map.
Code: All of the code in this repository is shared under the GPL-3.0 license.
Data: The data in this repository belongs to the original authors of the data. Please use the references section to look up the original version. In cases where I edited or revised the data, I impose no additional restrictions to the original license. Any data files I created myself are shared under the ODC Open Database License.
Artwork: The artwork included in this repository are shared under a Creative Commons Attribution-NonCommercial-NoDerivatives 4.0 International License.