Tillotson Spatial Systems Start a Project

Software + Automation

Less busywork.
More useful answers.

Clean a spreadsheet. See what a storm could affect. Build a briefing. Watch the work happen below—or try it yourself.

01 / GIS + everyday data cleanup

A messy spreadsheet. A usable map.

Standardize names, remove duplicates, and flag locations that need a human check.

Facilities.csv12 original rows
FacilityCategoryCheck
From rows to placesFictional community
Valid locationUncertain locations stay off the map
  1. Read rows
  2. Standardize
  3. Remove duplicates
  4. Map & flag

The result: 8 mapped facilities. Two duplicates removed; two locations need review.

Which rows need review?

    Missing or invalid coordinates are flagged, not guessed. All names and locations in these demos are invented.

    02 / Weather + emergency management

    Which places fall inside the storm area?

    Move the sample storm. Watch the map and facility list change together.

    Simulated scenario · not live weather
    Sample storm area Facility inside area
    Illustrative map of Prairie Junction, a fictional community. Counts describe locations inside the shape, not predicted damage or official warnings.

    03 / Reporting + office automation

    From scattered information to a briefing.

    Choose a sample scenario. Get a map, a facility list, and a plain-language summary in one document.

    Your inputs

    Facility spreadsheetCleaned locations from demo 01

    Sample storm areaThe same analysis as demo 02

    Report templateA consistent format for every run

    A complete sample is ready to read.

    Download opens as a standalone HTML report. Choose “Save as PDF” in your browser’s print dialog for a PDF.

    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.

    More Technical Work

    Established tools. Completed work.

    Explore land-cover analysis with public data and a completed open-source GIS modernization. These examples show how custom tools turn data into useful reports and keep established workflows working in current software.

    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.
    • Summarizes transitions between land-cover classes as percentages.
    Completed GIS Model Modernization ArcMap + Python 2 deprecated ArcPy calls manual install notes to ArcGIS Pro + Python 3 updated imports + errors documented toolbox package

    Completed Python + ArcGIS Pro Port

    Open-source SPreAD-GIS modernization

    Modernized the open-source SPreAD-GIS environmental sound-propagation model from ArcMap and Python 2.7 to ArcGIS Pro and Python 3 while preserving its GPL licensing and established model workflow.

    • Replaced deprecated ArcPy functions and updated environment handling.
    • Packaged the toolbox, source code, architecture notes, and installation documentation.
    • Tested the port in ArcGIS Pro 3.2 and 3.4.3 on Windows 10.

    Project Process

    From a recurring task to a tool your team can use.

    Start with the work you need to complete, the data you have, and the result you need. The project can then be scoped around your software, staff, and reporting requirements.

    01

    Define

    Review the current steps, inputs, and outputs to agree on what the tool needs to do.

    02

    Build

    Develop a script, GIS tool, or reporting workflow that fits how your team works.

    03

    Validate

    Check results against agreed examples and test how the tool handles incomplete or unexpected data.

    04

    Hand Off

    Provide setup instructions, usage notes, and a walkthrough so your team can run the workflow again.

    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