Latest Contributions by SóniaIldefonso

I got the same problem. I created an OBJ from Graphisoft ArchiCAD software and now I'm trying to import it into CityEngine. The textures don't show up... ... View more

Hello Matthias, did you solve this? ... View more

We're familiar with Ecotect here. Not yet the combination workflow. ... View more

Hello Chris, thank you so much for the quick answers. I've located with Bo Rodda indeed. I got their point in the LakeSIM Project and I checked some information about their energy modeler tool. What do you think about the CityEngine to Ecotect workflow approach? It seems to be an obvious solution... isn't it? Thanks, Sónia ... View more

Coming back to this issue again... I've gone through it carefully Matthias. Now I have streetWidth() attributes in my footprint shapefile. I'm able to use the selector street.front to generate street facades. The next question is: Can I generate different facades (footprint shapefile) according to an attribute value which has been set within the streetNetwork shapefile ? Footprints are static and "real" street width value is not available in my original streets shapefile (that's why it's getting the default 8). I was wondering... Can I use Layer Attribute (Street Network shapefile) as a source for Street_type attribute within the footprint shapefile ? -------------------------------------------- Facade --> case Street_type == "Main" :    FacadeA case Street_type == "Path" :    FacadeB case Street_type == "Boulevard" :    FacadeC else : NIL -------------------------------------------- This is not working... Thanks ... View more

Thanks again for the answer Matthias. As you've already noticed, I'm trying to reproduce an existing downtown which is very specific and strictly designed... and I'd like to do it by using rule-based modeling as much as possible so that I don't lose data. This is my main goal. About case 5: You told me to add a ShapeL() to the footprint before I extrude it, right? Is it possible to get footprint dimensions (width / depth) and use them as shapeL parameters as it follows? ---------------------------------------------------------------------------------------------------- attr footprint_depth = ? //based on the footprint, variable attr footprint_width = ? //based on the footprint, variable Lot --> shapeL(footprint_depth - 0.1, footprint_width - 0.1) {shape : BuildingFootprint | remainder : NIL} ---------------------------------------------------------------------------------------------------- *(-0.1) to minimize the void (not built). May I add this operation only to the roof in order to maintain the floors (area)? How to control the L shape orientation (right / left corner)? In order to solve the other cases, I'll try to check the combining polygonal modeling with rules process... Then I'll come back with more questions. Sorry for the "silly" questions. Thank you so much for your help. ... View more

Thank you so much for this useful thread, Matthias! I'll go through it carefully. I really have a lot to learn about CE... Best regards. sildefonso ... View more

Hello everybody. I'm a CityEngine beginner and this is my first time here. I found Avgi's question interesting as I'm facing a very similar problem. Even though I run through the tutorials, I'm not able to solve this issue... So, let me try to make it plain. I have a SHP file of building footprints and another SHP file of streets which I imported into CE. After the footprint extrusion, I use the component split in order to get the facades. In fact, I'm quite interested in main facades (the street-facing components). As footprints and streets don't interact dynamically (in the current case), I can't use the selector street.xxx to set the faces I want to use as main (or front) facades. As you can see (left side of the image - attachment file), whether I use front, side,etc or object.front, object.side,etc selectors, it doesn't work. It has to do with the different object coordinate system, right? Despite that, I have a second goal. I want to classify main facades according to the different street types (A,B and C). Then I tested the following workflow: 1. In order to set different main (or front) facades, I added a new object attribute to the original shapes called "BuildingType". The possible values are: StreetFront_north StreetFront_east StreetFront_south StreetFront_west Corner_northeast Corner_southeast Corner_southwest Corner_northwest and BlockFront (to the 4 quadrants). 2. Then I used the world.xxx selectors to get only the facades that correspond to the assigned buildings orientation. I gave them different colors so that I made it clear. The X faces are represented as black.  ---------------------------------------------------------------------------------------------------------------- Building(BuildingType) --> case BuildingType == "StreetFront_north" :   comp(f)    {world.north:N | world.west:X | world.south:X | world.east:X} case BuildingType == "StreetFront_south" :   comp(f)    {world.north:X | world.west:X | world.south:S | world.east:X}         (...)         else: NIL ---------------------------------------------------------------------------------------------------------------- As you can see at the right side of the image, the result is not perfect yet. Some faces of both corner and top buildings of the block have been generated as main facades too because there are more than one facing the same quadrant... And I even didn't classify the facades according to the street type yet... The next step would be adding a second new object attribute to the original shapes called "streetType" whose values differ between three values (A,B,C) so that I can call the right facade shape to either N, E, S and O previously generated shapes. So... I was wondering... there must be a simpler way of doing this! Would you give me some clues, please? Thank you. Best regards. Sónia I. ... View more