<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:st1 =
"urn:schemas-microsoft-com:office:smarttags"><HEAD><TITLE>Re: [GSBN] SB Overhangs (was Big News!)</TITLE>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18943"><!--[if !mso]>
<STYLE>v\:* {
BEHAVIOR: url(#default#VML)
}
o\:* {
BEHAVIOR: url(#default#VML)
}
w\:* {
BEHAVIOR: url(#default#VML)
}
.shape {
BEHAVIOR: url(#default#VML)
}
</STYLE>
<![endif]--><o:SmartTagType downloadurl="http://www.5iantlavalamp.com/"
name="PlaceType"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
downloadurl="http://www.5iantlavalamp.com/" name="PlaceName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
downloadurl="http://www.5iantlavalampft-com:office:smarttags" name="Street"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="State"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
downloadurl="http://www.5iamas-microsoft-com:office:smarttags" name="City"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
downloadurl="http://www.5iantlavalamp.com/" name="country-region"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
downloadurl="http://www.5iantlavalamp.com/" name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
downloadurl="http://www.5iamas-microsoft-com:office:smarttags" name="address"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[if !mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<![endif]-->
<STYLE>
<!--
/* Font Definitions */
@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Futura Lt BT";
panose-1:2 11 4 2 2 2 4 2 3 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{margin:0cm;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}
p.MsoAutoSig, li.MsoAutoSig, div.MsoAutoSig
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Arial;
color:green;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
@page Section1
{size:595.3pt 841.9pt;
margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:476461121;
mso-list-template-ids:-1643868626;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:36.0pt;
mso-level-number-position:left;
text-indent:-18.0pt;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0cm;}
ul
{margin-bottom:0cm;}
-->
</STYLE>
</HEAD>
<BODY lang=EN-GB link=blue bgColor=#ffffff vLink=blue>
<DIV><FONT size=2 face=Arial>Hello all,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>again compliments to all this great work which
in essence should make things easier by systemized solutions. If I read Andys
remarks on freedom of desgin we might be able to solve the paradox of
securing people from design failures and at the same time stimulate ongoing
experiments by a simple preamble for codes: ."this or better".
</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>This would be an opening to convince building
inspectors for what's not be known yet, but definitly soon will be offered.
Without flexibility there is just little innovation. And it is the "cemented
aspect" of the building industry which spends a minimum for innovation in
comparison to other sectors. </FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Best wishes from a rainy Brittany,</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial>Martin Oehlmann</FONT></DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV><FONT size=2 face=Arial></FONT> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV>----- Original Message ----- </DIV>
<BLOCKQUOTE
style="BORDER-LEFT: #000000 2px solid; PADDING-LEFT: 5px; PADDING-RIGHT: 0px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px">
<DIV
style="FONT: 10pt arial; BACKGROUND: #e4e4e4; font-color: black"><B>From:</B>
<A title=andy@ecodesignarchitects.co.za
href="mailto:andy@ecodesignarchitects.co.za">Andy Horn</A> </DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=GSBN@greenbuilder.com
href="mailto:GSBN@greenbuilder.com">'(private, with public archives) Global
Straw Building Network'</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, August 25, 2010 10:36
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> Re: [GSBN] SB Overhangs (was Big
News!)</DIV>
<DIV><BR></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">Hi
Martin<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">I certainly don’t
envy those trying to create a 1 size fits all international building code that
balances freedom of design and place for innovation with the specifics of good
building practice. Anyhow to add some further food for
thought.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">In answering
questions about what to do with multi storey designs, I always find history to
be such a valuable tool when it comes to looking at various design responses.
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">The vernacular
architecture of Japan has evolved a very sensible architectural style when it
comes to protecting their thin little earth plastered wattle and daub
structures. Numerous numbers of these structures still exist with some are
many hundreds of years old, with some being even 3 or 4 storeys high of earth
plaster!! The roofs are often but not always hipped, affording good overhangs
all around and in the case of multi storey buildings each floor has its own
min roof around it like skirts.…so shedding the rain at each level. In the
case of gabled wall ends, all the openings have min roofs over them. Other
times the clay wattle and daub is given a basic plaster and then an external
timber siding rather than more plaster is used. Effectively parapet walls are
generally avoided so the roof always closes over the top of a wall. Even their
boundary walls, which are usually of more solid packed earth and are typically
earth plastered, all have mini roofs over the tops of the walls ….usually 1
layer of beautiful crafted fire clay tiles overhanging either side with a
ridge cap in the centre. Their plastered walls are also broken into panels
with expressed timber framing, so that the plaster surfaces are broken down
into manageable sizes that can be plastered to absolute perfection and
generally present much fewer problems with
cracking.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">I am not familiar
with the extent or wording of the code, so I may be speaking out of context
but generally I would be worried about being overly prescriptive about how one
solves a problem ....especially where officials can take a narrow
interpretation of a code and there may be ways and new products that have not
been thought of yet that may offer alternate solutions? While I agree having
roof overhangs is best practice and I have not done otherwise, it may be wiser
that one set about defining what one is trying to do that a roof overhang is
doing…i.e. not letting water get in from the top being the most critical
clearly….. or is one trying to give the wall some degree of protection from
rain hitting it by using an overhang as well? Because outright protection I
don’t believe is practical or even necessary. I think the degree or amount of
overhang is more of a regional thing that is even specific to the exact
context of the site of the building… the intensity of rain that is potentially
hitting a wall and the direction that it comes (rain does not always come from
above) are clearly important factors to try and understand and respond to and
will vary from place to place.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">Context will change
things and how one designs in relation to the context …..so I would
imagine some of what the code needs to address would be how design may respond
differently in relation to the amount of rain, wind direction, wind driven
rain (if applicable), rain intensity, when it rains in relation to how cold or
hot it is, so one understands how quickly or otherwise rain may be able to dry
out again. The position of ones overhangs and rain buffers (pergolas, shade
devices etc) and use of rain screens may be of more importance depending on
where and how big one designing……the rain here in the Cape is typically winter
rainfall that is wind driven almost always coming from the North west….and in
some cases comes in horizontally especially along the coast. In these cases
one has to look at incorporating siding over the bales and rain screens on the
exposed sides to help shield the rain….and in certain cases I will avoid using
straw in the parts where it is too at risk….so I rarely end up with a building
with 100% of its walls being in straw bale.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">Best
<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt">Andy
Horn<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoPlainText><FONT color=green size=2 face="Futura Lt BT"><SPAN
style="FONT-FAMILY: 'Futura Lt BT'; COLOR: green; FONT-SIZE: 10pt"
lang=EN-US>ECO DESIGN – Architects &
Consulatants<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT color=green size=2 face="Futura Lt BT"><SPAN
style="FONT-FAMILY: 'Futura Lt BT'; COLOR: green; FONT-SIZE: 10pt"
lang=EN-US>6<SUP>th</SUP> floor, 79 on Roeland, 79 Roeland St.
<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT color=green size=2 face="Futura Lt BT"><SPAN
style="FONT-FAMILY: 'Futura Lt BT'; COLOR: green; FONT-SIZE: 10pt"
lang=EN-US>8001, <st1:place w:st="on"><st1:City w:st="on">CAPE
TOWN</st1:City>, <st1:country-region w:st="on">SOUTH
AFRICA</st1:country-region></st1:place><o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT color=green size=2 face="Futura Lt BT"><SPAN
style="FONT-FAMILY: 'Futura Lt BT'; COLOR: green; FONT-SIZE: 10pt"
lang=EN-US>Tel: 07 21 462 1614, fax 07 21 461
3198<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT color=green size=2 face="Futura Lt BT"><SPAN
style="FONT-FAMILY: 'Futura Lt BT'; COLOR: green; FONT-SIZE: 10pt"
lang=EN-US>website: www.ecodesignarchitects.co.za<o:p></o:p></SPAN></FONT></P>
<P class=MsoPlainText><FONT color=green size=2 face="Courier New"><SPAN
style="COLOR: green; FONT-SIZE: 10pt"
lang=EN-US><o:p> </o:p></SPAN></FONT></P></DIV>
<P class=MsoNormal><FONT color=green size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; COLOR: green; FONT-SIZE: 10pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><FONT size=3
face="Times New Roman"><SPAN style="FONT-SIZE: 12pt" lang=EN-US>
<HR tabIndex=-1 align=center SIZE=2 width="100%">
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT size=2 face=Tahoma><SPAN
style="FONT-FAMILY: Tahoma; FONT-SIZE: 10pt; FONT-WEIGHT: bold"
lang=EN-US>From:</SPAN></FONT></B><FONT size=2 face=Tahoma><SPAN
style="FONT-FAMILY: Tahoma; FONT-SIZE: 10pt" lang=EN-US>
GSBN-bounces@greenbuilder.com [mailto:GSBN-bounces@greenbuilder.com] <B><SPAN
style="FONT-WEIGHT: bold">On Behalf Of </SPAN></B>martin hammer<BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> 25 August 2010 02:50 PM<BR><B><SPAN
style="FONT-WEIGHT: bold">To:</SPAN></B> (private, with public archives)
Global Straw Building Network<BR><B><SPAN
style="FONT-WEIGHT: bold">Subject:</SPAN></B> Re: [GSBN] SB Overhangs (was Big
News!)</SPAN></FONT><SPAN lang=EN-US><o:p></o:p></SPAN></P></DIV>
<P class=MsoNormal><FONT size=3 face="Times New Roman"><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">Hi Graeme,<BR><BR>I’ll send you
the SB code off list.<BR><BR>Re: the overhangs, what do you do with
multi-story or tall walls? Do you have roof at typical first floor
ceiling height in addition to the upper roof?<BR><BR>I will definitely
consider putting such a table into the SB code. I saw Bruce’s vote of
agreement, and wonder if anyone else strongly agrees or disagrees that
overhangs be code-mandated for strawbale.<BR><BR>Overhangs are generally a
very good idea for SB, and I consider them “good practice” or “best practice”.
I don’t know if they are at the level of “minimum practice”, which is
typically the threshold of code language, although all of that is open to
considerable debate. Also in your table you account for wind as a
factor, but not rainfall. If your table were applied to desert climates,
it might be unfairly restrictive (although some desert climates receive
concentrated periods of rain).<BR><BR>In an earlier iteration of the code I
prohibited strawbale parapets, but for a few reasons decided to instead be
silent on the issue.<BR><BR>Martin<BR><BR><BR>On 8/24/10 4:11 PM, "Graeme
North" <graeme@ecodesign.co.nz> wrote:</SPAN></FONT><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">HI Martin<BR><BR>firstly my
congratulations -<BR><BR>and yes, I would really appreciate a word document I
can make comment on <BR><BR>>From my neck of the woods, one of the
overriding issues I encounter time and time again is that of good weather
protection from wind driven rain in our decidedly pluvian and humid climate -
something that gets skittered around in most books and references.
<BR><BR>I think we need a prescriptive starting point. In the NZ
Earth Building Standards NZS 4299 we relate wind zone. eaves height (vertical
exposed wall height), and roof overhang width to give MIMIMUM roof
overhangs as follows - <BR><BR><BR>Wind Zone - Ratio of eave
height to width<BR>Low (at ULS 32m/s) 4:1 (600mm over a 2400
wall)<BR>Medium (37m/s) 8:3 <BR>High (44 m/s) 3:2<BR>Very High
(50 m/s) 1:1 (or in other words a full
verandah)<BR><BR> <BR>We developed this table after leaks and
some degradation of material in some earthen structures and I can report that
there has been no reported problem since we adopted this. <BR><BR>It is
my contention that straw buildings are at least as moisture sensitive as
earthen buildings and I would suggest that this sort of table be regarded a
good starting point for calculating minimum roof overhangs for
direct-plastered external strawbale walls, a recommendation that could
possibly be worked back (or exceeded) after local weather or site assessment,
or possibly a service history of locally developed techniques.<BR><BR>It may
seem a but draconian to some but for my money the biggest problem with
strawbale buildings, in humid wet climates at least, seems to be that of
providing adequate primary weather protection, in the form of eaves, or rain
screening, and lack of good practical prescriptive guidance on this subject.
<BR><BR><BR>Comments
welcome<BR><BR><BR><BR><BR> <BR></SPAN></FONT><FONT size=1
face=Arial><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 9pt">Graeme (in bossy
standards writing mode) North<BR> <BR>Graeme North
Architects<BR><st1:Street w:st="on"><st1:address w:st="on">49 Matthew
Road</st1:address></st1:Street><BR>RD1<BR>Warkworth<BR>tel/fax +64 (0)9
4259305<BR> <BR>graeme@ecodesign.co.nz<BR>www.ecodesign.co.nz<BR><BR></SPAN></FONT><FONT
size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><BR><BR>On 23/08/2010, at 5:32
PM, martin hammer wrote:</SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">Everyone,<BR> <BR> Lars
Keller asked the below question so I thought I would answer to all in case
others are interested. I’ll set a deadline of September 30th for anyone
wanting to comment on the strawbale code as in the second draft of the
IGCC.<BR> <BR> Thanks.<BR> <BR> Martin<BR> <BR> <BR> On
8/22/10 9:36 PM, "Lars Keller" <larskeller@gmail.com>
wrote:<BR> <BR> </SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">Dear Martin,<BR> What is
the deadline for comments to you ?<BR> Best regards,<BR> Lars
Keller<BR> <BR> On 22 August 2010 03:36, martin hammer
<mfhammer@pacbell.net> wrote:<BR> </SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">Hello friends on the
GSBN,<BR> <BR> My voice has been conspicuously absent on this
subject, so I thought I would weigh in. <BR> <BR> First,
thanks for the words of appreciation. I was pleasantly surprised to hear
the news from David on Monday. I think this strawbale code document is
very good, but there are a number of reasons I didn’t think it would go
through to the next step. I thought both the Earthen Materials proposal
(referencing the recently revised ASTM standard that Bruce, David in earlier
years, and others worked so hard on) and the Straw-Clay proposal I co-authored
with Paula Baker-Laporte, had better chances. I might propose them again
in the upcoming Code Change Proposal phase (once IGCC committee concerns are
addressed).<BR> <BR> Much blood, sweat, and a few tears have gone
into this SB code since 2003, when I began writing it at the request of the
State of <st1:State w:st="on"><st1:place
w:st="on">California</st1:place></st1:State> (they asked Bruce, Bruce asked me
. . .). I’ve had very good input from others along the way, including
members of this list (David Eisenberg, Bruce King, Dan Smith, Bob Theis, Tim
Kennedy, John Swearingen, Bill Steen, Kelly Lerner) (apology if I’ve missed
anyone), and others not on this list, notably civil engineering professor Mark
Aschheim. <BR> <BR> Because it started as a <st1:State
w:st="on"><st1:place w:st="on">California</st1:place></st1:State> code, and
because there are great SB experts in northern CA where I live, the code might
be a bit California-centric (with particular attention to seismic issues).
However I’ve always wanted it to be broadly applicable and I welcome
broader, global input at this time. I expect to propose adjustments
during the next IGCC review phase. If it remains in the IGCC and goes
the way codes often do, some version of this might show up at your building
official’s door and then your strawbale door in Australia, South Africa, or
who knows where. And although I think there’s much to like, I can almost
guarantee you can find something you don’t like. So . .
.<BR> <BR> If you want to see and comment on the proposed code you
can ask me to e-mail the proposed SB code (by itself) to you as a word
document, and then e-mail me your comments or send it back with “track
changes”. <B><SPAN style="FONT-WEIGHT: bold">OR </SPAN></B>you can go to:
<U><FONT color=blue><SPAN style="COLOR: blue"><A
href="http://www.iccsafe.org/CS/IGCC/Pages/Comments0810.aspx">http://www.iccsafe.org/CS/IGCC/Pages/Comments0810.aspx</A></SPAN></FONT></U>
, and download all Public Comments under the “Complete Document” subheading
(Strawbale Construction is Comment #5-136). You can then e-mail your
comments to <U>me</U> (<B><U><SPAN
style="FONT-WEIGHT: bold">not</SPAN></U></B> to ICC). I’m also open to
comments on #5-134 Straw-Clay, and #5-135 Earthen Materials. If you want
to understand the IGCC process and schedule, you can go to: <U><FONT
color=blue><SPAN style="COLOR: blue"><A
href="http://www.iccsafe.org/cs/IGCC/Pages/PublicVersionDevelopment.aspx">http://www.iccsafe.org/cs/IGCC/Pages/PublicVersionDevelopment.aspx</A><BR> <BR></SPAN></FONT></U>In
addition, I want to clarify
that:<BR> <BR> </SPAN></FONT><o:p></o:p></P>
<UL type=disc>
<LI
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1"
class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">Strawbale is not yet in the
IGCC. That’s because it isn’t finalized (and SB could even be entirely
removed). </SPAN></FONT><o:p></o:p>
<LI
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1"
class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">Even if included in the final
version, the IGCC applies only to commercial and high-rise residential, AND
only in jurisdictions that adopt the IGCC. So it would have limited
application. </SPAN></FONT><o:p></o:p>
<LI
style="mso-margin-top-alt: auto; mso-margin-bottom-alt: auto; mso-list: l0 level1 lfo1"
class=MsoNormal><FONT size=3 face="Times New Roman"><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT> </LI></UL>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><BR> That said, this
approval is still a very good thing. And if it does make it to the
finish line of the IGCC, it would probably then migrate to the IBC in the next
code cycle, and then to a jurisdiction near you. I even see the
possibility of jurisdictions adopting it or informally using it for all
occupancies, even before reaching the IBC. John Swearingen’s report of
it already producing “instant results” for his project in <st1:place
w:st="on"><st1:PlaceName w:st="on">Stanislaus</st1:PlaceName> <st1:PlaceType
w:st="on">County</st1:PlaceType></st1:place> supports that notion, and is both
welcome and frightening. <BR> <BR> Finally, I want to acknowledge
David Eisenberg and Matts Myhrman who together forged the first SB code in
Arizona in the early-mid 1990’s, and to David again for speaking so
convincingly on behalf of the current proposed code at the recent hearing in
Chicago. If you read his description of what he said, you’ll see that he
simply told the compelling truth about the most relevant issues. It’s
one of many things David does so well. It’s nice when the compelling
truth prevails (at least for now).<BR> <BR> Thanks David, and thanks
to all. And thanks to the enduring spirit of
strawbale!<BR> <BR><FONT color=#888888><SPAN
style="COLOR: #888888">Martin<BR> <BR></SPAN></FONT>PS - For a pre-IGCC
history of this SB code, see my GSBN post on Dec. 1, 2009. Reviewing
that e-mail might also be used as a natural aid to help you fall asleep.
However, for me it is a riveting drama (sometimes moving at the pace of
a melting glacier . . . actually that’s happening quite quickly these
days!)<BR> <BR> <BR> <BR> <BR> On 8/16/10 10:13 PM,
"strawnet@aol.com" <strawnet@aol.com>
wrote:<BR> <BR> </SPAN></FONT><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><FONT size=5
face="Times New Roman"><SPAN style="FONT-SIZE: 18pt">Hello
all</SPAN></FONT>,<BR> <BR>I want share some great news. Earlier today,
here in <st1:City w:st="on">Chicago</st1:City>, Martin Hammer's
"comment"/proposal to include the strawbale code he’s been working on over the
past few years in <st1:State w:st="on"><st1:place
w:st="on">California</st1:place></st1:State> into the new International Green
Construction Code (IgCC) was approved by a committee vote of 8 to 6! The IgCC
is the new <st1:country-region w:st="on"><st1:place
w:st="on">US</st1:place></st1:country-region> code for commercial (and
high-rise residential) buildings that will become part of the family of 2012
International Codes (I-codes). It will go through a full code development
cycIe with the rest of the 2012 I-codes next year and there is work that will
need to be done still to make sure it doesn’t get rejected in that process,
but getting it into the second public draft of the code now is a very big step
forward. <BR> <BR> I served on the drafting committee for this
code from last summer through the spring of this year. For more information
about the IgCC and to download the whole IgCC first public draft and the
comments – including Martin’s proposals for strawbale and earthen building and
the EcoNest comment in support of straw clay go here:<BR> <A
href="http://www.iccsafe.org/cs/IGCC/Pages/default.aspx">http://www.iccsafe.org/cs/IGCC/Pages/default.aspx</A><BR> <A
href="http://www.iccsafe.org/CS/IGCC/Pages/Comments0810.aspx">http://www.iccsafe.org/CS/IGCC/Pages/Comments0810.aspx</A><BR> You’ll
find these listed as comments 5-134, 5-135 and 5-136.<BR> <BR> I was
the only proponent speaking in favor of it here, and there were others who
spoke in opposition. The initial motion was to disapprove but it failed 5
votes to 9 after considerable and very mixed discussion – which surprised me
because of the nature of some of the comments – that it was still not ready
and needed some technical fixes. <BR> <BR> The failure of the
motion to disapprove required a new motion and Chris Mathis, an old building
science friend from <st1:State w:st="on"><st1:place w:st="on">North
Carolina</st1:place></st1:State>, offered a motion for approval. That was
followed by more discussion, with more concerns expressed that it wasn't
ready. Then, just before the second vote, Chris pressed the committee to push
the envelope. He said they should approve it and get it in, and rather than
just having the few people who are very knowledgeable about it work on
improving the things that still need to be done, “Let thousands of people look
at it and help improve it through the next round of the code development
process!” He said it was time to start pushing these things through. Then they
voted - and it passed 8 to 6! I was amazed and delighted! So it is going into
the second public draft! <BR> <BR> There were two other
similar proposals (they’re called “comments”) that were heard right before the
strawbale comment. The first, from Paula Baker Laport and Robert Laport
proposed including the straw clay guidelines from <st1:State
w:st="on"><st1:place w:st="on">New Mexico</st1:place></st1:State>. Next was
the other submitted by Martin, that one in support of earthen construction
based on the new ASTM standard for earthen wall systems that I had initiated
almost 10 years ago and Bruce King has spearheaded over the past few years. I
spoke in support of both, but they were disapproved, though both received
encouraging suggestions to bring them forward again after addressing
non-mandatory/permissive language and other issues.
<BR> <BR> Because they were heard one after the other, and I
was the only proponent for them, I got to speak first for each one and so I
had a total of 6 minutes (2 minutes each) to frame them all in terms of the
big issues I’ve been speaking to for all these years, including the coming
challenges of ever-more limited and expensive energy, the low-impact,
low-tech, climate beneficial, local/regional benefits, the
industrial/proprietary bias and difficulty in funding research, testing and
development for public domain, non-proprietary materials and systems. I
started off by talking about the fact that I had been in buildings in
<st1:place w:st="on">Europe</st1:place> built with materials like straw clay
and earth that are twice as old as this country! And to say that these are
durable and safe ways of building when done properly. And when talking about
the ASTM earthen standard, I said that if they looked at it they might think
that it was too low tech to be reasonable compared to the standards that
they’re used to for concrete and other industrial materials. But, I said, It
was intentionally low tech. That I was involved in initiating that standard
almost ten years ago and it was both to enable the use of those materials here
and to reverse the outlawing of earthen building in developing countries
through the adoption of modern industrial codes. That it was designed to
enable people to build safe, durable, healthy, and affordable buildings
anywhere in the world—including the in <st1:country-region
w:st="on"><st1:place w:st="on">United States</st1:place></st1:country-region>.
I mentioned that the committee that developed that standard included the
leading experts on earthen building and engineering from around the world and
was based on reviewing and incorporating the best from international codes and
standards for earthen building. <BR> <BR> After the first two
went down, I was quite convinced because of the comments that the sb proposal
would share the same fate and, thankfully, I was
wrong!<BR> <BR> So hats off to Martin, Bruce, Matts, and many
others who have worked so long and hard to develop these codes and to Chris
Mathis for his leadership and visionary action on the committee.
<BR> <BR> Onward!<BR> <BR> David
Eisenberg<BR> <FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><o:p></o:p></SPAN></FONT></P>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><FONT size=2
face=Arial><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">
<HR align=center SIZE=3 width="95%">
</SPAN></FONT></DIV>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">_______________________________________________<BR> GSBN
mailing list<BR> GSBN@greenbuilder.com<BR> <A
href="http://greenbuilder.com/mailman/listinfo/GSBN">http://greenbuilder.com/mailman/listinfo/GSBN</A><BR> </SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><BR> <BR> _______________________________________________<BR> GSBN
mailing list<BR> GSBN@greenbuilder.com<BR> <A
href="http://greenbuilder.com/mailman/listinfo/GSBN">http://greenbuilder.com/mailman/listinfo/GSBN</A><BR> <BR> </SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><BR> <BR> </SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><BR> <BR>_______________________________________________<BR>GSBN
mailing list<BR>GSBN@greenbuilder.com<BR><A
href="http://greenbuilder.com/mailman/listinfo/GSBN">http://greenbuilder.com/mailman/listinfo/GSBN</A><BR> </SPAN></FONT><o:p></o:p></P>
<P style="MARGIN-BOTTOM: 12pt" class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></FONT></P>
<DIV style="TEXT-ALIGN: center" class=MsoNormal align=center><FONT size=2
face=Arial><SPAN style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">
<HR align=center SIZE=3 width="95%">
</SPAN></FONT></DIV>
<P class=MsoNormal><FONT size=2 face=Arial><SPAN
style="FONT-FAMILY: Arial; FONT-SIZE: 10.5pt">_______________________________________________<BR>GSBN
mailing list<BR>GSBN@greenbuilder.com<BR><A
href="http://greenbuilder.com/mailman/listinfo/GSBN">http://greenbuilder.com/mailman/listinfo/GSBN</A></SPAN></FONT><o:p></o:p></P>
<P class=MsoNormal><FONT size=3 face="Times New Roman"><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P></DIV>
<P>
<HR>
<P></P>_______________________________________________<BR>GSBN mailing
list<BR>GSBN@greenbuilder.com<BR>http://greenbuilder.com/mailman/listinfo/GSBN<BR></BLOCKQUOTE></BODY></HTML>