Embedded Files
In this section, we will delve into the inner workings of LotLogix, providing a detailed overview of the script's logic and functionality. From zoning compliance checks to construction cost estimation, we break down each step of the process into simple, digestible blocks, offering insight into how LotLogix transforms complex data into actionable insights for developers."
We begin the process by bringing in the surrounding context massing.
The property line s brought in as a boundary, within which we will start to create our development
we then establish our development constraints.
we reference the local zoning to define requirements for Front, side and rear setbacks, minimum and maximum lot sizes, minimum lot width and depths as well as structure maximum height.
we will also set primary and secondary street widths per city requirements
Finally, we set a few more parameters introduced by the developer; a range of acceptable building sizes and a floor area ratio.
With this information we can understand out generative goals and begin to set our parametric constraints.
A primary arterial street is created that will run through the subdivision. This primary street is wider than alternative streets. It also moves along the property lane, generatively to allow for the most usable lots per division
Secondary streets are created, following the constraints defined by evaluating both lot depth as well as lot area.
For example if a lot is between 7500 and 10,000 sf it can be divided from the front and the rear by the side setback constraint.
Additionally if a lot is deeper than 340’ it can be subdivided; because the road is 25' wide on either side’of each lot which would be 120’ each allowing the new lots to meet the minimum lot depth.
Does the lot meet the pre-defined constraints?
Here we calculate all of the pre-defined constraints; lot width, lot depth, front, side and rear setback requirements, and min/max lot area.
All that remain now are usable lots that fit all of our requirements, those that do not have been excluded from our calculations.
Within our buildable area a massing is created that falls within our maximum height limitations.
FAR and building footprint are calculated to ensure they comply with our requirements.
In this image the heights vary randomly between our minimum and maximum height variables.
Next, we calculate how many usable lots we have and how much FAR we can to maximize useable space and overall profitability for the development.
Finally we define the FAR per unit, using pre-defined floor-ceiling heights. This allows us to analyze specifics for each lot; GFA, FAR, Site use, etc.
Lots that do not meet the constraints will be considered as useable green space parks, trails, etc.
The script allows the user to focus on maximizing the variables of their choosing, whether that be coverage, accessibility, diversity of housing stock.
Future applications will look to introduce increased functionality such as integration of construction costs and loaded pre-defined housing typologies will increase the efficacy and applicability of the script.
Page updated
Google Sites
Report abuse