Latest Contributions by DevinLavigne

It would be great if attributes could be conditional - and remain hidden until some other condition is met. Take for example Holisticbynature Complete Streets Rule, if there were no bike lanes, then the attributes for bike lanes would be hidden or collapsed in the inspector.   ... View more

I don't know the exact number, but I feel like there are only about 10 undos, maybe less. Sometimes when I am writing CGA I have to make a more than 10 different changes throughout the code before I can test the results. The undos also only apply to the window or frame in focus - so that can get a little confusing. ... View more

I spend a lot of time browsing GeoNet, looking for help and seeing where I can help. I thought what might be missing was a place to share some completed work - showcasing how we are using CityEngine and to gather comments and critique by the group. So I thought I'd start one..... feel free to post thoughts, comments, suggestions etc. or shared your own CityEngine work. I've recently completed a project for a client - a redevelopment concept for a prominent 80-acre site occupied by an aging and outdated strip commercial site. I think the process I used was somewhat unique. The site plan was roughly sketched out with pen and paper, moving the primary building closer to the street, while reducing parking in favor of additional outlot commercial buildings. Opportunities for taller mixed-use buildings on the west side of the site were also suggested. The sketch plan was drawn out in SketchUp, and a simple 2D plan was color coded. I exported it as a KML and imported it into CityEngine. In CityEngine I simply applied my rules onto the color coded shapes created in SketchUp.  1. Aerial of the site - 80-acres at a prominent intersection of a regional corridor 2. SketchUp model imported into CityEngine as KML/KMZ 3. Color coding/rule explanation 4. Rules applied and linework on 5. Final CityEngine Exports ... View more

I'm running into something I can't wrap my brain around - I'm trying to split a street shape and it looks as though its adding in 4 extra meters - assuming its because of the default sidewalkWidthLeft and sidewalkWidthRight. This is complicating my splits a bit and when I look through the ESRI rules for streets I can't see where this is being accounted for. Am I missing something? Shouldn't this rule put in 4 equal splits between the sidewalks? The console reports 4 equal splits. lenAlongV = geometry.dv(0,unitSpace) ############################## #      Street @StartRule Street -->      print("Starting Street Width:" + lenAlongV)                                                        # Print Width                BuildStreet BuildStreet-->                split(v, unitSpace, 0) {'0.25:RandomColor print("Split Widths: " + lenAlongV)}*               # Print Split Widths            RandomColor-->                color(rand(0,1),rand(0,1), rand(0,1))                 Sidewalk -->      print("Sidewalk Width:" + lenAlongV)                                                            # Print Sidewalk Widths                     RandomColor‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ Instead I'm getting this ... View more