See the corridor the way people will move through it
Grading plans, profiles and cross-sections describe a road or trail in plan and section. Reviewers, clients and the public meet it in motion, at eye level. Where the earthwork, grades and sight lines change along the route is hard to read from drawings alone.
Corridor Studio puts the existing and proposed surfaces side by side along the alignment, so a team can drive the route, stop where something changes, and see the same station in the profile and in a set of measures.
It is for landscape architects, civil engineers, planners and designers working on roads, trails, greenways and other linear corridors at concept and design development.
How it works
- Load your data. Open a LandXML file with the alignment and the existing and proposed surfaces, or load them as separate files. Surfaces are recognized as existing or proposed from their names; you can change the choice. A second set of files with an alignment and a surface becomes the project, and any loaded item can be removed under Data & settings.
- Drive the route. Play at a chosen playback speed, which sets only how fast the drive-through runs, or drag along the profile to any station. Switch between eye height and a view from above.
- Swipe before and after. Drag the divider across the view: existing ground on the left, proposed grading on the right. Or show either surface on its own.
- Read the dashboard. Each measure shows its value at the current station, a color-coded band, a sparkline along the whole route and the share of the route in each band.
- Export the station table as CSV, the current view as an image with its station and a preview note, or a draft memo in Markdown. Save the assessment as a file to reopen it later or on another computer.
The measures
- Cut / fill at centerline
- Proposed minus existing elevation on the alignment. Where no proposed surface covers a station, the proposed elevation comes from the design profile in the LandXML file, if it has one, and the dashboard says so.
- Proposed grade
- Slope of the proposed surface along the alignment over one station interval, or of the file’s design profile where no proposed surface covers the station.
- Forward sight distance
- How far ahead along the route an object of a set height stays above the ground line from the viewer’s eye. Where the route or surface ends first, the value is shown as a lower bound.
- View enclosure
- The highest angle from eye level to the ground within a band either side of the route: how much the ground rises beside the viewer.
- Terrain change in view
- Average height change between existing and proposed ground across that band.
Each measure is rated low, moderate or high against two thresholds. The thresholds supplied are example values for exploring a design, not standards. Set them to your project’s criteria. Eye height, object height, station interval and band width are adjustable too.
Visual impact by landscape unit
The route is divided into landscape units, suggested where enclosure and earthwork change, which you can split and merge. For each unit the app measures project change (cut, fill and grade; trees removed only when a tree layer is loaded, which today means the demo) and how long travelers have it in view at a traveler speed you set in the unit card, separate from the playback speed. You rate existing and proposed visual quality (natural harmony, cultural order and project coherence), viewer awareness, neighbors and protected views.
The app then suggests whether the change is beneficial, neutral or adverse, and to what degree, for you to confirm or replace. Findings appear as a color strip along the route and on the profile, and export as a draft memo organized by the phases of the FHWA Guidelines for the Visual Impact Assessment of Highway Projects (2015). The suggestion rules are Field Method working rules stated in the memo, not rules from the guidelines, and the draft is not a completed assessment. Ratings are kept in your browser for that alignment.
Candidate key views
Visual impact is usually discussed from a few key views; the app proposes candidates for them from your own ratings and the terrain change it measures. Each station takes its landscape unit’s existing visual quality ratings, or a rating you set for that station alone in the unit card. Its score is the mean of natural harmony, cultural order and project coherence, and only when all three are rated; no score is inferred from terrain.
“Existing quality on profile” colors the profile by that score, gray where a station is not rated. The Key view candidates card proposes stretches of road, up to 500 ft long by default (150 m in meters):
- Highest existing quality (Q): the highest-scoring stretches, up to the number you ask for (5 to 10; 7 by default), none overlapping and no more than one per landscape unit. Ties in score go to the stretch whose landscape unit has the longer traveler time in view. You can set a minimum gap between them.
- Greatest change (C): unless you turn it off, each unit’s stretch with the greatest terrain change in view.
- Added by you (H): a stretch starting at the current station.
Every suggested candidate stays a suggestion until you confirm or dismiss it. Quality stretches you confirm, and stretches you add, count first, toward the number asked for and the one per unit. A dismissed stretch is not suggested again, and no suggestion overlaps a dismissed stretch of its kind. Candidates are bracketed on the profile and listed in the draft memo, each marked confirmed or added by the preparer, or suggested and not confirmed.
The station score, the 1-to-7 scale and the ranking rules are Field Method working rules, not rules from the FHWA guidelines, as the profile legend and the memo say. The app proposes; you choose the key views. Station ratings and key view decisions are kept with the other ratings, in your browser and in the assessment file.
Coordinate system and base map
Choose your project’s coordinate system: the app proposes the EPSG code a LandXML file declares, or you pick one of the 15 systems bundled for the San Diego County pilot (California zone 6 and UTM zone 11N, in the NAD83 realizations and units a San Diego project would use). It warns when the file’s length unit and the system’s disagree, including US survey feet against international feet, and when the route falls outside the system’s area of use. With a system set, an opt-in plan-view base map of USGS The National Map imagery shows the route, stations, your current station and the key view candidates, and you can confirm that the route sits in the right place; the confirmation is saved with the assessment, named in the memo, and cleared if the system or alignment changes. The station table gains longitude and latitude. The base map changes no measure. Positions treat NAD83 as WGS 84, a difference of about 1 to 2 m in the conterminous US: fine for a base map, not for survey work.
Supported data
- LandXML 1.x alignments (lines, arcs, clothoid spirals, irregular lines and chains of points; station equations are applied) and TIN surfaces, as exported from civil design software such as Civil 3D, OpenRoads or 12d. Irregular lines and chains have been tested only with hand-written LandXML files. Units are read from the file, including US survey feet. Element names with the LandXML namespace prefix, such as lx:Alignment, are read too.
- Design profile from the alignment’s first LandXML ProfAlign: tangent grades between PVIs, symmetric parabolic and circular vertical curves. It is drawn dotted on the profile as “Design profile (from file)”. PVI stations are read without station equations (an interpretation of the LandXML schema), with a warning when the alignment has them. So far tested only with hand-written LandXML files, not with an export from design software.
- Alignment as CSV with x and y (or easting and northing) columns, a survey point file in PNEZD or PENZD order, or a GeoJSON line.
- Surfaces as glTF or GLB meshes.
- Working in DWG or DGN? The app cannot open drawings directly; export LandXML from Civil 3D (DWG) or OpenRoads Designer (DGN) with the alignment and both surfaces. The app works in decimal feet and mph by default; switch to meters in Data & settings.
All files must use the same projected coordinate system, such as State Plane or UTM. Longitude and latitude are not supported. A current browser with WebGL 2 is required.
Limitations
- The base map was built and tested with stand-in tiles; it has not yet been checked against the live USGS service. USGS’s terms and preferred credit wording were read only in secondary sources and are being confirmed. The bundled coordinate systems cover San Diego County only, and the invented demo corridor has no real location, so it shows no map.
- The measures describe the loaded surfaces, and the file’s design profile where it stands in for a missing proposed surface. They are not a design check, a sight-distance compliance review or a visual impact assessment.
- Buildings, vegetation and structures are not obstructions unless they are part of a surface. The demo’s trees are illustrative.
- The view is a real-time rendering for orientation and discussion, not a verified photo simulation.
- A design profile gives cut / fill and grade only where no proposed surface covers a station; the two are never averaged. It does not change the 3D view, sight lines, enclosure or terrain change. Unsymmetrical vertical curves are not computed and leave a gap, with a warning, and only the first design profile of an alignment is read.
- A LandXML plan element the app cannot read is named in a warning. Between elements that were read, the gap is bridged by a straight line; an unreadable first or last element is left out, which shortens the alignment, and an unreadable first element also shifts every station after it. An arc given without its center is drawn as a straight chord, with a warning.
- A key view is a stretch of road with a status: it has no position, view direction, viewer group or photograph yet. The 3D view, route line and station table do not show the score or the candidates, and the color bar shows the combined score only, not a single criterion. A stretch cannot be dragged; dismiss it and add one by hand.
- Key view candidates come only from your ratings and the terrain change measure. They have been tried only on the invented demo corridor, in Chromium, not on a real project or by a practitioner.
- Assessment files are now format version 2. Files saved earlier still open, but a copy of the app from before October 7, 2026 refuses a version 2 file rather than drop its station ratings and key views.
- Large surfaces take longer to load; very large survey surfaces may need simplifying first.
- This is an early version. Compatibility with every export and browser has not been tested.
Questions
Is it free?
Yes, it is free to use.
Are my files uploaded?
No. The app is a single web page; it reads your files in your browser and does not send them anywhere. It makes no network requests unless you turn on the base map; then it requests imagery tiles for the map area from USGS The National Map, which therefore sees that area.
Where does it come from?
It is part of Field Method’s research into route-based visual assessment: how a corridor changes for the people who move along it. The research continues; Corridor Studio is a working tool alongside it.
What next?
Next steps being considered for the key views: street-level photographs of existing conditions for each key view, and a printable viewpoint report. The photos would be opt-in, like the base map, because they mean requests to an outside service. Obstructions such as buildings and vegetation are being considered too. Tell us what your projects need.
Related: Material Studio


