Geometry literacy · Development capacity

About the project

Site Geometry and Development Capacity

The Site Feasibility Sandbox helps students move from an abstract site plan to measurable relationships among area, setbacks, building footprint, lot coverage, stories, gross floor area, and FAR. It is designed for instruction and exploratory reasoning—not for determining whether a real project can be built.

Who should use it

The tool is intended for real estate, urban economics, planning, and related courses in which learners need a quick, visual way to test development-capacity concepts.

No account, specialized GIS software, or prior coding experience is required. All edits and calculations occur in the browser.

How to use it

  1. Begin with the Pollak Library guided case or load a prepared surface-lot example.
  2. Edit the site or building shapes, or draw your own site and footprints.
  3. Change the setback, FAR, coverage, and story assumptions.
  4. Compare live results and identify which simplified constraint appears to bind.
  5. Ask which omitted rules or real-world conditions could change the conclusion.

Prepared cases and boundary method

The Pollak Library case uses a mapped building outline inside an instructional study boundary. The three parking-lot cases use mapped surface-lot outlines with hypothetical building concepts. They provide recognizable geographic context while keeping the exercise editable.

Mapped outlines are adapted from OpenStreetMap. The official CSUF campus map is the appropriate source for current campus orientation and parking information. Neither source supplies a legal parcel or survey boundary for this tool. Parking names, access rules, site conditions, and mapped features can change.

Interpretation rule

Every preset should be read as a teaching scenario. A mapped outline indicates geographic context; it does not establish ownership, development availability, regulatory status, or institutional plans. Preset building footprints and all development assumptions are hypothetical unless the interface explicitly identifies a feature as mapped existing.

What the calculations include

  • Site and buildable area after a uniform setback
  • Building footprint, lot coverage, and open site area
  • Gross floor area and floor area ratio
  • Capacity under selected FAR, coverage, and story assumptions
  • Warnings when footprints extend beyond the simplified buildable envelope

What the model omits

  • Verified parcel, title, easement, and survey information
  • Applicable zoning, overlays, entitlement procedures, and legal review
  • Parking, access, fire, accessibility, infrastructure, and environmental requirements
  • Structural, architectural, engineering, and construction feasibility
  • Market demand, costs, financing, valuation, risk, and investment returns

Educational and professional-use disclaimer

The Site Feasibility Sandbox provides simplified, preliminary estimates for classroom instruction and independent learning. It does not provide land-use, zoning, legal, engineering, architectural, environmental, appraisal, brokerage, investment, or other professional or consulting advice. Nothing produced by the tool establishes a property boundary, development right, entitlement pathway, project feasibility, market value, cost, or expected return.

Do not use the output to make acquisition, design, permitting, financing, construction, or investment decisions. A real project requires current source documents, verified measurements, applicable regulations, site-specific evidence, and review by appropriately qualified professionals and public agencies.

Creator and citation

The tool was created and is maintained by Desen Lin for real estate instruction at California State University, Fullerton. Questions about the tool can be sent to Desen Lin.

Suggested citation

Lin, Desen. (2026). Site Feasibility Sandbox (Version 1.1.0) [Computer software]. https://desenlin.com/site-feasibility-sandbox/

The application has no account system or server-side database. Calculations run locally in the browser, and the project does not collect or transmit the site shapes or assumptions entered by users.