Objective. Students will independently complete a full spatial analysis workflow—data acquisition, cleaning, spatial operations, visualization, and interpretation—on a self-selected public dataset and present findings to the class.
This lesson, its worked examples and its practice questions has not yet been verified by an industry-certified professional or by a certification or approval body. It is a study draft and may contain errors. Do not use it as instructions for work on a job site or on live equipment. Always follow your instructor, your supervising professional, and current official references and regulations.
VoTechWorks program approval and accreditation are still in progress. Credentials are issued only by the certifying bodies named in each program, after their own exams.
This lab brings together every skill you have built in the GIS and Spatial Data Analysis course. You will plan, execute, and communicate a complete spatial analysis—from raw data to a polished map and a clear, defensible finding. Professional GIS analysts and data scientists follow this same sequence on the job, so mastering it now prepares you directly for the workplace and for credential exams from Google, Microsoft, IBM, and CompTIA.
Spatial analysis is rarely a single operation. Real projects require you to locate trustworthy data, assess its quality, apply the right geometric and statistical operations, visualize results clearly, and communicate meaning to an audience that may not be technical. Errors at any stage can invalidate your conclusions. A structured workflow—with documentation at every step—lets you catch mistakes, reproduce your results, and defend your methods when questioned.
Start with a clearly stated analytical question. A good question is specific, spatially grounded, and answerable with publicly available data. Examples include: Which census tracts in my county lack a full-service grocery store within one mile? or How evenly is park acreage distributed across neighborhoods by income quartile?
Publicly available spatial datasets suitable for this project include the US Census Bureau (TIGER/Line shapefiles, American Community Survey tables), the USGS National Map, CDC PLACES (county- and census-tract-level health data), and city or county open-data portals. Always record the source URL, the date you downloaded the file, the coordinate reference system (CRS) stated in the metadata, and any terms of use. Crediting your data sources is a professional and ethical obligation.
Data safety note: When downloading files from any portal, verify the site's HTTPS certificate before entering credentials or downloading executable content. Never run scripts or plugins from untrusted sources inside QGIS or Jupyter. If you work on a shared lab computer, log out of any cloud account when your session ends and do not store dataset credentials in plain-text files.
Raw spatial data almost always requires cleaning. Common issues include missing attribute values, features with null or invalid geometries, mismatched CRS across layers, and inconsistent field names or data types. In QGIS, use Vector → Geometry Tools → Fix Geometries to repair invalid polygons. In Python (GeoPandas), `gdf.is_valid` flags problem rows, and `gdf.geometry = gdf.geometry.buffer(0)` is a standard repair idiom.
Reproject all layers to the same projected CRS before running any distance or area calculations. Using a geographic CRS (latitude/longitude degrees) for area calculations will produce incorrect results. For continental US work, NAD83 / UTM zone projections or a State Plane system appropriate to your study area are common professional choices.
Document every cleaning decision in your lab log: what you found, why you changed it, and what tool or code you used. An honest lab log—including errors you made and how you fixed them—demonstrates the professional integrity that employers and credentialing bodies expect.
Choose operations that directly answer your question. Common operations in this course include:
Always ask: Is this operation appropriate for my question? A buffer answers proximity questions; a spatial join answers attribute-transfer questions. Applying the wrong operation produces a result that looks plausible but is analytically wrong.
A final map must communicate your finding at a glance. Every finished map needs a title, a legend, a north arrow, a scale bar, and a data source citation. Choose a color scheme appropriate to your data type: sequential palettes for ordered data (e.g., income levels), diverging palettes for data with a meaningful midpoint (e.g., above/below median), and qualitative palettes for categorical data. ColorBrewer palettes (colorbrewer2.org) are a professional standard.
For web output, Folium in Python or ArcGIS Online allows interactive maps with pop-up attribute information, which is especially effective for audiences unfamiliar with GIS.
Your presentation must state the analytical question, explain which spatial operations you performed and why, and deliver the key finding in one sentence. "Census tracts in the northern district show a 40% lower park-area-per-resident ratio than the city median, concentrated in tracts where median household income falls below the city average." is a defensible, specific finding. "There are inequalities in park access" is too vague to act on.
Take classmate questions seriously—they simulate the peer review and stakeholder questioning you will face in professional settings. Complete your self-assessment rubric honestly immediately after presenting.
This capstone maps directly to competencies tested across your target credentials: data preparation and transformation (Google Data Analytics, IBM Data Science Professional, CompTIA Data+), data visualization and reporting (Microsoft PL-300, CompTIA Data+), and reproducible analytical workflow documentation (IBM Data Science Professional, CompTIA Data+). A portfolio-ready project completed here can be shared with employers as evidence of job-ready skills.
Answer each question, then check it. Nothing is recorded; this is your own practice.
A free tech program — complimentary, as our commitment to get America working. Help us build VoTechWorks. Tell us what works, what doesn’t, and what you want to learn.