Tool / v0.9

Corridor Atlas.

Select a freeway interval to bring its mapped crossing streets into the same study. Choose an active roadway for its ground profile and Drive preview, then report recorded conditions and source coverage.

No account · Private browser space · Reduced images only in cloud mode

Corridor Atlas on a public I-5 interval near downtown San Diego: a yellow selected freeway, orange mapped cross-street lines and the active-road chooser. I-5 and eight named Census street paths stay selected together; numbered handles follow the active road. The map does not establish pedestrian access or surveyed position.Corridor Atlas at 375 CSS pixels: the selected-road chooser fits above the toolbar and lists I-5 with automatically selected named Census crossing streets. All selected lines remain mapped; the active road supplies handles, profile and Drive. Mapped crossings do not verify pedestrian access.
Local Chromium previews captured October 25, 2026 at 1280 × 900 and 375 × 812 pixels: one public I-5 interval near downtown San Diego and eight named Census crossing-street paths selected together. The active-road chooser controls handles, profile and Drive. No private photographs or recorded field measurements are shown. Mapped crossings do not establish survey accuracy, legal right of way, grade connectivity or pedestrian access.

Select the roadway interface

Corridor Atlas supports early corridor studies in San Diego and Imperial counties, focused on California Department of Transportation right-of-way references, interchanges and crossing streets. Begin with the mapped source geometry, then keep photographs and material observations linked to their source.

Numbered endpoints. Select a measured mile on one continuous source piece. Move handle 1 or 2 in either direction, including past the other handle; each keeps its identity. Keep 1 mile moves the interval together within the available source piece. Optional snapping uses loaded city/community boundary intersections.

Live badges on each handle show which kind of postmile it is. Each kind has its own border style and legend entry, so the meaning never depends on colour alone. A Caltrans SHN record endpoint is a published postmile. ≈ PM is interpolated along the source piece, and only when the piece's postmile span agrees with its mapped length. Otherwise the badge says the span disagrees with the source geometry. No Caltrans PM for this source appears on crossing streets and other non-state-highway lines, which show distance from the source start instead. A source that has not loaded yet shows as pending.

Handle arrow keys move 10 m, and Shift moves 100 m. Right/Up means increasing source distance. Home/End reach the source limits. A keyboard move saves once when you release the key, and Escape before release restores the previous position. Keep 1 and 2 one mile apart moves handle 2 one mile from handle 1 when you turn it on. A handle you are moving stays reachable at the map edge. Saved projects retain the interval and handle identities; an unavailable original source path remains explicit.

Freeway and crossing streets together. Selecting a retained public freeway interval automatically looks for named Census street paths that cross it in plan. The freeway and several crossing streets stay selected together. Choose an active roadway for its numbered handles, ground profile and Drive preview; the other selected lines remain on the map. Partial or unavailable source coverage stays explicit.

Select from a structure or interchange. The larger map targets load nearby street paths. A unique source match selects the street automatically; ambiguous, parallel or multiple paths remain choices. A mapped crossing does not establish pedestrian access, grade connectivity or Caltrans ownership.

Groups and Layers. Groups switches related layers together and shows partial visibility. Layers exposes individual visibility, opacity and front-to-back order. Each row names its group. Drag a row, use its keyboard controls or select its up/down buttons; the list scrolls while you drag near its edge. In Groups, Front and Back move a whole group while keeping its layers' order. List order follows map stacking, including imagery and markers; essential road-selection feedback remains visible. Save and reopen these display preferences with the project.

Panning and zooming move the drawn reference layers with the map and redraw them once the map settles. Loads already under way continue, and nearby pans reuse references fetched for a slightly larger area. Turning a layer on or off, or changing its opacity or order, does not reload its data.

Map navigation. Pan and zoom with the mouse, map buttons or keyboard. With the map focused, Home fits the selected interval or loaded route.

Read the ground along the selected corridor

Preview v0.7: selecting or reopening a continuous interval of up to one mile automatically opens Corridor view and loads its ground-elevation profile. No separate terrain file is required. The profile and model follow the numbered direction, from handle 1 toward handle 2.

Seek with the distance slider or profile, choose Overview, Drive or Above, then press Drive to start playback. Pause whenever needed. Preview speed is a viewing setting. The expandable cross section shows ground up to 80 m on either side of the mapped alignment. On a phone, Map returns to the endpoint controls without discarding the selection.

The profile displays NAVD88 ground elevation in feet. Road, bridge and deck elevations remain unknown. The alignment symbol and ground-following camera do not establish pavement geometry, lane position, clearance, roadway grade or visibility.

An uncached interval uses a bounded USGS elevation request: at most 256 × 256 samples, a 2 MiB response and a 30-second time budget. Requested sample spacing is distinct from native source resolution. Unsupported cells remain gaps and stop playback. A failed request leaves the selected map usable with elevation unavailable; no flat substitute is generated. The 3D view needs WebGL2; the map and available profile remain usable if graphics fail. Reduced-motion settings keep viewing manual.

Earlier I-5 ground-preview check near Del Mar: numbered map handles beside a ground overview, explicit Drive controls and ground-elevation profile; road and bridge grades are unknown.Earlier 375-pixel ground-preview check with a distance slider, NAVD88 ground profile and Map return.
Ground-preview checks captured October 24, 2026. These earlier views show the retained USGS ground workflow; the alignment is a display symbol, and road, bridge and deck elevations remain unknown.

Record existing sidewalks and marked crosswalks

Conditions lists the freeway and every selected cross-street segment. Existing sidewalk widths and marked-crosswalk counts remain Not verified until you record supporting evidence. Atlas does not measure sidewalks from aerial imagery, road-centerline geometry or ground elevation.

Record a sidewalk width or absence at a stated location, with its side facing endpoint 1 toward endpoint 2, evidence source and date. Widths describe those locations; they do not establish a constant width along a street. A changed or reversed selected interval does not inherit the previous measurements.

Count marked crossing legs at all intersections within each selected cross-street segment, including its local-street intersections. Individual stripes and mapped road intersections are not crosswalk counts. A partial observation keeps the segment total unknown; a segment total of zero is shown only for an explicit recorded complete count. Recorded observations are not independently field-verified by Atlas.

Download the conditions table as HTML or CSV. Create report also includes these conditions for every selected roadway alongside the active corridor's reference inventory.

Create a corridor report

Create report loads references for the whole selected interval and lists interchange references, a separate structure inventory, community identifiers, boundary transitions and source coverage. It includes recorded conditions for the full selected collection. Export printable HTML or JSON; complete interchange totals remain unknown where source coverage is incomplete.

Where Edges Connect

Planning opens Where Edges Connect: from hard edge to people first, a reading of the selected freeway interval or crossing street. It has four chapters. Historical lens starts with Temporary Paradise? as a bibliographic record only, a historical reference rather than current policy. Current plans shows community and regional plan notes with exact source, version and page citations, amendments and conflicts, but only after a library operator loads the reviewed planning bundle in that tab. Site evidence fills in automatically from the official layers already loaded in Atlas: districts, boundary contacts, right-of-way references and the freeway-to-crossing-street sequence. Authored framing poses Field Method questions before any spatial thesis.

Each item is labelled as a mapped source reference, recorded plan policy, or Field Method authored question, so observed conditions, adopted policy and proposed interpretation stay distinct. Boundary contacts are possible gateways only. A bridge structure does not establish an exit or interchange. Informational right-of-way linework is not a legal boundary, and mapped crossings are not verified pedestrian connections. No reasoning model, image classifier, scoring rule or network request produces this reading. Direct access to the shared planning catalog is not enabled, and nothing from the reading is saved.

Keep an observation with its source

The catalog keeps photographs and selected surface regions together, so an observed finish or material hypothesis can be traced back to its context.

  • Add owned or permitted photographs. Select up to 500 files or bounded ZIP archives, confirm permission once and let Atlas resize and save them sequentially. Duplicates and unsupported files appear in the batch results.
  • Review placement. Camera position and the photographed asset have separate pins. Correct route, travel direction and photographed side; missing GPS stays in the placement queue.
  • Classify the photograph. Choose a category in photo details and record the appearance you observe, or request material suggestions with Catalogue with AI. Review each suggestion before treating it as your record. Existing saved labels remain in the record; unknown stays unclassified.
  • Record a surface. Outline an image region, then choose a category/type and editable tags. The legend covers concrete, stains, railings, rock, textures and landscape materials. Unknown remains a valid answer.

The map opens first. Switch to Catalog for search and material filters. Corridor selection uses the loaded reference geometry; a terrain or alignment file is not required.

Optional AI catalogue. After saving a cloud photograph and marking it Clear to send, explicitly start a catalogue run. The service requires that saved privacy status before sending the stored thumbnail to OpenAI for suggestions from 83 eligible dictionary types. Adding, importing or reopening photographs does not start inference. Manual observations and previously saved records remain available.

Suggestions describe visible appearance; they do not verify a material specification. Catalogue limits are 20 requests per private browser space and 100 across the site per day. The real-photo accuracy evaluation and per-photograph cost assessment have not run.

Choose where the work is saved

Cloud saving uses Field Method’s private R2 media storage and D1 records. Access belongs to this browser’s private space; there is no account or sign-in. Existing contributor labels remain attached to their records and do not verify a person’s identity.

Cloud mode uploads a re-encoded PNG at most 2,048 pixels per axis and 2 MiB, plus a thumbnail. Images may be reduced further to fit the byte limit. Source files on your device stay unchanged, and the app releases its temporary high-resolution buffer only after a confirmed save. Original metadata and source identity stay separate from the reduced image and reviewed placement.

Local only explicitly saves selected originals and records in this browser. Cloud failures never silently switch modes. Browser cleanup can remove local work or the access needed to reopen a cloud space; no account-based recovery or cross-device transfer is provided.

Official map references

The map loads the California Department of Transportation’s State Highway Network for San Diego and Imperial counties. The October 22–23 check returned 357 source pieces and 27 route labels. Source directions, route suffixes and postmile attributes remain distinct. Display simplification leaves the source geometry used for placement unchanged.

Derived chainage is distance along an individual source piece, not official postmile or engineering stationing. This is an informational state-highway reference, not a survey or a complete inventory of crossings, ramps, local roads or legal right-of-way. Service availability and current coverage can change. The optional imagery context uses attributed USGS The National Map imagery and topographic labels; image acquisition dates are not established by the service refresh date.

Automatic crossing-street discovery uses bounded requests to the U.S. Census Bureau’s TIGERweb local-road and secondary-road references. Returned street geometry is mapped context, not a complete crossing inventory or evidence of grade separation, legal access or sidewalk dimensions.

Numeric terrain comes from the USGS 3DEP bare-earth elevation service, resampled onto the requested grid. Source acquisition dates and native resolution vary. The panel converts source metres to feet. Bare-earth DEMs do not establish an elevated road surface; USGS DEM specifications call for bridges to be removed from that surface.

The base plan loads Census county boundaries, municipal jurisdiction boundaries, available City of San Diego community planning areas, incomplete District 11 right-of-way reference lines and source-described interchange ramp junctions. Bridge structure references have a separate toggle. Each layer retains its source, coverage and limitations. Bridge facility-carried and features-intersected fields remain source text; these points do not automatically establish a reviewed crossing, interchange or over/under relationship.

Unincorporated San Diego County community polygons remain unavailable while their usage terms are clarified. No usable official Imperial County community-planning polygon service is connected. Census, zoning and informal neighborhood outlines are not substituted. Right-of-way linework is informational and cannot determine ownership.

What has been checked

The depth workflow was reviewed locally in Chromium 156 on macOS using an actual I-5 source interval near Del Mar. One bounded selected-interval USGS response supplied the displayed ground surface and profile. The final rebuilt desktop and 375 px review replayed those same captured bytes, covering automatic open, station seeking, explicit playback, camera/speed choices, cross section, Map return and saved interval reopening. This is a workflow and parser check, not field or pavement-grade validation.

The simultaneous-selection workflow was checked in Chromium with an actual public I-5 interval and captured Census responses: the freeway and eight crossing streets were retained, active-road switching and reopening preserved the collection, and the 375 px chooser stayed within the screen. Conditions checks distinguish unknown values, partial observations and an explicit recorded zero. No field measurements were supplied for that mapped scene.

Source tests cover request and grid bounds, reversed handles, exact endpoints, NoData gaps, cancellation and stale results, graphics failure and reduced motion. The real I-5 test interval had no missing samples, so failure and gap behavior were checked with fixtures. The optional AI catalogue is available in beta; its recognition accuracy has not been established on the planned real-photo set. Opportunity authoring stays parked; previously saved categories, observations and study records are retained. The Mapillary visual character scan and street-imagery viewer were removed on October 27, 2026; Atlas reads no third-party street-imagery service.

Version 0.9 was checked locally in Chromium at 1280 px and 375 px on live Caltrans, Census and USGS sources. Checked items: automatic crossing-street selection from a structure marker, the endpoint postmile badges, all four Where Edges Connect chapters, and phone-width layout of the reading. In the same local scenes, toggling a layer made no network requests, and panning while layers loaded made none against 17 in one run of the previous build. Frame smoothness during zoomed-out pans did not measurably improve and varied between runs. These are local measurements, not production latency or frame-rate guarantees. Physical touch and Safari remain unverified.

The earlier corridor-selection release was reviewed locally in Chromium at desktop and 375 px widths: crossing-street preview, confirmation and reopen; handles passing one another by pointer and keyboard; Escape rollback; mixed groups and actual layer stacking; saved preferences; Home; and external imagery-point selection. Repeated layer toggles reused loaded geometry in the measured local scenes; that is not a production latency or frame-rate guarantee.

Earlier catalog checks used generated photographs, corrections and save/reopen. A simulated 500-file queue tested sequential preparation and partial failure; it was not a 500-photo production upload. Existing private cloud saving has separate release verification. The local screenshot preview disabled private cloud endpoints, so its captures do not establish production saving or isolation.

  • A photograph supports an appearance observation or material hypothesis. It does not establish exact paint, composition, thickness, quantities or real surface area.
  • GPS does not verify identity, ownership or the photographed asset’s position. Coordinate placement is planning context, not survey control.
  • Field accuracy, physical touch/pinch, 200% browser zoom, native Safari and other browsers remain unverified for this release. The ground preview is not a viewshed, traffic, safety or engineering analysis.
  • JPEG, PNG and WebP intake are supported within the tool’s limits. HEIC/HEIF needs conversion; unsupported files are reported.

Questions

Does saving publish my photographs?

No. Saving creates private records in the selected space. A public sharing or review workflow is not part of this release.

Can I open the same cloud space on another device?

Not through an account. The browser holds access to its own private space, so clearing that access or reaching its expiry can prevent reopening. Cross-device recovery remains future work.

Are photographs classified automatically?

Adding photographs does not start classification. You can choose a category yourself or explicitly request Catalogue with AI for saved cloud photographs marked Clear to send. Only the stored thumbnail is sent to OpenAI, and the returned material suggestions need your review. Saved labels from earlier versions remain readable.

Is the elevation profile the road's grade?

No. It samples ground along the mapped alignment. Elevated roads and bridges need separate verified elevation evidence; the tool does not infer their deck or pavement heights.

What next?

The labelled real-photo catalogue evaluation, verified sidewalk and complete marked-crosswalk inventories, broader community coverage, field-reviewed access evidence and explicit sharing remain later work. Opportunity Map authoring is saved for a future requested release. Send a task-specific problem or reproducible issue through the feedback link.

Related: Corridor Studio · Material Studio · Site Lens