Latest Contributions by DavidWasserman

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

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

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