PATCO Speedline (Camden–Lindenwold), as a ladder of facts
The rung you asked for is the primary object. Everything above it is inherited context; everything below is what it contains. Empty rungs are shown, never hidden.
the rung you asked forinherited context (above) — show all to openwhat it contains (below) — a way ina rung with no facts loaded yet
The wider region every place here sits inside.Planning areas mapped443show all ▾
Regional planning centers31
Land-use polygons91,275
Roadway segments · AADT stations20,471 · 1,006
Flood (NFHL) · wetlands features24,696 · 42,305
Aerial imagery vintages13
Where this comes from
▪1DVRPC, NJ Office for Planning Advocacy, NJDOT, NJDEP, NJOIT-OGIS · as of 2026-09-14 · license public / per-source; see footer
Countycorridor spanThe county — the group of towns a place belongs to.Counties the corridor runs throughCamdenshow all ▾
Corridor placementregional rung — below county, above municipality
Where this comes from
▪1ALMANAC derived — parcels within the corridor buffer of the spine (NJDOT roadway network + published transit GTFS shapes) · as of 2026-09-14 · license derived; underlying: NJDOT roadway (as-is) + published transit GTFS
A major road or rail line and the properties along it.
CorridorPATCO Speedline (Camden–Lindenwold)
Mode · subtyperail · Passenger rail (GTFS shapes)
Parcels within 400 m (region-wide)14,403
Spine segments237
Sales recorded, 2025860 · median $327,000
Usable market sales, 2025270
Construction permits, 20251,446
Where this comes from
▪1PATCO GTFS (Port Authority Transit Corporation / DRPA) · as of GTFS feed_version 17 (start 20260807) · license PATCO GTFS published for public developer use (ridepatco.org/developers); no explicit reuse license stated on the feed; provided as-is
Municipalitymunicipalities touched
The town or township that governs the place.
Where this comes from
▪1ALMANAC derived — parcels within the corridor buffer of the spine (NJDOT roadway network + published transit GTFS shapes) · as of 2026-09-14 · license derived; underlying: NJDOT roadway (as-is) + published transit GTFS
Neighborhoodneighborhoods touched
A named part of a town, finer than the town itself.
Where this comes from
▪1ALMANAC derived — parcels within the corridor buffer of the spine (NJDOT roadway network + published transit GTFS shapes) · as of 2026-09-14 · license derived; underlying: NJDOT roadway (as-is) + published transit GTFS
Blockblocks touched
A tax block — a small group of neighboring properties.
Where this comes from
▪1ALMANAC derived — parcels within the corridor buffer of the spine (NJDOT roadway network + published transit GTFS shapes) · as of 2026-09-14 · license derived; underlying: NJDOT roadway (as-is) + published transit GTFS
Parcelparcels within 400 m
A single property — one lot at one address.
Where this comes from
▪1ALMANAC derived — parcels within the corridor buffer of the spine (NJDOT roadway network + published transit GTFS shapes) · as of 2026-09-14 · license derived; underlying: NJDOT roadway (as-is) + published transit GTFS
One composer, any rung. A dossier is not written per property — it is a query that starts at a key and walks up the ladder, each level a module of facts with its own source. A town page and a parcel page are the same composer with a different starting rung.
On the map
Our own basemap — municipal boundaries (NJGIN) and the roadway network (NJDOT), drawn in ink from one tile archive over the pmtiles protocol. No vendor tiles; no network beyond the archive.
This is a rail corridor. No rail line geometry is a separate layer in the tile archive, so the spine is not drawn on the map; the roadway network is shown for context. The corridor's parcels are counted in the ladder above.