Description
Scale nonnegative floorArea by tripRate/positive unitArea for grossTrips.
Spatial models compare distances, travel intervals, activity areas, or supplied interaction functions. Coordinates and model parameters must share a compatible basis, and a local term does not establish observed behavior.
Scale nonnegative floorArea by tripRate/positive unitArea for grossTrips.
When to use this tool
Use Landuse Trip Rate One Parcel Term when you need one explicit spatial or travel-model component.
How to use the tool and how it works
- Enter floorArea, unitArea, tripRate, passbyFraction, internalCaptureFraction. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read grossTrips, externalNewTrips. Use the output convention below.
Scale nonnegative floorArea by tripRate/positive unitArea for grossTrips. Multiply by one minus passbyFraction and one minus internalCaptureFraction for externalNewTrips.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| floorArea | Floor Area | Required. Finite number; minimum 0. |
| unitArea | Unit Area | Required. Finite number; strictly above 0. |
| tripRate | Trip Rate | Required. Finite number; minimum 0. |
| passbyFraction | Passby Fraction | Required. Finite number; minimum 0; maximum 1. |
| internalCaptureFraction | Internal Capture Fraction | Required. Finite number; minimum 0; maximum 1. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| grossTrips | Gross Trips | Required. Finite number. |
| externalNewTrips | External New Trips | Required. Finite number. |
{
"input": {
"floorArea": 1000,
"unitArea": 100,
"tripRate": 5,
"passbyFraction": 0.2,
"internalCaptureFraction": 0.1
},
"output": {
"grossTrips": 50,
"externalNewTrips": 36
}
}Limitations and assumptions
- Fractions lie in [0, 1] and floorArea and unitArea share units; sequential reductions and the trip rate are supplied, without traffic counts, calibration, or network impact analysis.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
- Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.
Alternative or Complementary methods
Check projection, route definitions, calibration, and the complete model before interpreting access or predicted flows.
References
Similar or alternative tools
- Gravity Flow One Origin Destination Term
Multiply nonnegative coefficient, originMass, and destinationMass and divide by positive distance raised to supplied exponent.
- Accessibility One Destination Decay Term
Return exp(-decayRate × travelTime) and opportunities times weight times that decay.