Latest Contributions by romainjanil

Hi, I guess I'm behind this video so may be I can help a bit. Generally speaking you can leverage adjacency (occlusion) test everywhere if you build relevant labeled shape proxys beforehand (but not parent nor children) in your shape tree. In this regard you can also use some comp(f,e etc) functions that will query occlusions tests so you can then grab subsequent indexes to feed operations that work with arrays of index as input . roofRidge doesn't but you can set the scope aligned to a specific edge before. To get this edge, use comp(fe) before with some other tests to get:- the edges which are not side, nor overlapping the labeled mass of some other building (or even finer labeled mass of the walls), their length, then rank them per length in order the longest edge (or whatever else not adjacent/inside/overlapping another building or wall), then set the scope you're applying the roofRidge onto to this index. If you need further hints feel free to contact me directly.  ... View more

.cgb is purposefully binary of .cga hence is not editable ... View more

Hi Jonas, yep I don't know if this is possible and what core design implications it may have. basically it would be similar to dynamic (g) selector for all available components. Thanks ... View more

Indeed, this is a long asked feature probably already in esri's backlog. This would also allow direct use of double parallel street segments coming from OSM or other, when constructing complex median ways and intersections... ... View more

indeed longtime wish 🙂 ... View more

combination of set() setElems() and with are indeed the way to go for this kind of stuff. You can do a lot of geometrical calculation in some kind of loop, iterating on the initialShape, storing calculated values in arrays trough comp(), sets feeding arrays, incrementing, resetGeometry and eventually exit the loop when condition are met ... View more

HI , no unfortunately, it's impossible to catch those pure geometrical error at the moment, as I said derivation stops and leaves rule geometry -as is- as a terminal leaf. No matter what you code after. This is a very special tricky usecase, I should probably package an exemple.  ... View more

Hey, totally forgot this is already implemented in comp !thanks for the reminder ! ... View more

tons of, first is comp(e) from for shapes coming from envelop() which are not regular roofing operation hence do not really support hip/ridge/valley etc selectors (everything falls in ridge) 2- for more easy identification (and further derivation) of corners between faces (ie from a concave A rectified shape to insert instanced rounding: A-->extrude(3) comp(f){side=B C} B-->comp(e){concave:ConcCorners|convex:ConvCorners} ConvCorners-->i(assetForCorner("conv")) ConcCorners-->i(assetForCorner("conc")) 3, insert some proxy labeled shapes going to NIL against which other part of a facade could test so to get smarter generic adaptative facade patterns (avoid balconies in corners, or the contrary etc) many many use cases I think and ti's very generic. Best Romain   ... View more

cool ... View more