Posted on 26 Mar 2015 by
I had the honor of traveling to University of Wisconsin-Madison last week as an invited speaker for the Yi-Fu Tuan Lecture Series put on by the Department of Geography. I had an amazing time and want to highlight some of what I did during my visit. I also want to take this opportunity to thank everyone in the Department for being such gracious hosts!
The Geography Department at UW-Madison is really inspiring. The way in which students, faculty, and staff collaborate and teach each other is something that really stood out during my visit. The comradery is contagious and I found myself wishing I was back in grad school as part of this Department. After my visit, it is clear to me why UW-Madison alumni are some of the most talented cartographers I know.
Cartography students and staff in the UW Cartography Lab.
In addition to meeting with students, faculty, and staff, I also had the honor (and pleasure) of meeting with Yi-Fu Tuan, emeritus professor and sponsor of the lecture series. Yi-Fu is a pillar of our discipline - having pioneered the field of humanist geography and the notion of space, place, and nature in a completely new way.
What was most inspiring during my time with Yi-Fu was listening to him explain why he started the speaker series. He started it to give his colleagues in the Department a venue to share their work by creating a place where connections could be made and where everyone was aware of what was going on around them. Over the years, the series has grown into one where professionals (both researchers and practitioners) from around the world come to Madison to share their work.
My Yi-Fu talk gave a look into how NPMap is customizing open source tools to make web mapping possible for everyone at the National Park Service. I also spent a good amount of time explaining how we are incorporating the National Park Service's graphic identity and accessibility/usability guidelines into our toolset. My slides and abstract can be viewed here.
Giving my talk in Science Hall.
I also had the opportunity to facilitate a Brown Bag Lunch conversation about the evolution of online basemap design. On Saturday, I led an introductory Mapbox Studio workshop with 30 students. By the end of the workshop, each student had published tiles using a custom vector data source and modified the design of an out-of-the-box Mapbox Studio template to support their custom overlay.
Saturday introduction to Mapbox Studio workshop.
This is a very brief synopsis of an increadible few days in Madison. It was good to see old friends and make new ones. I am especially excited for what the future of cartography is knowing the caliber of students, faculty, and staff around the world in Geography departments like the one at UW Madison!
Finally, I would like to give an extra special thank you to my Madison host, and friend: Professor of Cartography, Dr. Rob Roth!
Posted on 10 Mar 2015 by
I am extremely excited to introduce our new cartographer, Jake Coolidge!
Jake will help out with a number of projects - including improving our suite of Park Tiles basemaps and developing tilesets for National Park Service maps. He'll also lead the effort to develop and implement multi-scale cartographic data standards for the Places database.
Jake brings years of cartographic experience to the team. He worked as the Geospatial Historian at the Spatial History Project at Stanford University until January 2013. While there, he published his cartographic works in multiple journals and publications - including a hand drawn map featured in last year's Atlas of Design. More recently, Jake freelanced for clients like Duke University, Stanford University, and the City of Oakland... to name a few!
Jake is more than a cartographer, he is also an artist, and we are looking forward to working with him to define the future of National Park Service maps.
Take a look at Jake's team page for more information about his background and interests. You can also find him on Twitter.
Posted on 01 Dec 2014 by
NPMap is growing, and we're looking for a Data Engineer and a Cartographer to join us in defining the future of National Park Service maps.
As part of our team, you can expect to work on a wide variety of projects for parks, programs, and partner organizations. If building custom tools for digital mapping and making government more open and transparent interest you, we encourage you to apply!
Follow the links below to read the full position descriptions and apply.
If you have additional questions, feel free to contact me at email@example.com.
Posted on 04 Aug 2014 by
With an average of ten million visitors each year, Great Smoky Mountains National Park experiences many visitors who get lost in the park because of inaccurate Location-Based Services (LBS) or outdated maps. Park-issued maps are available at visitor centers, but many visitors rely on navigation assistance from their mobile phones or other GPS devices. This is a major problem because the map data used by many LBS providers does not reflect authoritative data - causing many visitors to follow poor navigation directions.
Great Smoky Mountains National Park is a 276,344 acre park located on the border of North Carolina and Tennessee.
In Comes OpenStreetMap
When the NPMap team announced several initiatives built around OpenStreetMap (OSM), the Smokies quickly saw an opportunity to get accurate maps and data into the hands of an increasingly technologically-savvy public. All National Parks must make their authoritative map data available through the NPS Data Store, but few park visitors possess the knowledge or the software required to manipulate the data or load it onto their personal electronic device. OpenStreetMap, on the other hand, is built specifically for non-technical users, and it gives them the ability to edit and interact with the data in a platform of their choosing.
During the summer of 2013, the Smokies approached the OSM community through the Imports-US mailing list with their proposal for uploading the park's authoritative data to the OSM database. The park engaged with the community because any significant addition or alteration of OSM data usually requires a discussion to:
- Ensure that the data is a good fit for the OSM model
- Reach agreement with the community on how the data will be entered into the database
Initially, the park struggled with some of the feedback received during the import discussion process. Like any federal agency, the Park Service must follow strict rules when publishing map data in any format. For example, federal regulations prohibit a government entity from publishing the name of a geographic location unless that name has been approved by the United States Geological Survey's Board of Geographic Names. Given that the OSM database is based on “crowd-sourced” input, many OSM members felt that the park's official names for many features were not inline with local, common, or well-known geographic names that members of the public might recognize. Ultimately, consensus was achieved when the park agreed to add an “Official Name” tag to data it was contributing to OSM.
Experienced OSM mappers were also able to help the Smokies work through some challenging “tagging” questions, such as how to tag buildings, deal with TIGER data, and document National Park Service tagging guidelines on the OSM Wiki. The value of this feedback emphasizes the importance of reviewing import proposals with the OSM community.
Following agreement on how the park would proceed with its OSM import, the park converted its authoritative base data into shapefile format - allowing it to be imported via the Java OpenStreetMap (JOSM) application. For the many features that already existed in the OSM database, park mappers simply conflated (replaced old with new) geometries, such as road and trails, with the more accurate park data, then attributed the tags according the NPS tag wiki. They completed a portion of the park and made the OSM database available for public review before completing the import and posting all of the data to the production OSM database.
A Lesson Learned
One important lesson was learned when the park ran into significant data validation issues related to the amount of data they were uploading at one time. This was related to the length of time it took to edit such a large geographic footprint. During the few weeks that the park was uploading data, many changes were still occurring to the “live” OSM database, which led to an increase in time spent re-validating data. In addition, the park experienced the ubiquitous computer crash during an upload of several hundred thousand objects (each node edit is counted as an object), resulting in a hair-pulling, all-night-long correction of a duplicate upload to the OSM database.
Because of this experience at the Smokies, the NPMap team is now discouraging bulk uploading and editing of NPS data in the OSM database - at least for the time being. The team now recommends that no more than a few features be edited or uploaded at once. The team is investigating ways to simplify the process of getting data from internal NPS databases into OSM.
The entire process, including import discussion and editing, took about 400 hours for the park to complete. The NPMap team and Smokies staff spent much of that time documenting tagging guidelines on the OSM wiki. These guidelines are meant to make it much easier for other National Parks to contribute their data to OSM. The NPMap team expects that parks following those guidelines would be able to complete a park-wide update of their data in OSM in 40 hours or less.
The park is well-mapped in OpenStreetMap now.
The Smokies update to OSM has been complete for over a year now. Present in the OSM database, available for public use, is what the National Park Service considers essential base data for visitor services: transportation networks, points of interest, and visitor services infrastructure. For example, anyone can consume OSM data from the Smokies and make a map showing the location of visitor centers, ranger stations, campground, and hiking trails - no specialized skills required!
The continued maintenance of the Smokies data in OSM is a dynamic process. Through the OpenStreetMap editor and specialized tools like MapRoulette, other OSM mappers continue to improve upon the park's contribution by, for example, updating feature that have too many nodes or making cartographic improvements to feature geometry.
The National Park Service does not monitor or endorse commercial mapping applications, but the Smokies has noticed that many smartphone and web-based applications are using the park's OSM data. This demonstrates that OpenStreetMap is a great way for the Smokies to make their authoritative data available for public usage in an open way - with no restriction on how the data is used or distributed.
Posted on 11 Jun 2014 by
We just released a new version of the state page maps for each of the NPS.gov state pages. These maps are intended to demonstrate the breadth of the impact the National Park Service has on communities across America. They include National Parks as well as locations from various NPS programs like the National Register of Historic Places, Federal Lands to Parks, the Rivers, Trails, and Conservation Assistance Program, and more.
The previous version of the state page maps used out-of-the-box Bing tiles. The maps now use our custom basemap, Park Tiles. The design of Park Tiles pushes National Park unit boundaries and program locations to the forefront of the map.
About the Technology
NPMap.js is built on top of Leaflet and uses the Leaflet.markercluster plugin internally to support marker clustering. This makes it possible to display the more than 100,000+ program locations across the country while maintaining good performance across all platforms and browsers.
The point data for each of the maps is stored and served directly from GitHub using GitHub Pages.
Take a Look
You can access the state pages directly from the NPS.gov home page. Simply select a state from the dropdown at the top right-hand corner of the page.