Crater Lake National Park


Digital maps for the National Park Service

Denver OpenStreetMap Editathon

Posted on 17 Apr 2013 by Nate Irwin

National Park Service and OpenStreetMap

Join Mamata and I as we help improve OpenStreetMap coverage for our National Parks at the Denver OpenStreetMap Editathon this Saturday, April 20th, on the DU campus.

We'll be meeting in Room 123 of Boettcher West (2050 E. Iliff Avenue) from 10am-4pm. Wifi is provided, but make sure to bring your own laptop. You can RSVP on the OSM Colorado Meetup event page:

We hope to see you there!

Using Park Tiles in ArcGIS Online

Posted on 22 Mar 2013 by Mamata Akella

Esri recently released a new version of ArcGIS Online that introduced some new capabilities, including the ability to add a Tile Layer with a URL template. This means that Park Tiles, which is designed and hosted using tools from MapBox, can now be added to an ArcGIS Online map.

How To

  1. Go to the My Map view in the map viewer
  2. Click on the Add button in the top left hand corner of the My Map interface
  3. Select the option to "Add Layer from Web"
  4. From the drop-down in the Add Layer from Web window, choose the option to reference "A Tile Layer"
  5. Copy and paste the follwoing into the "URL" field:
  6. If you would like to use Park Tiles as your basemap layer, check the option "Use as Basemap"
  7. Give the map a Title and Credits
  8. In the Subdomains field type the following: a,b,c,d
  9. Click the button to "Add Layer"

The Add Tile Layer interface in ArcGIS Online

You should now see Park Tiles loaded into the ArcGIS Online map viewer.

You can hide layers by taking the ID of the layer out of the URL. For example, you can hide Road Shields by taking out of the URL.

Our Conference Schedule for 2013

Posted on 21 Feb 2013 by Nate Irwin

Sequestration is putting a bit of a damper on our travel this year, but we are still planning on attending and presenting at several conferences. Mamata is doing the bulk of the traveling, but our entire team is going to try to make it to State of the Map US in San Francisco in June. Here's a list of the conferences we'll be at this year:

  • FedGeo Day - February 28, 2013 in Washington, DC
  • FOSS4G NA - May 22-24, 2013 in Minneapolis, MN
  • SOTM US - June 8-9, 2013 in San Francisco, CA
  • NACIS - October 9-11, 2013 in Greenville, SC

If you are going to be at any of these conferences, make sure to find us and say "hello"; we'd love to talk shop!

Relief Methodology in Park Tiles

Posted on 11 Feb 2013 by Tom Patterson

During our initial planning for Park Tiles, we spent a week working on shaded relief and cartography with NPS Cartographer and relief guru Tom Patterson. In this guest post, Tom explains the design rationale behind how the shaded relief is symbolized in Park Tiles.

Tom has created a methodology for generating shaded relief specifically for web maps. Be sure to check out the link at the bottom of this post for his online web relief tutorial.

Mamata Akella


Given the world famous landscapes of Grand Canyon, Yosemite, and other National Parks, including shaded relief on Park Tiles was an easy decision to make. Trickier to decide was just how to design a shaded relief that could do justice to this spectacular terrain while also serving as an unobtrusive background for multi-purpose maps. Another objective was creating a relief that complements the design standards found on the visitor maps produced by Harpers Ferry Center.


On Park Tiles, the shaded relief functions as a ubiquitous background. The relief is kept light to maximize the legibility of park areas, roads, rivers, boundaries, urban areas, and labels that appear on top of it. A relief that prints too dark would lessen overall map legibility. We also wanted a color that could stand on its own as an attractive and pleasing tone — thus, sterile gray was ruled out. After trial and error, we decided on light, neutral beige.

A beige shaded relief makes it possible to present other map information lightly and with clear visual hierarchies. For example, roads appear unobtrusively in a light red. The shaded relief also features reduced contrast for its highlights and shadows. This makes for a less “noisy” background—the shaded relief does not distract from park and thematic information on the map. And because a little tone exists even the brightest highlights, white state and international boundaries show up no matter how rugged the terrain.

Ocean Vignettes

We’ve also paid close attention to water. Tones for land and water are complementary yet provide enough figure-ground contrast to distinguish the coast. River and lakes use the same blue tint as the oceans, putting all water features on the same visual plane. Even more important, the land-water boundary appears without any thin coastal lines, making for a cleaner map. A feathered vignette applies darker blue tones along the immediate coast fading to lighter blue further offshore. This graphical effect gives emphasis to coasts without excessively darkening the map.


Creating the shaded relief and ocean vignettes was accomplished with a combination of GIS and graphical software. For example, coloring the shaded relief as beige and adding ocean vignettes occurred in Adobe Photoshop using the Geographic Imager plugin by Avenza, which maintains georeferencing. We used Natural Scene Designer 6.0 to generate the shaded reliefs, saved as GeoTIFFs. To get around the 4GB file size limit for GeoTIFFs, we created smaller, overlapping shaded reliefs for the very large areas covered by zoom levels 9 and higher. We then used GDAL VRT files to reference the multiple GeoTiffs, and then loaded these single pieces into TileMill, giving these relief pieces a seamless appearance on the final online map.

Natural Scene Designer 6.0

For detailed information on creating web map shaded relief, visit

The Anatomy of Park Tiles

Posted on 24 Jan 2013 by Mamata Akella

In a previous post, we introduced you to Park Tiles, an online basemap we are working on. In this post, we'll go into more detail about how we're serving Park Tiles and outline how you can use the basemap in your own web maps.


We've all seen the traditional mash-up pattern where data are placed on top of a basemap and, in turn, obscure the underlying (and important!) contextual information. Most “traditional” online basemaps used in web map applications have been designed for navigation first and foremost. Because of this, these basemaps tend to be information rich with a wide variety of highly-saturated colors to denote different road, landuse, and landcover types. The problem with these traditional designs is that information mashed-up with them doesn't always pop off the map and often gets lost. As the use of basemaps as backdrops for spatial information changes, the way these basemaps are designed and served needs to change as well.

Basemaps available through various providers are shifting towards a more minimalist and subdued style where a better figure-ground relationship is established between the basemap and the mashed-up content. This isn't a new idea. It is something print cartographers have done for years. For example, in a National Geographic Atlas, you don't see bird migration data on top of a road map with all of the reference information covered up. You, rather, see these data overlaid on a map background that supports the information instead of distracting from it.

As described in our introductory blog post, the design of Park Tiles is a subtle one. The shaded relief on the basemap is colored to make it sit nicely in the background and the other reference information is equally subdued. The features that are highest in the visual hierarchy are National Park units and their labels. This design ensures that Parks are clearly visible and information that is mashed up on the basemap comes to the foreground (if designed appropriately).

Another pattern that has emerged over the past few years is a change in the way basemaps are served. More and more, we're seeing basemaps that are separated into various components. Some examples include Esri's Terrain with Labels and Light Gray Canvas Map. Both of these maps gives users the ability to put reference information that is typically underneath mashed-up content on top. MapBox's suite of basemaps goes one step further, giving users the ablility to reorder layers, turn groups of features on and off, and recolor groups of features dynamically. With the release of their new basemap designs, Stamen has also created a reference overlay from their Toner style that can be used to provide geographic context with other basemaps. Two of the first online basemaps to demonstrate these new patterns were Esri's Terrain with Labels (released in 2009) and GeoIQ's Acetate basemap (released in 2011).

Our Idea

We have been thinking about how we can take this pattern one step further. We have decided to “explode” Park Tiles into multiple layers. What this means is that each feature on the map is served on its own.

We decided to do this for a few reasons:

  1. We want to support multiple overlay types - including points, lines, and discontinuous/continuous polygons.
  2. We want to get the greatest amount of flexibility out of our basemap so we can mix and match layers to support any number of projects and applications.
  3. We feel like this is new pattern is worth exploring.

Take a Look

You can use our Park Tiles Viewer to explore this pattern in more detail. In the bottom right-hand corner of the map, click the "Toggle Layer View" button.

Under the Overlays layer section, you will find two pre-generated overlay examples that are discussed in more detail below.

Overlay Types

Here are some examples of how this pattern works with line and continuous polygon data:

National Trails (Lines)

We want our National Trails data to be shown over Parks and water features, but, as seen in the image below, we don't want them to overrun labels for Parks, cities, and hydro features.

Default Trails

In this case, we can put the tiles for our National Trails underneath the tiles for Park, city, and hydro labels.

Reordered Trails

Ammonium Deposition in Parks (Continuous Polygons)

The traditional mash-up pattern is to overlay contiguous data on top of a basemap while using transparency to allow the underlying geographic context to be seen.

Default Mash-up

A more desirable view of the Ammonium Deposition overlay would be a view where the context (roads, labels, Park polygons, etc.) are on top. In this case, we would put the Ammonium Deposition tiles above the shaded relief but below all of the other reference information. The result can be seen in the image below.

Better Mash-up

The above example still has some issues. The urban areas (symbolized in a pale yellow) can be misinterpreted as data and it is difficult to see the variation in Ammonium Deposition in Rocky Mountain National Park because Park polygons are symbolized with a fill.

The solution is to turn off the urban area and symbolize Park polygons using outlines. This way, there is no other polygon data interfering with the continuous surface of Ammonium Deposition.

Ideal Mash-up


By serving Park Tiles as individual tilesets, we're giving ourselves the flexibility to use the individual components of the map for a variety of projects. For example, in some of the Park projects we work on, the focus of the map is only on a subset of Parks managed by the Park Service. In those cases, we would not serve our layer with all of the Parks displayed, but would instead create an alternative Park layer to display only the relevant Parks on the map. The number of use cases addressed by this basemap is huge. Each layer of the map can be mixed and matched into a variety of web maps, and each layer of the basemap can be ordered in a way that best tells the story of the overlaid data.

How to Use and Access Park Tiles

Whether or not you are a Park Service employee or partner, you may find our new basemap and the pattern we've implemented useful in some of your projects. If you'd like to learn more about how to access these tilesets and use them in your own applications, take a look at the Using Park Tiles tutorial in our support documentation.