{"id":2897,"date":"2015-03-15T13:02:07","date_gmt":"2015-03-15T13:02:07","guid":{"rendered":"http:\/\/www.geoplanit.co.uk\/?p=2897"},"modified":"2015-03-15T13:30:18","modified_gmt":"2015-03-15T13:30:18","slug":"cityengine-and-bank-barns-built-heritage-meets-geodesign","status":"publish","type":"post","link":"https:\/\/www.geoplanit.co.uk\/?p=2897","title":{"rendered":"CityEngine and Bank Barns? Built Heritage meets Geodesign"},"content":{"rendered":"
\"BankBarns_01\"
Variant versus True Bank Barns in CityEngine??<\/figcaption><\/figure>\n

\u00a0Imagination<\/em><\/strong> is required to use CityEngine, I’ve said this before and I say it a lot in our 3DPathFinder CityEngine training sessions<\/a> (shameless plug). \u00a0 The power of the rule file is in it’s ability to be used in other contexts and is often only limited by your imagination. \u00a0Some of what I think Geodesign is also about this, connecting up other peoples workflows, joining disciplines together to form a coherent team.<\/p>\n

Take the humble rule that places a parapet around a roof top and places a satellite dish inside, this is the same rule that I use to make my infamous “procedural sheep”. \u00a0Get your head around that and the world is yours (in a metaphorical sense).<\/p>\n

\"procedural_sheep_esiruc_01\"
What do you mean you haven’t heard about my Procedural Sheep??!<\/figcaption><\/figure>\n

 <\/p>\n

This leads me to a little rule file I adapted yesterday, my colleague and friend Matthias<\/a> had created a couple of rule files for a client (Philadelphia University’s Geodesign course<\/a>). \u00a0One rule file coloured a surface depending on the steepness of a slope, which clearly when drawing a path or a road can be useful. \u00a0The other rule file was one that placed arrows facing down a slope in a grid pattern, think about water run-off and this is cool, useful stuff. \u00a0<\/p>\n

<\/p>\n

I\u00a0often say CityEngine doesn’t do analysis<\/strong>, it is far better to\u00a0process\u00a0and analyse data first before bringing it in to CityEngine. \u00a0 However, having CityEngine providing constantly updated visualisations of design iterations is analysis, and the best thing is it only adds to my design without getting in the way (i.e. stopping my design, exporting it and analysing in ArcGIS, then re-importing it).<\/p>\n

My wife is our heritage specialist at Garsdale Design<\/a> and is often at the records office researching old buildings and barns as part of a clients planning application process. \u00a0 One of the things that will be talked about is ‘bank barns’ and there is a key text you might like to read about them\u00a0(The Bank Barns of Cumbria<\/a>\u00a0[PDF]). \u00a0Anyway I thought it would be fun to use CityEngine to place barns on a hill slope (call this historical Geodesign<\/strong> maybe?). \u00a0 First there are main types\u00a0of ‘bank barn’ but we can boil it down to two basic types “True Bank Barns” and “Variant Bank Barns” basically\u00a0there are lots of variations in layout but the two main differences are direction that a barn is orientated to a hill slope.<\/p>\n

\"BankBarns_04_extract_figure3\"<\/a>
Click to download the original document<\/figcaption><\/figure>\n

 <\/p>\n

True Bank Barns –\u00a0Doors in sides (up or down) slope, and can be on level ground<\/p>\n

\"BankBarns_05_extract_figure5\"<\/a>
Click to download the original document<\/figcaption><\/figure>\n

 <\/p>\n

Variant Bank Barns – At right angles to the slope, only downhill end of barn is two storey. Doors in the gable end.<\/p>\n

So I boiled this down into two basic types orientate with the contours and those at right angles to the contours of a hill. \u00a0 What I needed was a way of visualising and assessing hill slope and of orientating an object based on the hill slope. \u00a0 It’s a good job Matthias had already done most the work for me! \u00a0 Here were his rule file outputs:<\/p>\n

\"BankBarns_07_Matthias_Street
The yellow indicate steeper slopes<\/figcaption><\/figure>
\"BankBarns_06_Matthias_Arrows\"
Difficult to see but trust me the arrows point down hill…<\/figcaption><\/figure><\/p>\n

 <\/p>\n

So I took these two rules and combined them, instead of an arrow I created a simple barn shape, I added a switch to change the orientation of the ‘Bank Barn’. \u00a0Matthias’ rule already had a way\u00a0to change the grid size so I just adjusted the default value to something that made the barns created further apart. \u00a0I’m pretty happy with the outputs as you can see below:<\/p>\n

 <\/p>\n

\"BankBarns_01\"
True Bank Barn on left and Variant Bank Barn on right..<\/figcaption><\/figure>\n

 <\/p>\n

 <\/p>\n

Now a nice animated GIF to show you just how dynamic CityEngine really can be!\u00a0<\/p>\n

\"BankBarn_Demo_01\"<\/p>\n

 <\/p>\n

\u00a0Where does the geodesign<\/strong> come in to this? Well, this is about creating a historic environment in 3D that takes various variables and some analysis in to account, my next step would be to add a tree line and perhaps add some change based on elevation. \u00a0 I would also want to actually make the barn look a little more realistic as well, something that can easily be done in CityEngine. \u00a0 I’m thinking of creating various barn models that can be varied to look like those illustrations in the Bank Barns of Cumbria document<\/a>\u00a0[PDF].<\/p>\n

To summarise I’ve said it before and I’ll say it again, don’t think of CityEngine as just about cities perhaps it would be better called ImaginationEngine? Okay no that’s a terrible idea.<\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

\u00a0Imagination is required to use CityEngine, I’ve said this before and I say it a lot in our 3DPathFinder CityEngine training sessions (shameless plug). \u00a0 The power of the rule file is in it’s ability to be used in other contexts and is often only limited by your imagination. \u00a0Some of what I think Geodesign […]<\/p>\n","protected":false},"author":161,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[93,275,12,145,261,156,7,37,1,9],"tags":[277],"class_list":{"0":"post-2897","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-3d","7":"category-3dpathfinder","8":"category-arcgis","9":"category-cityengine","10":"category-garsdale-design","11":"category-geodesign","12":"category-gis","13":"category-heritage","14":"category-uncategorized","15":"category-workflow","16":"tag-3dpathfinder"},"_links":{"self":[{"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2897","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=\/wp\/v2\/users\/161"}],"replies":[{"embeddable":true,"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2897"}],"version-history":[{"count":5,"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2897\/revisions"}],"predecessor-version":[{"id":2925,"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=\/wp\/v2\/posts\/2897\/revisions\/2925"}],"wp:attachment":[{"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2897"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2897"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.geoplanit.co.uk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2897"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}