> For the complete documentation index, see [llms.txt](https://digital-carleton.gitbook.io/digital-mapping-for-humanists/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://digital-carleton.gitbook.io/digital-mapping-for-humanists/master.md).

# Digital Mapping for Humanists: A Cookbook

## Introduction

Maps, mapping, and spatial understanding are central to many current projects in the humanities. Too often, however, the tools and approaches that facilitate spatial knowledge are limited to GIS and data analysis most useful to scientists and social scientists. Humanities researchers and teachers bring a range of other concerns to spatial data: to work smoothly with historical maps from other spatial traditions, to work in languages other than English, to incorporate a range of media, and to represent ambiguity just to name a few issues.

> #### This open-access, collaboratively authored "cookbook" is dedicated to helping spatially-minded humanities scholars produce maximal research insight, pedagogical utility and suitability for public outreach.

## What is a mapping "cookbook"?

Culinary cookbooks offer recipes for making specific dishes. A tech or [programming "cookbook"](https://en.wikibooks.org/wiki/Coding_Cookbook) contains "recipes" to make specific things on the computer. A cookbook differs from a reference manual or tutorial documentation in that it doesn't attempt to cover all aspects of the topic, detail all the tools, or teach you the basics from the ground up. Rather, it contains "recipes" to teach you just those ingredients and steps necessary to perform a specific task.

This mapping cookbook, created for a workshop on [Fostering Humanistic Tools for Digital Mapping](https://www.acm.edu/professional_development/project/104/fostering-humanistic-tools-for-digital-mapping) funded by the Associated Colleges of the Midwest, contains recipes for adapting existing digital mapping tools to better meet the needs of humanistic scholars. Participants share proven methods of navigating obstacles within existing mapping tools to produce effective humanities-based digital maps.

## How to Use this Site

There are a number of ways you can use and contribute to this site:

* Read the **Instructions and Examples** recipes for thinking through how to get started
* **Use our recipes** to make your maps better!
  * **Browse complete recipes** in the table of contents, or 
  * **Search for keywords** using the search bar top right
* **Contribute** to the project and share your tips by 
  * **Editing an unfinished recipe**
  * **Writing a new recipe** (read about [How to Write a Good Recipe](/digital-mapping-for-humanists/how-to-write-a-good-recipe.md), check out the [Add Historic Maps to ArcGIS Online](/digital-mapping-for-humanists/recipes/add-historic-maps-to-arcgis-online.md) recipe as an example, and copy the [Recipe Template](/digital-mapping-for-humanists/recipe-template.md) to get started)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://digital-carleton.gitbook.io/digital-mapping-for-humanists/master.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.