Title Card: Creator: Parisa Setayesh | Level: Beginner | Category: Data: Data, Space and Place

Why this matters
Messy data is one of the fastest ways to make mapping feel impossible. GCDI’s How to Organize Data for Maps signals this very clearly with its example of a basic spreadsheet in which each sample is a feature and one sample is represented in each row. QGIS documentation reinforces the same logic for delimited text files: the file should have a header row, fields must be structured consistently, and coordinate fields must be numeric if they are being used to create geometry.

Key ideas

• One row should usually represent one feature or observation.
• Columns should represent fields or variables.
• Coordinate columns must be clean and consistent.
• IDs and field names matter more than they seem.

Lesson
This lesson should help learners see that spreadsheet design is already part of mapmaking. Many spatial problems that appear later inside QGIS, R, or a web mapper actually begin upstream: multiple values crammed into one cell, inconsistent place names, missing IDs, numbers stored as text, mixed coordinate systems, blank rows, or ambiguous field names. A clean table is not busywork; it is what makes the map possible.

This is also a good place to teach a few durable habits: use a stable unique identifier when possible, keep one observation per row, avoid decorative formatting, make field names clear, and keep a separate note of what each field means. For many beginners, this lesson is the moment when mapping becomes less mystical and more procedural in a useful way.

Example Project or GCDI resource
How to Organize Data for Maps should be the anchor post here. It is already doing the exact pedagogical work this lesson needs: translating mapping into concrete data organization practices that a beginner can apply immediately.

Open reading / resource
Use the QGIS documentation on Importing a delimited text file and Delimited Text Files. These pages are especially helpful because they tie abstract advice to very concrete requirements for getting a table into a GIS correctly.

Reflection / mini activity
Open a spreadsheet you already have — or create a tiny sample one. Ask:

• Does each row represent one feature?
• Are the column names understandable?
• Is there an ID field?
• Are coordinates stored as numbers?
• What would confuse someone else trying to map this?

Then make one pass of cleanup.