Latest Contributions by DavidWasserman

The short answer is yes I have. Specifically for shared streets/woonerf designs. Is it ok to incorporate some of these textures into the rule? Do I have permission to use them?  It is in a long to do list. If you want any particular features let me know, but I would not plan to necessarily make a street that could have existed in medieval times. That might be a separate rule.  ... View more

Understood. So there is a subcategory of building type that is reduced by some percentage?  Cheryl Lau's suggestions are good ones to use as a template. My only concern is the example you described might be a little more complicated if they are from independent shapes. There are not many examples for minimumDistance()  using inter shape logic, but the general idea should be the same.  My principle concern is unlike the scatter operation, the distribution of independent shapes exists already. You might need to experiment on how to set up a starting distribution for buildings.  ... View more

To clarify, you imagine the code to generate these houses will look like the following logic: case probability a house is created && house is not within 20 meters of another house:    generate house else:   no house (NIL) I want to review the rule, but this is easier if the houses are generated on the same shape. For example, vehicles are allocated on the complete street rule using a recursive allocation method shared by Matthias B. Something similar is needed here, but if they are different parcels you will need minimumDistance for a fact (target selector would be "inter", I think). The code for that depends  on the use of the label("thing") function. See the scatter example in the link above for a similar condition (red cylinders). My main concern is the distribution though. If they are independent shapes, controlling the order of generation and its implicit results on the final distribution of housing is not a clear cut thing. I imagine you might need to manually generate a few houses to set up a "init" results for start point distributions, similar to how various machine learning libraries give ways to set starting points for clustering resultings.  I am not an expert on minimumDistance, and it is a function I have read the documentation more than I have actually used. I like reading about it, have not had time to use it.  David ... View more

Hi Christina,  Glad you found it helpful!  If you use the tool in academic research or as part of professional reports, please cite the rule as the following: Wasserman, D. Feature Line Split. (2019) GitHub repository, GitHub https://github.com/d-wasserman/feature-line-split.  Thanks! David ... View more

These are great examples! Thanks! ... View more

Please share. I just want to take a look. I am curious if something could be done in a similar way with the minimum distance functions.  ... View more

Is it creating new shapes or moving the old ones? It almost looks like floating point precision error when it resets the the shapes...how small is this pipe? ... View more

L R‌ - Does the result change if you use?:  comp(f){all = X.} Even if so, that is weird. Are shapes translating? ... View more

This is one of the greatest things I have gotten to see in a while in a CGA thread. Regional (contextual) information being made locally available and relevant to the smaller parts. Can you share the code for this somewhere? Just this sample?  The planning implications of this are immense. You could in theory create dynamic land use mix entropy indexes. What a time to be alive... ... View more

I think I do...Something to remember about street shapes is that they dynamically segment themselves technical when exposed to curves. As a result, it is typically recommended to stick to UV based operations (insertAlongUV changed much of what was possible in the Complete_Street.cga rule for this reason). However, images help tell this story. I applied the TOD.cga rule in the Land_Use folder of the Complete Street repo linked above to three different streets, each manipulated differently. Notice how, the curved non-straight street broke multiple times based on the shapes articulations. Instead of one building, I have dozens. You can see how the complete street rule by comparison is depending on inserted shapes/models, simple extrusions, and textures.  Based on this you have a few options:  1. Keep the street shapes as straight as possible. Remove all curves from the geometry.  2. Use insertAlongUV with predesigned shapes/3D models. It is possible the envelop operation is not what we want here.  3. Something else. There are likely other ways to set up the shape. It might work now, but previously the comp operation (= vs. : - see the operator), did not work on street shapes to consolidate this segmentation behavior into one shape. It does create headaches. For example, if you can insert a thin base using the insertAlongUV operations, then component split the top of that shape with a = operator...it might keep it in one shape. However, in my experience, the envelope operation is very sensitive to starting geometry (I still don't have raised crosswalks for this reason.) . Street rules are like programming on shifting sand.  ... View more

That makes sense. Generally, I would recommend sticking to one or the other. It can be really difficult to get them to play nice.  ... View more

Did you install Geopandas in a separate environment? I have had success with Geopandas and Arcpy coexisting but I do so in separate environments. I can share a requirements file if it would help.  ... View more

Chris Wilkins‌ beat me to it with his time zone related superpowers.  I agree with Chris that a UV approach is more likely to work for this. My concern is whether we can get it properly align with the current polygon shape (we likely could for most of it). I think I have a few pre-processing suggestions that might make a rule to do this simpler.  1. Break up the polygons based on their nearest vertex joints- if you split it so that each shape is "roughly" rectangular, it would be easier to get an alignment between shapes. This might be difficult.  2. Represent the polygon as a street - A street can accommodate the curves desired more appropriately, but requires representing the polygon as a polyline for import.  I am sure there is a pure CGA around this, but it might require some smart calibration of the UV space and subsplits to provide exactly what you are looking for.  ... View more

I guess my question is there are two types of "parcels" or "lots" in CityEngine. One generated by outlines of roads, and those imported. I guess my question is how this applies to imported parcels and how one might go about orienting their edges for these operations.  ... View more

Got it. Only on parcels CE generates or also can be associated with a first edge operation?  ... View more