For climate and environmental consultants
Site-context package for the climate appendix: the neighbours' model, without building it by hand
Every project rebuilds the site model from scratch: neighbour heights, floor counts, and plans that are approved but not yet built. This model already exists for every address in Israel, from municipal sources, permits and transactions — exported in a format that opens in Rhino, Ladybug or Radiance.
What the committee counts
Every address in Israel
The site model already exists; it is not built to order.
Today + future
Also includes massing for approved, not-yet-built plans, at the permitted height.
Regulation 87(g)
"List of references": the software name and method appear in the appendix. Apricity enters the same line as Ladybug.
21 Dec · 09:00–15:00
The same window the committee counts, computed from true solar time at the site.
The signature stays yours. The document supplies what used to be built by hand — not the judgment.
What the document contains
Site-context package
- A 3D model of every building within the influence radius, with a source for every height (municipal / permit / transactions / OSM)
- Massing for approved, not-yet-built plans, per the rights table
- Export to a standard 3D format (OBJ/glTF) and a list of sources
Full shading module
- Everything above, plus a sun-hours table for 21 December, per neighbour and per apartment, today and after the plan, in your appendix template
- Isolating the plan from the plans around it
- Method appendix
Office subscription
- Unlimited site-context packages for the office's projects, updated whenever the municipal data updates
Who, and when
A climate or environmental consulting office
When the next appendix needs a site model and no one has time to build it this week.
An architect preparing their own shading appendix
For plans where the committee requires a shading study but not a full climate appendix.
What committees have already said
„the model was made in RHINO… LADYBUG… RADIANCE”
The software is always named. The site-context package enters the same reference line.
„the mutual effect… in terms of shading”
The requirement is about the relationship between the building and its neighbours — that is, about the neighbours' model, exactly the part rebuilt by hand every time.
How it is computed
A 3D model of the building under review and every neighbour within the influence radius, from municipal heights, permits and transaction data — not a general estimate.
The sun path is computed from true solar time at the site, on 21 December, in the 09:00–15:00 window, floor by floor and apartment by apartment.
Two states per neighbour: today, and after the plan. The difference is the number the committee asks about. One plan isolated from every other plan around the address, or cumulative — as needed.
Recurring questions
What format does the model arrive in?
A standard 3D file (OBJ or glTF) at metre scale, oriented to north, with a source list for every height. It opens in Rhino and from there in Ladybug or Radiance.
Where do the heights come from?
Municipal GIS layers, building permits, Tax Authority transaction data, and OSM — in that order, and every height carries its own source. A height with no source is marked as an estimate.
What about plans that are approved but not yet built?
Included as massing at the height permitted by the rights table, marked separately from what is already built. This is the hardest part to collect by hand.
Does this compete with us?
No. The signature, the judgment, and the wind and thermal-comfort chapters stay with you. The document sells speed and per-apartment resolution, not expertise.
How do we start?
Send the address of a real project. The first package goes out for review, and it ends with one question: what did this save, and which line in the budget it would have come from.
Send an address and a plan number — you get a scope and a timeline back.
No sign-up form and no sales call. A written answer within one business day.