MIP Logo

National Park Services Api

This post was originally published on The Data School blog between 2018 and July 2025, before our program was renamed to MIP’s Analytics Career Accelerator. References throughout this article to “The Data School” or “DS” all refer to what is now MIP’s Analytics Career Accelerator. The program, its people, and its commitment to launching outstanding analytics careers remain the same – just under a new name.

If you are having trouble viewing this article, please report it here

Hello everyone! Today, I want to share insights from the third day of Dashboard Week, where we focused on working with APIs. Our project centered around the National Park Service API, which provides a wealth of information across several endpoints covering parks, places, people, activities, amenities, and more.

To begin, I used Alteryx to retrieve data from the API. The API has a limit of 1,000 queries per hour, and each request returns a default of 50 rows. To overcome this, we needed to adjust the URL parameters, setting the limit to match or exceed the total number of rows required.

The image below shows the entire Alteryx workflow, which outputs three datasets I used in my dashboard. I also created a separate workflow to process the ‘Activities’ endpoint in Alteryx.

Once the data was imported into Tableau, I established the model and relationships, as seen in the image following.

In my dashboard, I focused on comparing park entrance fees. Additionally, I included options for users to filter based on park type, preferred activities, and budget.

Conclusion:
Users can now easily find parks that align with their preferred activities and budget, making it simpler to plan their visits.

Share this post