|
DOC
|
Absolutely. Please let me know if you have any issues with some of the new features or have ideas for new ones. I am trying to be conservative on changes and focus on usability of the core functions. I might make a "Simple" version in the future that has a lot of extraneous attributes hidden.
... View more
10-01-2015
04:07 PM
|
0
|
0
|
42676
|
|
POST
|
Hey Aida, On the rule portion can you share the CGA rule in question? For flat roofs, I usually comp the top shape, then do a setback to create a "roof edge" that I can further manipulate. So once you make that edit, you could make something similar with a setback that you then split so that you can create alternating extrusions up. Similar to the Interweaved Repeat split in the documentation page here. As far as curb extensions, the guide I wrote is the best advice I have for curb extensions. If you add those nodes to the streets, you just have to alternate changes in Street and Sidewalk Width parameters to create the effect of the curb extension. I hope this helps. David
... View more
10-01-2015
01:54 PM
|
0
|
7
|
4102
|
|
DOC
|
Hi Geonet, So after the first iteration of the Complete Street Rule I developed as part of ESRI Redlands I started working on a personal version of the rule I have decided to share because of how useful I found some of the changes. The rule being shared is a derivative work of the Complete Street Example released by ESRI Redlands. Background: What is the Complete Street Rule? "Complete Streets is a robust procedural street example that incorporates knowledge and ideas from various sources of transportation planning knowledge including NACTO Design Guidelines, AASHTO Design Recommendations, and MUTCD standards. The goal of the rule is to represent a diversity of street configurations to support multimodal planning in urban areas, and provide some basis for before and after comparisons of street treatments and transportation investments in CityEngine. Along with visualization, the street rule includes analytical reports on various aspects of the geometry of the street that can be used to inform rough cost estimates. In addition to these analytics, the street rule has various customizable thematics and reports that use information from the geometry and configuration of the street to suggest how it might impact the "stress levels" put on different modes. The street rule intends to represent transportation planning treatments for complete streets within urban areas and common highway configurations that might include shoulders, Jersey barriers, and HOV Lanes."- ESRI The Github link here has a simple project that has the updated rule. You really only need the CGA rule because the assets for the rule have not changed yet (in the future they might). The version of CityEngine the rule is compatible with starts with 2014.1, and then varies by release on GitHub. Quick Download Link for the project is here: https://github.com/d-wasserman/Complete_Street_Rule/archive/master.zip Download the project or just the rule on Github here: d-wasserman/Complete_Street_Rule: This i... - GitHub Documentation for the rule can be found here: Complete Street Rule Documentation & User Guide.pdf Previous Feedback posts on the rule can be found here: Esri Complete Street Rule Discussion-Feedback? Webscene Using Rule with Recent Changes: LTS Visualization Please provide feedback if you have any. Tags: CGA Rule Library, Transportation, 3D
... View more
10-01-2015
01:29 PM
|
13
|
51
|
60616
|
|
DOC
|
Hi All, I got inspired by an Arcpy Cafe post to develop a tiny scripting tool that takes an existing polyline feature layer and proportionally splits into a desired number of segments of equal length. This scripting tool will enable you to do batch editing based on either an input field or just split all the lines into segments of equal length. This tool WILL attempt to copy the fields from the original feature class. I have since changed these tools so that they include more editing tools to assist with generating linear study geometries generally. These tools include: Feature Line Split - create a new feature class that has input lines split into an arbitrary number of segments. Feature Line Pull - create a new feature class that has input lines split pulled back a target length. Feature Line Whiskers - create a new feature class that perpendicular lines generated based on the sampled headings of the input polylines. Feature Line Corridor Assembly - will add corridor ids to an output line network for all lines that are parallel within a tolerance and spatially connected/contiguous. For more info see the links below: Github Repo for the tool is here: Download Link GitHub - d-wasserman/study-line-editor: The goal of this toolbox is provide a set of batch line editing tools for ArcGIS…
... View more
09-20-2015
06:04 PM
|
5
|
16
|
11674
|
|
POST
|
I was seriously thinking about doing something like this! Nice!
... View more
08-25-2015
11:32 AM
|
0
|
0
|
1110
|
|
POST
|
Hi Chad, I actually had to deal with something similar. I guess my main question is what progress did you make either the eliminate tool? It sounds like that is what you want to do in the sense it might allow you to query/exclude specific fields. Is the area issue the concern? David
... View more
08-24-2015
07:31 PM
|
0
|
2
|
3779
|
|
DOC
|
Hi All, I made a quick scripting tool that I thought I would share. The scripting tool will take a feature class, its fields, and a new target value as inputs. Where ever a Null value exists (None), the value will be set to the target value. The target value default is of numeric type and is set to 0. This tool has to be used understanding what your field types are, the tool will try and set the target field to the desired value with an update cursor, but will pass that row if it cannot. Only "None" values are changed, all other values should be left alone. It is really simple, but might be helpful. I am not sure something like this exists (I know it does for raster but not for fields). You could accomplish the same with a "calculate field", but this allows multiple fields if you need it for a lot of fields. David
... View more
08-21-2015
09:33 AM
|
0
|
2
|
3715
|
|
POST
|
Hey Valerio, I took a look at the rule briefly. The first extrusion seems to align the geometry to the longest edge. However, can you try first edge setting just in case. That should be the right command, and don't worry CityEngine takes a while to learn. It is just like any new software. David
... View more
08-19-2015
09:32 AM
|
0
|
0
|
1953
|
|
POST
|
Hey Valerio, Can you post a link to the rule you used? Is it in Esri.lib? Have you tried setting the first edge on the shapes you are using? http://cehelp.esri.com/help/index.jsp?topic=/com.procedural.cityengine.help/html/manual/is/manually/manipulating.html David
... View more
08-16-2015
05:12 PM
|
1
|
2
|
1953
|
|
POST
|
It seems the sidewalk and planting textures are clashing though.
... View more
08-13-2015
09:55 AM
|
0
|
1
|
462
|
|
POST
|
Hey Veronica, What version is the original Scene? Are you using 2015.1 to open a 2014 scene? Do we have a resulting polygon count from this? Did you run a shape clean up before model generation? (I am just curious if the fact the original data was CAD might influence vertex/polygon count. Don't know for sure). I have seen errors similar to this in ArcGIS where I had to give more memory to Arc from my OS/or change internal Arc settings. Matt has explained before that CE uses Java and C++ and both have their own memory allocation. Maybe it is an Install issue... Have not ran into this before in CE, so I am just thinking of questions. David
... View more
08-07-2015
09:58 AM
|
0
|
1
|
2290
|
|
POST
|
I know this is old, but I think it is link I sent you in the other thread. 😃 I think you are already past this though. I just want to share it for others who find the thread. Under Manual Shape Editing: http://cehelp.esri.com/help/index.jsp?topic=/com.procedural.cityengine.help/html/manual/is/manually/intro.html I think it is shape manipulation link here though that discuss the clean up shapes tool. -http://cehelp.esri.com/help/index.jsp?topic=/com.procedural.cityengine.help/html/manual/is/manually/manipulating.html
... View more
08-06-2015
09:11 AM
|
1
|
1
|
1898
|
|
POST
|
I guess what is confusing me is that I thought when imported they start as static models, and as part of the process you converted them to shapes, then applied a rule to make a rule based model in CE. I was just using the word casting trying to understand if you were molding one type of object into another with a rule application. It sounds like any rule would work for this purpose. I did some experimentation and came up with this image. The raw DAE model does not have the lines (static model), converted to shapes does, but when the rule is applied and sent to X. it also does not have the lines but also is a little different (likely just a result of certain shapes being sent to white blank leafs). It the three combinations that is a little confusing. Thanks for the help Chris! It makes a little more sense now.
... View more
08-06-2015
07:27 AM
|
0
|
0
|
696
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 06-07-2024 02:16 PM | |
| 1 | 05-15-2022 12:21 PM | |
| 1 | 08-27-2016 11:03 AM | |
| 1 | 12-19-2021 01:10 PM | |
| 1 | 06-12-2020 03:29 PM |