PHILADELPHIA IN FLUX

A GPS-tagged photographic survey of the city through its transit arteries.

The transit map is the skeleton.
The walk is the method.
The archive is the artwork.

---

1. INTRODUCTION

Philadelphia in Flux is a long-term photographic survey of Philadelphia, organized around the city’s transit system.

It is not a portfolio.
It is not a gallery.
It is a structured, GPS-tagged archive that grows one station at a time.

The project replaces random wandering with a repeatable protocol: move through the city by transit, stop at each node, photograph for a fixed hour, preserve the coordinates, and slowly light up the entire map.

Dante Sisofo is the blueprint photographer. The first phase is a single-photographer proof of concept. The protocol is designed so that, in time, other photographers can contribute to the same living archive without changing the standard.

ONE SENTENCE
Move through the city by transit, photograph each stop for one hour, preserve the coordinates, and build an expanding visual map of Philadelphia.

---

2. PROJECT PHILOSOPHY

The city is always moving.

The light changes.
The crowd changes.
The station changes.
The photographer changes.

You cannot photograph the same station twice.

Philadelphia in Flux inherits the core FLUX principle and applies it to a fixed geography. The river is the transit map. The seeing is the survey.

2.1 Structure Over Randomness

A photographer with no constraint has infinite options and makes infinite compromises. A photographer with a constraint has one job: one station, one hour, return with the survey.

The transit map supplies the constraint:

• The map decides where the body goes.
• The hour decides how long the eye works.
• The walk decides what enters the archive.

When the route is fixed, attention is freed.

2.2 Coverage, Not Perfection

The goal is not the perfect frame. The goal is the complete map.

• Coverage — every station, eventually.
• Rhythm — the same unit of work, repeated.
• Consistency — one visual language across years.

The goal is not perfection. The goal is coverage, rhythm, and consistency.

2.3 Why One Hour Works

One hour is long enough to see.
One hour is short enough to repeat.

A unit that can be repeated is a unit that can be completed. A survey that demands a perfect day will never finish. A survey built on one repeatable hour will cover the city.

---

3. CORE METAPHOR

The city is an organism. The project documents it as one.

Element	Body
City Hall	The heart
Subway lines	The arteries
Stations	The organs
Streets	The veins
People	The cells
Photographs	Traces of life moving through the organism

The metaphor is not decoration. It sets the order of the work:

• Begin at the heart — City Hall.
• Move outward along the arteries — the subway lines.
• Document each organ — one station at a time.
• Follow the veins — the streets within walking distance.
• Record the cells — the people moving through.

Each photograph is a trace of circulation: a record of life passing through one node of the body at one moment in time.

---

4. PROJECT OBJECTIVES

The project has a small number of clear objectives:

• Visit every major subway station in Philadelphia.
• Photograph the area around each station within a walkable radius.
• GPS-tag every photograph at the moment of capture.
• Build an expanding, interactive visual map of the city.
• Produce a chronological, searchable, publicly accessible archive.
• Establish a protocol that other photographers can later execute without instruction.

4.1 Phase 1 — The Subway Spine

The survey begins with the spine of the system:

1. Market–Frankford Line
2. Broad Street Line
3. Broad–Ridge Spur
4. City Hall — the central heart

SCOPE DISCIPLINE
The point is not to solve every detail immediately. The point is to create a repeatable field protocol and begin walking.

---

5. SURVEY METHODOLOGY

5.1 One Stop / One Hour / One Survey

One transit stop.
One hour.
One photographic survey.

The unit of the project is the field walk: one station, photographed for one continuous hour, within a walkable radius of the station entrance.

5.2 The Survey Sequence

1. Arrive at the station.
2. Start GPS tracking and confirm it is active.
3. Photograph continuously for one hour.
4. Remain within a walkable radius of the station.
5. Make photographs intuitively — respond to light, gesture, form, and movement.
6. End the walk at the hour.
7. Export the photographs.
8. Preserve the GPS metadata.
9. Add the walk to the archive.
10. Update the project map.

5.3 The Walkable Radius

A walkable radius is the area reachable on foot within roughly five minutes of the station entrance — typically two to three blocks in each direction.

• Stay inside the radius for the full hour.
• Do not chase a subject out of the zone.
• Circle, double back, and re-see the same corners. Depth over distance.

The station is the anchor. The hour belongs to its immediate surroundings.

---

6. FIELD ASSIGNMENT PROTOCOL

Each field walk is a FLUX field assignment, identified by a permanent assignment ID.

Assignment ID:  PIF_NNN_STATION-SLUG_YYYY-MM-DD
Example:        PIF_001_CITY-HALL_2026-05-29

6.1 Before Leaving

• Charge the Ricoh GR.
• Clear the SD card.
• Confirm JPEG settings — Small JPEG, High Contrast B&W.
• Confirm phone battery.
• Confirm the GPS tracking app is running.
• Bring water.
• Pick one station.
• Commit to one hour.

6.2 At the Station

• Photograph the station entrance.
• Photograph the surrounding streets.
• Photograph people and gesture.
• Photograph architecture, signs, shadows, and light.
• Walk instinctively.
• Do not overthink.

6.3 After One Hour

• Stop the GPS track.
• Save the route.
• Write a short field note:
• Station
• Date
• Time
• Weather
• Feeling
• Strongest observation

6.4 First Assignment — PIF_001

• Station: City Hall
• Duration: 60 minutes
• Rule: Photograph outward from the heart.
• Output: 36 selected photographs — one FLUX issue.

The selected output of a field walk is a canonical 36-frame FLUX issue. The walk fills the archive; the issue is the published record.

FIELD NOTE
GPS must be confirmed active before the walk begins. No exceptions. A walk without coordinates is not part of this archive.

---

7. GPS TRACKING STANDARDS

GPS is canonical truth. Coordinates are embedded in the JPEG at the moment of exposure — not added afterward. Every downstream output (captions, maps, station matching, statistics) depends on coordinates captured correctly in the field.

7.1 Ricoh GR World — On Camera

Menu → Wrench → Wireless Communication
  Wireless LAN:                         ON
  Smartphone Link with Store Location:  ON
  Pairing:                              Execute

7.2 Ricoh GR World — On iPhone

Settings → Privacy → Location Services → GR World
  Allow Location Access:  Always
  Precise Location:       ON

GR World → App Settings
  Background Location Transmission:  No Time Limit
  Transmission Frequency:            High

7.3 Confirm Before Every Walk

• Camera shows connected status.
• Satellite icon active in the viewfinder.
• Make one or two test frames and verify the GPS fields are populated in EXIF.
• Do not begin the walk until GPS is confirmed.

7.4 Standards

• Small JPEG only. No RAW.
• Coordinates are embedded at capture — never reconstructed in post.
• If GPS fails mid-walk, note the time gap. Do not fabricate coordinates.

WHY “NO TIME LIMIT”
The default background-location limit silently stops embedding GPS after a set period. It must be changed before the walk, or the second half of the survey loses its coordinates.

---

8. FILE STRUCTURE & ARCHIVAL STANDARDS

8.1 Principles

• Originals are never modified.
• Every processing step is stateless and re-runnable.
• Chronological order is determined by EXIF capture time.
• The full archive is reproducible from the originals plus the build scripts.

8.2 Fieldwork Folder

philadelphia-in-flux/
└── fieldwork/
    └── PIF_001_CITY-HALL_2026-05-29/
        ├── images/          # original JPEGs, unmodified
        ├── gps/             # exported GPS track (GPX / CSV)
        ├── manifest.json    # walk metadata
        └── notes.md         # field note

8.3 Naming Conventions

Assignment ID:  PIF_NNN_STATION-SLUG_YYYY-MM-DD
Photograph:     DANTE_YYYY-MM-DD_HH-MM-SS_R0000000.JPG
Station slug:   lowercase, hyphenated (city-hall, 30th-street, york-dauphin)

Assignment numbers, once assigned, are permanent. They are never reused and never reassigned.

The walk manifest template is in the Appendix.

---

9. WEBSITE ARCHITECTURE

The project publishes as a static website. No server-side computation, no database — HTML, CSS, JavaScript, JSON, and image files.

9.1 Main Page

/philly-in-flux/

Contains:

• Project statement
• Interactive map
• Progress statistics
• Station list
• Latest walks
• Link to the full archive

9.2 Homepage Sections

Hero

PHILADELPHIA IN FLUX
A GPS-tagged photographic survey of Philadelphia through its transit arteries.

Live Map — every station rendered by status color (see Station Completion System).

Progress — running counters:

• Stations Completed
• Field Walks
• Photographs Archived
• Project Started

Latest Walks — a chronological feed of completed assignments.

Station Index — a directory of stations, by line or alphabetical.

9.3 Station Page

/philly-in-flux/stations/{station-slug}/

Contains:

• Station name and line
• GPS location
• Visit count, first visit, latest visit
• Photographs
• GPS tracks
• Field notes

---

10. DATA MODEL

Three JSON files drive the static site. Each is generated from the fieldwork folders and is safe to regenerate at any time.

10.1 stations.json

[
  {
    "id": "city-hall",
    "name": "City Hall",
    "line": "BSL / MFL",
    "status": "completed",
    "visits": 1,
    "lat": 39.9526,
    "lon": -75.1635,
    "first_visit": "2026-05-29",
    "latest_visit": "2026-05-29"
  }
]

10.2 walks.json

[
  {
    "id": "PIF_001_CITY-HALL_2026-05-29",
    "station_id": "city-hall",
    "date": "2026-05-29",
    "duration_minutes": 60,
    "photo_count": 214,
    "selected_count": 36,
    "gps_track": "gps/PIF_001.gpx",
    "notes": "notes.md"
  }
]

10.3 photos.json

[
  {
    "id": "R0000001",
    "walk_id": "PIF_001_CITY-HALL_2026-05-29",
    "station_id": "city-hall",
    "filename": "DANTE_2026-05-29_09-14-22_R0000001.JPG",
    "timestamp": "2026-05-29T09:14:22",
    "lat": 39.9527,
    "lon": -75.1634
  }
]

---

11. AUTOMATION ROADMAP

11.1 The Pipeline

A single build run should:

1. Read the uploaded photos.
2. Extract EXIF data.
3. Extract GPS coordinates.
4. Match each photo to its nearest station.
5. Generate the walk page.
6. Update the station page.
7. Update the map.
8. Update the statistics.
9. Deploy.

Shoot → Upload → Archive updates itself.

11.2 Build Strategy

Version	Mode	Capability
V1	Manual	One project page, one map, one station list, one completed station
V2	Semi-automatic	Generate JSON from fieldwork folders
V3	Fully automatic	Drop folder into archive, run build script, deploy

Each version is shippable on its own. The project does not wait for V3 to exist.

---

12. STATION COMPLETION SYSTEM

Every station holds a state. The live map renders that state as color.

Color	State	Meaning
Gray	not_started	No walk recorded yet
Yellow	visited	Visited once, survey not complete
Black	completed	Full survey — one hour, 36 selected frames
Purple	revisited	Completed, then walked again later
Red	heart	City Hall — the center of the system

State transitions:

• not_started → visited — first walk logged at the station.
• visited → completed — a full survey plus 36 selected frames.
• completed → revisited — any later walk at a completed station.
• City Hall is always red.

Progress statistics are simply the count of stations in each state. The map lighting up from gray to black is the visible record of the survey’s growth.

---

13. FOUNDER PHASE

In the founder phase, only Dante contributes.

Purpose:

• Prove the concept.
• Build the workflow.
• Refine the protocol.
• Build the first archive.
• Establish the standard.

The founder phase ends when the protocol is stable enough that another photographer could execute a complete, conforming walk from this document alone.

---

14. CONTRIBUTOR PHASE

In time, the protocol opens. Other photographers contribute to the living archive.

The contributor rule is the same as the founder rule:

One stop.
One hour.
GPS on.
Photograph what life gives you.
Submit the sequence.

14.1 Submission Protocol

• Execute one station for one continuous hour, GPS confirmed.
• Select 36 frames.
• Submit the sequence with its manifest and GPS track.
• Each submission is reviewed before it joins the archive.
• Contributor walks share the protocol and visual language but occupy a separate namespace from the founder archive.

The protocol is shared. The seeing is not.

---

15. LONG-TERM VISION

This is not simply a photography project.

It is a visual census of Philadelphia.

Over years and decades, the archive becomes:

• Geographic
• Historical
• Documentary
• Searchable
• Publicly accessible

Every photograph becomes a coordinate in a larger structure. Every walk becomes part of the living memory of the city.

---

16. FIRST 90-DAY ACTION PLAN

The plan turns the protocol into motion. Three thirty-day blocks, each shipping something usable.

16.1 Days 1–30 — Spine & Proof

• Execute PIF_001 at City Hall — the first walk from the heart.
• Begin walking outward along the subway spine.
• Lock the field protocol and the GPS standard against real conditions.
• Build the V1 site: one project page, one map, one station list, one completed station.

16.2 Days 31–60 — Coverage & Semi-Automation

• Complete the first ten station surveys (below).
• Build V2: generate the JSON data model from fieldwork folders.
• Stand up station pages and the live-map color system.

16.3 Days 61–90 — Automation & Publication

• Extend coverage along the full Market–Frankford and Broad Street Lines.
• Build V3: drop-folder → build → deploy.
• Publish /philly-in-flux/ with live progress statistics and the latest-walks feed.

16.4 Recommended First Ten Assignments

#	Station	Phase
1	City Hall	Heart
2	30th Street	Spine
3	8th Street	Spine
4	Spring Garden	Spine
5	Girard	Spine
6	Berks	Spine
7	York–Dauphin	Spine
8	Huntingdon	Spine
9	Somerset	Spine
10	Frankford Transit Center	Spine

START PRINCIPLE
Do not wait for perfect infrastructure. The project begins with the first walk.

One station.
One hour.
One survey.
Philadelphia in Flux.

---

17. APPENDIX

17.1 Folder Structures

Project root:

philadelphia-in-flux/
├── fieldwork/                         # raw walks, one folder per assignment
│   └── PIF_NNN_STATION-SLUG_DATE/
│       ├── images/
│       ├── gps/
│       ├── manifest.json
│       └── notes.md
├── data/                              # generated data model
│   ├── stations.json
│   ├── walks.json
│   └── photos.json
└── site/                              # generated static website
    ├── index.html
    └── stations/

17.2 Manifest Template

{
  "project": "Philadelphia in Flux",
  "fieldwork_id": "PIF_001_CITY-HALL_2026-05-29",
  "station": "City Hall",
  "date": "2026-05-29",
  "duration_minutes": 60,
  "photographer": "Dante Sisofo",
  "gps_enabled": true,
  "status": "complete",
  "photo_count": 0,
  "selected_count": 0,
  "notes": ""
}

17.3 Example JSON

// stations.json — minimal record
[
  { "id": "city-hall", "name": "City Hall", "status": "not_started", "visits": 0 }
]

// walks.json — minimal record
[
  { "id": "PIF_001_CITY-HALL_2026-05-29", "station_id": "city-hall", "duration_minutes": 60 }
]

// photos.json — minimal record
[
  { "id": "R0000001", "station_id": "city-hall" }
]

17.4 Future Feature Ideas

• Visual embeddings and semantic search across the entire archive.
• Automatic reverse-geocoding of station areas into street addresses.
• A public contributor portal with a review queue.
• Per-line spine PDFs and printed station zines.
• A time-lapse animation of the map lighting up over months.
• Weather and temperature capture recorded per walk.
• Automatic cross-linking of walks whose GPS tracks overlap.

---

SEE ALSO

Document	Layer	Relationship
PROTOCOL	Layer 2 — Protocol	The base FLUX protocol this project runs inside
ARCHIVE	Layer 2 — Protocol	The digital archive structure the survey feeds
PROJECTS	Layer 3 — Field	The collaborative project framework
BROAD STREET IN FLUX	Layer 3 — Field	The founding GPS-mapped field project
MARKET STREET — DIGITAL MIRROR	Layer 3 — Field	The metadata-archaeology sibling project
FIELD ASSIGNMENTS	Layer 3 — Field	Constraint protocols that govern each walk

---

FLUX_PROJECT_v1.0 — flux.dantesisofo.com/wiki/philadelphia-in-flux/