{"id":1483,"date":"2014-03-27T12:45:57","date_gmt":"2014-03-27T12:45:57","guid":{"rendered":"http:\/\/www.geoplanit.co.uk\/?p=1483"},"modified":"2014-03-27T14:01:15","modified_gmt":"2014-03-27T14:01:15","slug":"unexpected-consequences-and-the-power-of-instant-feedback","status":"publish","type":"post","link":"https:\/\/www.geoplanit.co.uk\/?p=1483","title":{"rendered":"Unexpected consequences and the power of instant feedback"},"content":{"rendered":"
\"ce_unexpected_consequences\"
Bridge Supports don’t go upwards…. (generally)<\/figcaption><\/figure>\n

Did I tell you I like\u00a0CityEngine<\/a>\u00a0today? \u00a0 Okay you will have noticed that CityEngine gives a designer an instant feedback on their rule files. \u00a0 You move a centre line of a road or a node on a building plot and the model created on top of it dynamically changes as it’s moved. \u00a0 \u00a0It’s fascinating to watch your simple rule files come alive.<\/p>\n

Take this example, it’s my attempt at really simplifying a street rule that includes a bridge element. \u00a0Above a certain elevation (either 0 or a terrain) and the street gets bridge supports and simple sides. \u00a0 Also no trees are planted and no zebra crossings (‘crosswalks’ to our North American friends) are created either.<\/p>\n

It works great, raise the road and supports are made, trees are taken out, just as I wanted but what happens if the road goes down… well have a look, I think I have some unintended consequences<\/strong> of a decision I made in my rule file…
\n