Tillotson Spatial Systems Start a Project

Software + Automation

Turn repeat work into reliable tools.

Many location-based problems are not solved by a single map. They need repeatable data processing, clear reporting, quality checks, and tools that help people do the same task correctly every time.

View Examples Discuss a Tool
Remote sensing land-cover time-series maps
Example remote-sensing workflow output: multi-year land-cover maps generated from a repeatable analysis script.

What This Looks Like

Custom code should make the work easier to trust.

The goal is not to impress people with code. The goal is to reduce manual effort, make results easier to repeat, and give decision makers outputs they can understand without becoming GIS or programming experts.

Python + ArcPy ArcGIS Pro tools, batch processing, geoprocessing, and data cleanup.
R + Remote Sensing Land-cover analysis, raster summaries, reproducible charts, and reports.
C# + Pro SDK Desktop GIS add-ins and workflow tools for professional map users.

Ways to Use Code

Practical software offerings for spatial work.

These can be scoped as a small script, a polished internal tool, a repeatable report, or a modernization project for an older workflow.

Automation

Workflow Scripting

Automate repetitive data preparation, GIS processing, map exports, file organization, QA checks, and report generation.

Useful for

  • Monthly or weekly reporting.
  • Batch map production.
  • Cleaning and joining messy spatial data.

GIS Tools

ArcGIS Pro Tooling

Build script tools, toolboxes, and add-in style workflows that fit into how GIS teams already work.

Useful for

  • Repeatable analysis workflows.
  • Staff-friendly buttons instead of manual steps.
  • Standardizing outputs across users.

Modernization

Legacy GIS Code Updates

Move older ArcMap, Python 2, or fragile desktop workflows toward ArcGIS Pro, Python 3, clearer packaging, and better documentation.

Useful for

  • Old tools that still matter.
  • Scripts only one person understands.
  • Specialized models that need a modern home.

Dashboards

Reports + Decision Tools

Turn analysis results into charts, webmaps, simple dashboards, and PDF-ready visuals that support decisions.

Useful for

  • Public-facing summaries.
  • Internal review dashboards.
  • Grant, planning, and operations support.

Example Demos

Safe public examples, real technical substance.

Sensitive project details do not need to be exposed to show technical ability. A better public approach is to demonstrate the same pattern with public, synthetic, or simplified data.

Land-cover class area trend chart

Remote Sensing + R

Land-cover time-series reporting

A repeatable raster workflow classified NLCD imagery across multiple years, summarized land-cover area, and produced charts that make long-term landscape change easier to review.

Land-cover transition percentage chart

Change Detection

Before-and-after transition analysis

Instead of only asking what changed overall, the workflow compared earlier and later land-cover classes to show which categories converted into other categories.

  • Useful for planning, development pressure, and environmental review.
  • Can be repeated for a county, watershed, property, or project area.
  • Can be rebuilt with cleaner branding for a public demo.
Legacy GIS Tool Modernization ArcMap + Python 2 deprecated ArcPy calls manual install notes to ArcGIS Pro + Python 3 updated imports + errors documented toolbox package

Python + ArcGIS Pro

SPreAD-GIS modernization pattern

The original SPreAD-GIS scripts were built for older ArcGIS and Python environments. A modernized version can preserve the model's purpose while updating syntax, imports, tool packaging, and run behavior for ArcGIS Pro.

  • Port Python 2 era code toward Python 3 conventions.
  • Replace deprecated GIS patterns where ArcGIS Pro requires it.
  • Keep open-source license notices and documentation intact.

Demo Strategy

How to show coding work without exposing private projects.

This is the professional sweet spot: show enough to build trust, but keep source data, client details, and sensitive workflows protected.

01

Recreate

Build a small version of the workflow using public or synthetic data.

02

Record

Capture a short before-and-after clip: manual process, automated result.

03

Explain

Use plain language to describe the problem, the tool, and the time saved.

04

Protect

Keep source data, client names, private systems, and sensitive code out of public examples.

Have a Repetitive Task?

It may be a good candidate for automation.

Send the task, the files involved, and what the final output should look like. Even a messy manual workflow can often become a cleaner tool.

Start a Software Project