Latest Contributions by TalAisenberg

I've just upgraded to 2012, then first thing was to open the project I'm working on. For some reason all the mapping layers I've had working on 2011 don't seem to work in 2012. The 'inspector' lets me select 'by layer attribute' and let me pick from the list the right attribute but then the value assigned is just 0 (zero). My model uses mapping quite extensively both for block and shape creation parameters. Now I can't run my model and bit stuck. My mapping layers pick one colour of 27 off my colour chart (attached) and selects the corresponding number based on the range it is in (so everything similar will be assigned to the nearest value), the 'inRange' routine does that. Here's a sample of my mapping layer code: // map red[0..1] to aRed[0.0...1.0] attr aRed = map_01(red, 0.0, 1.0) // map blue[0..1] to aBlue[0.0...1.0] attr aBlue = map_01(blue, 0.0, 1.0) // map green[0..1] to aGreen[0.0...1.0] attr aGreen = map_01(green, 0.0, 1.0) inRange (input, range) = case abs(range-input) < 0.25 : true else : false attr type =   case inRange(aRed, 0) && inRange(aGreen, 0) && inRange(aBlue, 0) : "Offset Subdivision" //1 case inRange(aRed, 0) && inRange(aGreen, 0.5) && inRange(aBlue, 0) : "No Subdivision"  #2 case inRange(aRed, 0) && inRange(aGreen, 1) && inRange(aBlue, 0) : "Offset Subdivision" //3 case inRange(aRed, 0.5) && inRange(aGreen, 0) && inRange(aBlue, 0) : "Recursive Subdivsion" //"Offset Subdivision" //4 case inRange(aRed, 0.5) && inRange(aGreen, 0.5) && inRange(aBlue, 0) : "Recursive Subdivsion" //5 #industry case inRange(aRed, 0.5) && inRange(aGreen, 1) && inRange(aBlue, 0) : "Offset Subdivision" //6 case inRange(aRed, 1) && inRange(aGreen, 0) && inRange(aBlue, 0) : "Skeleton Subdivision" //7 case inRange(aRed, 1) && inRange(aGreen, 0.5) && inRange(aBlue, 0) : "Skeleton Subdivision" //8 case inRange(aRed, 1) && inRange(aGreen, 1) && inRange(aBlue, 0) : "Offset Subdivision" //9 case inRange(aRed, 0) && inRange(aGreen, 0) && inRange(aBlue, 0.5) : "Offset Subdivision" //10 case inRange(aRed, 1) && inRange(aGreen, 1) && inRange(aBlue, 0.5) : "Skeleton Subdivision"  #18 case inRange(aRed, 0) && inRange(aGreen, 0.5) && inRange(aBlue, 1) : "Offset Subdivision"  //20 case inRange(aRed, 0.5) && inRange(aGreen, 0.5) && inRange(aBlue, 1) : "Offset Subdivision" //23 case inRange(aRed, 0.5) && inRange(aGreen, 1) && inRange(aBlue, 1) : "Offset Subdivision" //24 case inRange(aRed, 1) && inRange(aGreen, 0) && inRange(aBlue, 1) : "Offset Subdivision" //25 case inRange(aRed, 1) && inRange(aGreen, 0.5) && inRange(aBlue, 1) : "Offset Subdivision" //26 case inRange(aRed, 1) && inRange(aGreen, 1) && inRange(aBlue, 1) : "Offset Subdivision" //27 else: "No Subdivision" //0 I've doubled check that the image is still there and that its within the graph boundaries. I've tried to create a NEW mapping layer which seem to work but I've tried with a static assignment: attr type="Recursive Subdivsion". Is it possible that we can not anymore use routines within mapping layers Any ideas ? p.s. did anybody notice the typo in the 'Recursive Subdivsion' ??? - its missi ... View more

Hi, Currently we are using the standard method of terrain - a mapping layer coupled with a texture one. Problem is the topography is far from accurate. We usually get the contours from CAD so they are very accurate, then we need to translate it into raster which less so and into CE which in turn gives really strange results. I've attached a photo to show how contours (which are on the underlying texture) are quite different from what the terrain is doing. (contours should be flat on the surface as are supposed to be equal-elevation) Is there a way to use the innately accurate CAD contours instead of a map layer ? We can also convert that into a surface via Civil / Sketchup or other applications if need be. Cheers T ... View more

Hey, Is there a way to store a value at some point in the code so I can use it later - for example: I want to determine a building's height based on the plot size and its footprint (in order to get my FAr right). So I need to: 1. Measure the plot - geometry.area and save it 2. create the building footprint with ShapeL (or offset / ShapeU....) 3. now calculate based on a target FAR the height of the building (FAR = plot area / (footprint * no. of stories)) 4. extrude the building to the required height Its just that once I've done the shapeU operation I cannot go back to read the plot area as geometry.area(bottom) will now give me the building footprint. I tried with assigning the value to a new attr on the Lot rule (just before I divide them) but this doesn't seem to work. Cheers T p.s. working with really tedious urban planners - you know how they can sometimes be 😐 ... View more

a measure / dimension tool would be much appreciated - currently need to export to CAD, then measure... surely this is an easy one. Cheers T ... View more