A project title is not a project. "Make a map of your city" has launched a thousand abandoned weekends, because the beginner immediately hits the questions the title never answered: which data, in what order, analyzed how, and finished when? So this guide specs six projects the way a good manager would: data source named, steps ordered, the single analysis that makes each one GIS rather than illustration, and an explicit finish line. They run in difficulty order, and the skills stack: project one's styling becomes project two's choropleth, whose join becomes project six's service gap analysis. Pick the first one. Finish it. The checklist above is the finish line habit in tool form. These projects are stage four of the learn GIS plan; if the vocabulary below is new, that plan's first stages come first.
Home / GIS and Open Map Data for Beginners
GIS Projects for Beginners: Six Small Projects, Fully Specced, Sequenced by Difficulty

Photo: Kampus Production / Pexels
Your First GIS Project: Finish Line Checklist
Check off each step as you finish it. Your progress stays on this page.
0 of 7 complete
0% done
Project 1: My Neighborhood, Mapped Properly
Data source: an OpenStreetMap export of your neighborhood (our download guide shows the routes), plus three places you choose yourself.
Steps: load the streets, buildings, and green spaces as separate layers; style each layer distinctly; label the streets you actually walk; add your three places as a point layer you create by hand; compose a print layout with title, legend, scale bar, and north arrow; export as PDF.
The one analysis: count and classify. Use the attribute table to count buildings by type, or amenities by category, and put the resulting numbers in the map's margin: "214 buildings, 31 shops, 4 parks". Counting is the seed of all analysis.
Finish line: a PDF a neighbor could use to find everything you labeled, with the counts printed on it. Difficulty: the gentlest possible start, and deliberately so; every later project reuses this layout skill.
Project 2: A Choropleth of Your Home Region
Data source: official district or county boundaries from your open data portal, plus one statistics table from the national statistics office: population density, median age, rainfall, your choice.
Steps: load the boundaries; open the statistics table and find the code column both files share; join the table to the boundaries on that code; style the joined layer by the statistic in five classes; add a legend that states the classes honestly; export.
The one analysis: the join itself, plus one sentence it earns. The map must let you write, truthfully, "the three densest districts are all in the north" or whatever your data says. If the join fails, the codes do not match, and fixing that mismatch is the real lesson of this project; every working analyst has served this apprenticeship.
Finish line: a shaded map whose every district carries a real statistic, with the source and year printed on the page.
Project 3: Every Coffee Shop in Town, and the Gaps Between Them
Data source: OpenStreetMap points for cafes, pulled with an Overpass query like the one in our OpenStreetMap API guide, for your town's boundary.
Steps: extract the cafe points; load the town boundary; clip the points to it; style by any attribute the data carries (chains versus independents, if the brand tag allows); measure the distance from a point you choose, your home, your office, to the nearest cafe; export.
The one analysis: spacing. Compute each cafe's nearest neighbor distance, or map the point farthest from any cafe, the coffee desert. The deliverable number: the largest gap, in meters, and where it is.
Finish line: a map that shows the pattern and states the gap, with the query and date recorded, because the data changes under you and honesty includes a timestamp.

Project 4: An Elevation Profile of a Known Hike
Data source: a public digital elevation model for the area, plus the trail line, from OpenStreetMap or a GPX track of your own.
Steps: load the elevation raster; drape the trail over it; sample the elevation along the line; chart distance against height; read off the total ascent by summing the climbs, not just the difference between start and summit; export the profile with the map.
The one analysis: elevation gain, computed properly. The start to finish difference lies; the honest number accumulates every rise along the way, which is the entire subject of our guide to elevation gain. Your profile is where that concept becomes a picture.
Finish line: a profile chart labeled with distance, total gain, and the steepest kilometer, beside the map it came from.
Project 5: Your City at Two Ages
Data source: two vintages of the same area: OpenStreetMap data at two dates, two years of aerial imagery, or historical and current building footprints from your open data portal.
Steps: load both vintages in the same coordinate system, and stop until they align exactly, because this project fails precisely there; classify or extract the built area in each; compute the area of each; map what appeared and what vanished in different colors; export both maps at the same scale.
The one analysis: change, measured. Built area then, built area now, the difference in hectares, and the direction of growth. Two numbers and a map that shows where they came from.
Finish line: a same-scale pair with the change quantified in the caption. This is the hardest data discipline of the six so far, and the first project that resembles professional monitoring work.
Project 6: The Library Service Gap
Data source: library locations (OpenStreetMap or your library system's list), district boundaries, and population by district from the census.
Steps: load the libraries as points; draw a buffer around each at a distance your group agrees means walkable, 2 kilometers is a defensible start; dissolve the buffers into one served zone; join population to districts; compute each district's population outside the served zone; style districts by their unserved population; export.
The one analysis: a gap with a number on it. "Districts A and C hold 38,000 residents outside a 2 kilometer walk of any library, 61 percent of the city's unserved total." That sentence, earned by a buffer and a join, is the most employable artifact in this entire guide.
Finish line: a map a librarian could take into a budget meeting. When you can build this, the beginner label no longer applies to you, whatever your job title says.
The Rules That Make Projects Finish
One project at a time; the second project's data may not be downloaded until the first project's PDF exists. Every project exports something; a project that lives only inside the software is a rumor. Every export carries its data source and date, because maps without provenance are decoration. And every project gets shown to one human, because the questions they ask are the syllabus for what you learn next. The data under all six projects is the open data this pillar exists to explain; our open map data guide covers the licenses that let you use it, and the skills sequence from GIS for beginners fills any gaps the projects expose.
The Shared Toolbox: Six Operations Doing All the Work
Read the six specs again and a pattern surfaces: a handful of operations recur, and learning the operations is the transferable skill, while the projects are just their costumes. This table is the cheat sheet to keep beside the keyboard.
| Operation | What it does | Projects that use it |
|---|---|---|
| Load and style layers | Shows each dataset distinctly and legibly | All six |
| Attribute count and filter | Counts and selects features by their facts | 1, 3 |
| Join by code | Attaches a statistics table to boundaries | 2, 6 |
| Buffer | Draws a distance zone around features | 6 (and 3, in spirit) |
| Nearest neighbor and distance | Measures how features relate in space | 3 |
| Sample along a line | Reads values, like elevation, along a path | 4 |
| Compare two vintages | Aligns two dates and measures change | 5 |
Notice that project 6, the capstone, is nothing but load, join, and buffer, operations from projects 1 and 2, aimed at a question that matters. That is the deepest lesson the sequence teaches: professional GIS is rarely exotic machinery. It is basic operations, chosen well, on data whose limits you understand, in service of a question someone actually asked. When you meet a new problem, decompose it into this toolbox before reaching for anything fancier; nine times in ten the decomposition is the solution.
Showing Your Work: The One Page Write-Up
Each project's export deserves a one page companion, and writing it is a skill employers quietly screen for. Four paragraphs suffice. The question, in one or two sentences a non-specialist understands. The data, named with sources and dates, because a map whose data cannot be traced cannot be trusted. The method, in plain steps, naming the operations from the toolbox above. The result, leading with the number the analysis earned, and closing with the limits: what the map cannot prove, where the data was thin, what you would do with better sources. That last paragraph, the honest limits, is the one beginners omit and professionals never do, because a mapmaker who states their limits is one whose numbers can be relied on. Keep the six write-ups with the six exports and you hold a portfolio that demonstrates not just that you can operate software, but that you can think in maps, which was the point of the projects all along.
Related Guides
Readers working through this topic usually need its closest companions too. These GIS and open map data guides cover the neighboring ground:
- What Is GIS Software? The Six Categories, From Desktop GIS to Spatial Databases: GIS software is any software that stores, analyzes, or presents geographic data, and it comes in six working categories: desktop GIS like QGIS and...
- How to Use OpenStreetMap in Python: OSMnx, Overpass, and Nominatim With Real Code: Python is where OpenStreetMap stops being a map you look at and becomes data you compute with.
- How to Use OpenStreetMap Offline: Apps, Extracts, and Field Editing Without a Signal: OpenStreetMap may be the most offline friendly map data on Earth, because the whole database can live on your phone.
Frequently Asked Questions
What software do I need for these projects?
QGIS, which is free, professional grade, and runs on Windows, Mac, and Linux. Every project here is specified for it: layers, joins, buffers, layouts, and exports are all core QGIS operations. No paid software, subscription, or programming is required for any of the six.
Where do I get the data for beginner GIS projects?
OpenStreetMap exports for streets, buildings, places, and cafes; your city or national open data portal for boundaries and official layers; your statistics office for census tables; public elevation models for terrain. All six projects run entirely on free data, and each spec names its source.
How long does each project take?
Project 1 takes a long afternoon. Projects 2 and 3 take a weekend each, mostly in the join and the data cleaning. Project 4 takes a day once the elevation data behaves. Projects 5 and 6 take a full weekend each. Finishing all six at a steady pace is a season of evenings, which matches the stage four estimate in the learn GIS plan.
Which project should a total beginner do first?
Project 1, the neighborhood map, without skipping. It teaches layers, styling, labeling, and layout with data you can verify from your window, and every later project reuses those skills. The choropleth (project 2) is the correct second, because its join is the gateway skill to all real analysis.
Do these projects help me get a GIS job?
They build exactly the evidence GIS hiring asks for: finished maps with named data, a stated method, and a number the analysis earned. Project 6 in particular mirrors real municipal analysis work. A portfolio of the six exports, with a paragraph each on the question and the method, is a stronger application asset than most certificates.
What if I get stuck on the data?
You will, and it is the job, not a detour. The three classic stalls are mismatched coordinate systems (layers will not align), mismatched join codes (the statistics will not attach), and missing values (the map shades a district blank). Each has a standard cure, and the GIS forums are full of working analysts who answer exactly these questions daily, because everyone before you hit the same three walls.
Photo credits: Kampus Production (Pexels); Lukas Blazek (Pexels). Photos are served from this site; follow the credit to the library page for the original.