FIELD METHOD

Corridor Atlas

Caltrans ROW + crossing streets
1Select
2Confirm & collect
3Report
4Corridor view
Caltrans ROW + crossing streets · SD + Imperial
Photo & material catalog0 records
Materials & appearance 0 regions

Types and tags describe photographic evidence. Composition, stain cause and performance remain unverified.

0

No photographs yet.

FIELD METHOD / SOURCE-LED READING

Where Edges Connect

From hard edge to people first

Operator: load reviewed planning bundle

For the library operator: load the exact reviewed metadata JSON. It is checked against the pinned snapshot, stays in this tab only and is not added to photographs or saved projects.

No bundle loaded. This browser does not fetch the reviewed catalog.

PRIVATE CONTRIBUTION

Add photographs

Drop photographs or a photo ZIP here

500 selected files · processed one at a time · 32 MiB / 40 MP per photograph. ZIP: 100 photos / 160 MiB per archive. JPEG, PNG, WebP. Export HEIC as JPEG first.

Private until explicitly shared.

Cloud: reduced PNG only · up to 2,048 px / 2 MiB. Source files stay unchanged. The app releases its high-resolution buffer after confirmed saving.

MATERIAL STUDIO / PHOTO OBSERVATION

Material observation

Keyboard vertex controls

Add at least three vertices, then finish outline.

Photographic color and material type are observations or hypotheses, not verified specifications. No real surface area is inferred.

No surface outlined.

MAP ANALYSIS

Analysis record

Geometry
Coordinates / keyboard entry

WGS84 longitude, latitude · one pair per line.

Evidence & responsibility

Sources & working limits

Basemap · USGS The National Map

USGS Imagery Topo: orthoimagery and US Topo. Service refresh: April 2026, v1.2. Image acquisition varies and is unknown here. Coverage: United States; unavailable tiles leave the alignment usable on a plain background.

Service & attribution ↗

Map services and data available from U.S. Geological Survey, National Geospatial Program. No terrain/tilt is loaded; the fast 2D map is the working view. Display-only viewport tiles; no bulk cache.

Corridor view · ground and aerial imagery

The Corridor view reads the selected corridor’s ground from the USGS 3D Elevation Program service, and, only while its “Aerial imagery on the ground” toggle is on, drapes one USDA National Agriculture Imagery Program (NAIP) export from the USGS National Map imagery service (USDA FPAC fallback) over that ground. The export covers exactly the loaded terrain frame at a bounded size (at most 2,048 pixels on its longer side), is public domain and display only, and is never saved with a project; this browser remembers only the toggle and strength. Acquisition dates vary by tile and are shown when the service catalog returns them.

USGS NAIP imagery service ↗

Resampled aerial pixels on a resampled ground grid: not a survey, right-of-way boundary, roadway grade or current-conditions record. Clouds, shadows, building lean and seasonal change belong to the acquisition, not to the site today.

Highway reference

Official regional highway reference is loading. No substitute geometry is generated if the service is unavailable.

California Department of Transportation · State Highway Network ↗

Dated cached reference for San Diego and Imperial counties, with live-source fallback when unavailable. Source pieces, directions and postmile attributes are retained. Derived path chainage is not official postmile or engineering stationing. Public reference snapshots are stored separately from private photographs; retrieval date is distinct from the source vintage.

Owner alignments & inventory

Imported geometry retains its source file and CRS; it is not automatically verified as an official freeway alignment. Neither county has a complete inventory in this slice. Stationing follows the loaded alignment direction; side labels must be reviewed.

Context layers & crossing evidence

Municipal limits, official community/planning areas and right-of-way references are separate layers with different coverage and dates. Selected layers load for the map view; availability and source records appear in the Atlas log. An absent feature does not establish that a boundary, structure or crossing is absent.

Informational right-of-way records cannot determine ownership or establish an engineering/design boundary. No highway buffer represents right-of-way. Source structure points are crossing candidates, not a complete crossing inventory; over/under relationships, ramps and pedestrian connections require reviewed evidence.

Streetscape · OpenStreetMap

Only when you choose Read streetscape from OpenStreetMap for a selected corridor, Atlas asks the public Overpass API for mapped sidewalks, road sidewalk tags, crossings, trees and tree rows within 50 m of the selected line and groups them into 100 m stretches with your analysed photographs. No key or account is used. "Not mapped in OpenStreetMap" is not "absent": completeness varies street by street. Photo numbers are model estimates, not measurements.

© OpenStreetMap contributors · ODbL 1.0 ↗

AI photo suggestions · OpenAI

Two optional tools send a photograph to OpenAI through Field Method's server: Suggest with AI (eight broad classes such as road, sidewalk and trees, as shares of the frame) and Catalogue with AI (material types from the dictionary, only types the owner has marked visually eligible). Only photographs marked Clear to send can be sent, only from the private cloud space, and only when you start a run; nothing runs on upload, import or reopen. What is sent is a reduced copy of about 640 pixels at low detail, with storage turned off (store:false). OpenAI does not train on API data by default; it may keep requests for up to 30 days in abuse-monitoring logs, longer where the law requires, and scans images for child-safety violations (checked October 29, 2026). Daily limits apply per space and for the whole site. Every answer is a model suggestion: it is not a measurement or a verified specification, and nothing counts as an owner record until you review it.

OpenAI API data controls

Contributions & storage

Cloud saving uses a private space associated with this browser through Field Method’s existing R2 media storage and D1 record store. No sign-in is required. Layer labels are organizational labels, not verified identities. Anyone using this browser profile may access its space. Clearing browser access data can prevent this browser from reopening the cloud space; this is not an account-based collaboration system.

For new cloud saves, the browser resizes the photograph to at most 2,048 pixels on its longest edge and encodes a PNG before upload, reducing it further if needed to fit the 2 MiB image limit. Only that reduced image is saved to the cloud; the source file on your device is unchanged. The app releases its high-resolution image buffer after a successful cloud save. Original metadata and source identity are recorded separately from the reduced image and reviewed asset placement. Existing saved evidence is not rewritten by selecting a different mode.

Local only is an explicit choice. It uses IndexedDB in this browser for selected originals, thumbnails, metadata and observations. Browser cleanup or eviction can remove this local work. A failed cloud save does not automatically switch to local saving. Neither mode publishes photographs automatically. Recoverable removal retains records; no permanent-deletion or automatic-retention schedule is active.

Street photographs & future video

Street photographs are the ones you add to this project. Atlas reads no third-party street-imagery service. Photos do not establish ownership, right-of-way, safety, accessibility or cultural value. Video ingestion and frame extraction are a later slice; future records must retain exact frame timestamps and distinguish camera tracks from asset locations.