Map Regression 101: How to Find “Lost” Places Using Historic Maps

Cities don’t vanish—they get renamed, rerouted, or quietly paved over. Map regression is a simple way to prove what changed, where, and (often) why.

What Is Map Regression?

Map regression compares two or more maps/aerials from different dates to track how a place evolved: streets realigned, creeks culverted, blocks erased, districts rebranded. You anchor an older map over today’s view, line up fixed reference points, and read the mismatches as evidence.

Why it matters (and how this fits my “Lostness” framework)

  • Catastrophic burial: abrupt, sealed layers and straight edges over organic street grids

  • Environmental shift: waterways moved or covered; shorelines advance/retreat

  • Economic rerouting: rail spurs vanish; frontage density thins on former main drags

This method turns the “Five Ways Cities Become Lost” explainer into practice—and it tees up ethical field notes and casefiles.


What You’ll Need (all free)

  • Google Earth Pro (desktop)

  • Historic map/aerial from a library, archive, or open collection (e.g., Sanborn fire insurance maps, USGS topos, state archives)

  • Optional: a historic aerial photo close in date to your map for triangulation

Time: plan ~45–60 minutes for your first pass on one block.


Step-by-Step Tutorial

1) Pick a block you know

Choose a small area (1–3 city blocks) so changes are readable and your reference points are easy to identify.

Pro tip: Corners of long-standing buildings, church spires, monuments, or bridgeheads make great anchors.

2) Find a historic map

Grab the closest-year map you can find (same decade is ideal). Export a JPG/PNG (or screenshot) at decent resolution. Note the year, sheet #, and source for citation.

What to look for on the map:

  • Street names and alignments

  • Lot lines and building footprints

  • Rail sidings, depots, or wharves

  • Water features (creeks, canals, shorelines)

  • Industrial labels (mills, foundries) and public buildings

3) Overlay in Google Earth Pro

  1. Open Google Earth Pro.

  2. Go to Add → Image Overlay and select your historic image.

  3. Set opacity ~50–70% so you can see both layers.

  4. Anchor 3–5 fixed points (corners that exist in both eras). Adjust scale/rotation until lines up.

Alignment sanity checks:

  • Do two perpendicular streets match in both layers?

  • Do long blocks align at both ends?

  • If a creek existed, can you see its culverted path in today’s parcel shapes or tree lines?

4) Trace “features of change”

Toggle opacity and jot down each mismatch:

  • Renamed streets: Same alignment, new label

  • Realigned streets: Curve straightened or jog removed

  • Erased lots/blocks: Superblocks, parking, stadiums, or campuses replacing fine-grained parcels

  • Filled/covered waterways: Former creeks now in storm drains (often hinted by curvy property lines)

  • Lost rails/industry: Sidings and depots gone; land use flips to residential or mixed-use

Log each item in your Change Log CSV with: feature, map year, basemap year, type of change, evidence, likely cause (use the Lostness patterns), and source.

5) Export a before/after visual

  • Screenshot A: Historic overlay at ~70% opacity with labels

  • Screenshot B: Modern basemap only, same viewpoint

  • Optional: Place them side-by-side with callouts (“creek culverted,” “block consolidated,” “street renamed”)


How to Read the Clues

  • Catastrophic burial: Look for abrupt edge lines, uniform fill areas, or streets that stop mid-block where rubble or infill likely standardized surfaces.

  • Environmental shift: Wiggle-to-straight transitions in streams, levee construction, new shorelines, marshlands converted to gridded parcels.

  • Economic rerouting: Disappearance of rail infrastructure, thinning storefront density, bypass highways that strangle main-street traffic.

  • Memory & naming: If a saint, creek, or barrio name persists in businesses or parks—but not on official maps—you may be seeing place-name memory outlasting the fabric.


Mini Case Study Prompt (plug in your city)

Use this template to demo your findings:

  • Site: [Neighborhood/Block, City, State]

  • Historic base: [Map series + year + sheet]

  • Modern base: Google satellite/basemap (year)

  • Three key changes:

  1. [Example: “North–south lane removed; block consolidated for parking (Economic rerouting)”]

  2. [Example: “Creek culverted; property lines still curve (Environmental shift)”]

  3. [Example: “‘Mill St.’ renamed to ‘Commerce Ave.’ post-redevelopment (Memory/branding)”]

  • Likely drivers: [One-line synthesis]

  • Open questions: [What you’d ground-truth or ask locals]

Ethics & Good Practice

  • Cite your sources (archive, collection, sheet numbers).

  • Avoid precise coordinates for sensitive or sacred sites.

  • Invite local knowledge—descendant communities, longtime residents, and historians.

  • Credit corrections publicly when readers contribute.

Troubleshooting

  • Can’t get the overlay to line up? Try more anchor points farther apart; verify your historic map wasn’t distorted by scanning.

  • Street names don’t match? Confirm city renamings; use building footprints and block shapes instead of labels.

  • Nothing “changed”? Zoom out one level or switch eras; pick a location known for a highway, flood control, urban renewal, or rail decline.


Keep Exploring

  • Pair this post with Five Ways Cities Become ‘Lost’” for the theory backdrop.

  • See From Census Maps to Google Maps to understand why the data exists and how to find it.

  • Coming soon: Phone-First Photogrammetry (build a 3D model with your smartphone) and Toponymy as Evidence (how place-names remember).



Previous
Previous

Toponymy as Evidence: How Place-Names Preserve Lost Landscapes

Next
Next

From Census Maps to Google Maps: A Quick History of GIS