Geospatial Analysis

A clear location question, a sound toolkit and coordinate rules, geocoded and joined data, routines that keep layers clean and current, spatial skills, catchment and site decisions, and specialist models from Huff to routing.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Then open the Marketplace in the app, search for Geospatial Analysis, and click Install. It goes into your own files, and works offline from then on.

What it installs.

1

Pillar

1

Area

50

Projects

205

Starter tasks

📊 Data & Analytics

Geospatial Analysis

Analysing location data with maps, regions and distances to answer questions about catchments, routes, site selection and coverage.

  1. Writing the location question before opening a map
  2. Choosing a GIS desktop and spatial code toolkit
  3. Coordinate reference system rules for every project
  4. Geocoding addresses with a measured match rate
  5. Boundary layers for the regions you report on
  6. Spatial data source register
  7. First reference map of sites and customers
  8. Assigning points to regions with a spatial join
  9. Straight-line or travel-time distance decision
  10. Spatial database with indexed geometry tables
  11. Monthly geocoding refresh and failed match queue
  12. Dated snapshots of site and customer locations
  13. Weekly geometry and coordinate quality checks
  14. Catchment and coverage dashboard refresh
  15. House map style guide and layout template
  16. Location data licence and attribution log
  17. Quarterly coverage gap review
  18. Shared spatial query and snippet library
  19. Location privacy rules for maps and exports
  20. Projections and distortion through hands-on exercises
  21. Spatial SQL fundamentals
  22. Python geospatial stack in practice
  23. Honest choropleth maps and the areal unit problem
  24. Spatial autocorrelation and hot spot statistics
  25. Raster data basics with elevation and land cover
  26. Road network analysis and isochrones
  27. Kernel density and spatial interpolation
  28. Hexagon grids and H3 indexing for aggregation
  29. Drive-time catchments for existing sites
  30. Site selection scoring for a new location
  31. Choosing a geocoding service on accuracy and terms
  32. Balanced sales or service territory design
  33. Population coverage within a travel time of services
  34. Cannibalisation check between nearby sites
  35. Moving from shapefiles to GeoPackage and GeoParquet
  36. New site opening or closure impact read
  37. Map pack for a planning or funding application
  38. Field data collection day with a mobile GIS app
  39. Conference poster or paper map figures
  40. Board presentation of a location expansion plan
  41. Reproducible spatial methods for a thesis chapter
  42. Taking over an inherited GIS folder
  43. Location analysis without dedicated GIS software
  44. Small-area statistics for social and health research
  45. One-off location study for a client
  46. Geographically weighted regression for varying effects
  47. Gravity and Huff models for market share by location
  48. Multi-stop route optimisation study
  49. Satellite imagery change detection for land use
  50. Mobility and footfall data validation

Where it starts.

Each project arrives with its purpose, milestones and first tasks written out. Here is how the first three read.

Writing the location question before opening a map

Before any layer is loaded, write down what the map or analysis has to decide: whether to open a site in the north of the city, which postcodes a service fails to reach, or how far patients travel to a clinic. Spatial work drifts into pretty maps that answer nothing when the question is vague, and a written question fixes the unit of analysis, the geography and the distance measure up front.

First tasks

  • Ask the requester what decision the map or analysis should change
  • Write the location question and its decision in one sentence each
  • Name the unit of analysis and the geography the answer needs
  • Get the requester to confirm the question by email

Choosing a GIS desktop and spatial code toolkit

Most location work needs two tools: a desktop GIS for looking at and checking data, such as QGIS or a commercial equivalent, and a code or SQL route for repeatable analysis, such as Python with GeoPandas, R with sf, or a database with spatial functions. Choosing them deliberately, against your data volumes, colleagues' skills and licence budget, saves months of exporting shapefiles between tools nobody shares.

First tasks

  • List the data sizes, colleagues and budget your tools must cope with
  • Score two desktop GIS options and two code routes on the same criteria
  • Install the chosen tools and open a sample of your own data in both
  • Update the GIS and spatial libraries to their current stable release @recurring(quarterly)

Coordinate reference system rules for every project

Coordinates mean nothing without a reference system, and mixing latitude and longitude in degrees with a projected grid in metres is behind most wrong distances and areas. Setting one storage system, usually WGS84 for exchange, and one projected system for measuring in your region, then writing the rule down, stops buffers drawn in degrees and areas that are off by a factor of thousands.

First tasks

  • Look up the recommended projected reference system for your country or region
  • Write the storage and measuring EPSG codes on a one-page rule sheet
  • Check and record the reference system of every layer you hold
  • Measure one known distance in degrees and in metres to show the error

Make it yours.

Install Geospatial Analysis, then tell Aurum the date you're aiming for. It checks whether the plan fits the weeks you actually have.

Free · Mac (Apple silicon) and Windows · v1.0.5 · Other platforms

Blueprints are general information to help you organise your own work. They are not medical, financial, legal or other professional advice. See the Terms.