---
# System prepended metadata

title: '(##?)Reference: Tutorials and File Types'
tags: [session-2-chunkified]

---

# (##?)Reference: Tutorials and File Types

###### tags: `session-2-chunkified`

**tm note: I think this can be slotted into the "Decoding Data Types" chunk as hidable boxes... I've gone ahead and done that, but left this as a standalone file just in case...**

---

This section can serve as a reference on your mapping journey. Do not feel pressure to dive into all of these techniques now, but the resources linked below can help you use these tools as you need them. 

There is a vast set of file types you might encounter when making or viewing maps and data, but a few of the most common are the following:


### Tabular Data

Often, you will find the information you want to use in a Comma Separated File. The CSV works very similarly to an Excel sheet or Google Sheet. Once you are comfortable working with one of these, you will be able to navigate all of them, as well as any other similar spreadsheet entities you encounter. 

These are all examples of **tabular** data sources, which include anything that comes in a spreadsheet format with rows and columns. This is how we look at our attribute data when using GIS software. When performing a join, a column from our tabular data source serves as the identifying information that makes the join possible. For example, there could be a column listing the names of states used to join the data with a spatial resources. 

If you do not have geographic identifiers for a set of data but do have addresses or another identifier, **geocoding** can convert these data to a GIS-readable format.

This brings us to our next set of files.

### Spatial Data

There is another family of file types curated specifially for the mapmakers of the world. These methods of data storage are specifically used for spatial/geographic purpose. Some common examples are Shapefiles, GeoJSON, and GeoTIFF. 

You might hear people talk about "putting a Shapefile" into a GIS software. This means that they are opening the file to view its contents. These files have a visual component when opened in a mapping environment.They could provide the borders of every county in Massacusetts, for example. Examples of this software include [QGIS](https://www.qgis.org/en/site/), [ArcGIS Online](https://www.arcgis.com/index.html), and [Carto](https://carto.com/).

### Learn More

Unfortuantely, we will not have time to dive into the technial details of these file types in this course. However, the internet is full of helpful resources if you are interested in learning more and using any of these file types or software. It is often a matter of finding which tutorials work best for you, but here are some good places to start:


#### Working with Spreadsheets

[Zapier tutorials](https://zapier.com/learn/google-sheets/google-sheets-tutorial/) for Google Sheets

[Compiled tutorials](https://digital.com/excel-tutorials/) for Excel 

#### Mapping Software 

[Helpful lessons](https://www.qgistutorials.com/en/) for QGIS

[Carto provides lessons](https://carto.com/help/tutorials/getting-started-with-carto-builder/) for using its platform (hover over Tutorials tab to see categories).



This section can serve as a reference on your mapping journey. Do not feel pressure to dive into all of these techniques now, but the resources linked below can help you use these tools as you need them. 

There is a vast set of file types you might encounter when making or viewing maps and data, but a few of the most common are the following:

<Hideable title="Tabular Data">


Often, you will find the information you want to use in a Comma Separated File. The CSV works very similarly to an Excel sheet or Google Sheet. Once you are comfortable working with one of these, you will be able to navigate all of them, as well as any other similar spreadsheet entities you encounter. 

These are all examples of **tabular** data sources, which include anything that comes in a spreadsheet format with rows and columns. This is how we look at our attribute data when using GIS software. When performing a join, a column from our tabular data source serves as the identifying information that makes the join possible. For example, there could be a column listing the names of states used to join the data with a spatial resources. 

If you do not have geographic identifiers for a set of data but do have addresses or another identifier, **geocoding** can convert these data to a GIS-readable format.

This brings us to our next set of files.

</Hideable>

<Hideable title="Spatial Data">

There is another family of file types curated specifially for the mapmakers of the world. These methods of data storage are specifically used for spatial/geographic purpose. Some common examples are Shapefiles, GeoJSON, and GeoTIFF. 

You might hear people talk about "putting a Shapefile" into a GIS software. This means that they are opening the file to view its contents. These files have a visual component when opened in a mapping environment.They could provide the borders of every county in Massacusetts, for example. Examples of this software include [QGIS](https://www.qgis.org/en/site/), [ArcGIS Online](https://www.arcgis.com/index.html), and [Carto](https://carto.com/).

</Hideable>

<aside>

### Learn More

Unfortuantely, we will not have time to dive into the technial details of these file types in this course. However, the internet is full of helpful resources if you are interested in learning more and using any of these file types or software. It is often a matter of finding which tutorials work best for you, but here are some good places to start:


#### Working with Spreadsheets

[Zapier tutorials](https://zapier.com/learn/google-sheets/google-sheets-tutorial/) for Google Sheets

[Compiled tutorials](https://digital.com/excel-tutorials/) for Excel 

#### Mapping Software 

[Helpful lessons](https://www.qgistutorials.com/en/) for QGIS

[Carto provides lessons](https://carto.com/help/tutorials/getting-started-with-carto-builder/) for using its platform (hover over Tutorials tab to see categories).

</aside>

<aside> 
### Discussion: How might these various file types and data collection and storage methods introduce bias?

</aside>