Back to projects

Project case study

Municipal Infrastructure Planning

Exploring the relationship between location, scheduling, and budgets. Start with a synthetic illustration, then read the implementation decisions and verification limits.

Synthetic illustrative demonstration

Move an asset. Reconcile the plan.

All assets and USD estimates are invented; this is not an actual app screenshot or City data. Changes stay in this demo.

Totals update as soon as you select a year.

Selected estimate: $120,000

Annual budget totals

2027
$200,000
2028
$160,000
2029
$90,000
Plan total · unchanged
$450,000

Moving an asset subtracts its estimate from one year and adds it to another.

Choose an asset and change its year to rebalance the annual totals.

Case study · GIS & planning workflows

Municipal Infrastructure Planning

GIS planning tools for pavement, sidewalks, and ADA ramps

Two browser-based workspaces for exploring multi-year infrastructure scenarios, coordinating related work, and reviewing the effects of planning changes.

Purpose
Infrastructure planning connects location, timing, treatment, and funding. Moving one task can affect its follow-up work and the shape of a multi-year program. These tools bring spatial selection, scheduling, review flags, and budget summaries into one editable workspace.
Contribution
I defined the domain requirements and planning workflows, then iterated on the applications through AI-assisted development. The work translates municipal planning rules into configurable interactions, reversible edits, and portable project files.
Availability
This case study describes the implementation and a targeted QA pass. The application bundles and underlying city datasets are not distributed here. Planning scenarios require professional review and do not represent an adopted municipal plan.

Pavement Plan Editor

Coordinate treatment schedules and linked follow-up work across a configurable planning horizon. Spatial selection, custom treatments, annual and district budget summaries, and GIS exports connect edits to reviewable outputs.

Sidewalk and ADA Planner

Coordinate sidewalk and ramp scheduling while retaining separate program budgets. Explicit asset associations, duplicate and overlap checks, review flags, and shared undo/redo support changes across the two programs.

  1. Select assets

  2. Adjust schedules

  3. Review dependencies and budgets

  4. Save or export a scenario

Illustrative workflow only. No city data or application screenshot.

Engineering decisions

Reversible planning changes
Transactional stores preserve undo/redo history and reject invalid changes atomically. This gives scenario editing a clear recovery path when a proposed adjustment does not fit the plan.
Explicit dependencies and review flags
Linked follow-up treatments and asset associations make sequencing visible. Missing or conflicting relationships can be surfaced for review. Targeted testing also identified a deletion edge case that still needs correction.
Local projects and GIS handoff
Standalone HTML/CSS/JavaScript, canvas mapping, coordinate transformations, and portable JSON projects support a local planning workflow. CSV, GeoJSON, and shapefile export code paths support GIS handoff. Live basemaps and address search use external services.
Separate accounting and planning judgment
Budget summaries expose the effects of scheduling choices. The tools retain program and district boundaries; they do not authorize funding transfers, establish construction readiness, or certify accessibility compliance.

Targeted verification

On October 5, 2026, 49 targeted source/core checks passed across the two applications. The pass identified two reproducible defects and an imported-cost validation question. Browser acceptance testing remains pending.

Passing checks covered areas including year assignment, undo/redo, invalid-change rejection, budget reconciliation, linked follow-ups, project serialization, geometry selection, and export helpers. Coverage differs by application.

Open findings

  • Pavement: deleting a crack-seal parent can leave a linked microsurfacing task behind. The review checker can flag the orphaned relationship.
  • Sidewalk and ADA: the first application of an unchanged year can create a false edit-history entry. Tested costs and geometry remained unchanged.
  • Imported pavement costs: externally supplied estimates are accepted without automatic reconciliation to configured rates. The intended override policy needs a product decision.

These results verify selected source and core behavior. Rendered maps, click-driven workflows, browser persistence, file dialogs, downloads, accessibility, and live services still need browser validation. The findings have not been represented as fixed.

Next validation priorities are correcting the two reproducible defects, defining imported-cost handling, and running browser acceptance tests for complete editing and export workflows.

  • JavaScript
  • HTML / CSS
  • Canvas mapping
  • proj4
  • fflate
  • GeoJSON
  • Shapefile
  • JSON project files