Latest Contributions by DavidWasserman

Oh...have not looked at that code in a while...ermm...I guess you could  modify the median so that it looked that way... I can look into it. Now that you mention it...that should be a thing. ... View more

Looks awesome. 😃 As specified in the documentation, you can remove trees by setting "Tree Percentage" to zero. The Official Unofficial Guide to the ESRI Complete Street Rule.pdf ... View more

Need feedback on it, but just keep in mind major modifications are out of scope for what I want to do with this feature. Thanks David ... View more

Hi Wendell, Please see the most recent rule here. This was actually a feature I tried to add a week ago...It really looks good on single cross sections and does not deal with joined streets very well. GitHub - Holisticnature/Complete_Street_Rule: This is an updated repository for a modified version of the ESRI Complete … Go under Bicycle_Lane_Type--> Sidewalk Then width added to bike lanes only applies to sidewalk side bike lanes. I added this to give a starting point to anyone who wanted to take the concept further...I have realized internationally this is one of the biggest asks of my rule. I have at least 3 different people from 3 different countries ask me for this feature at this point. David ... View more

Hey Wendell, Generally when I want to do this, I copy paste the street segment in question and then move it to the side to be parallel to the same street, then change the settings till I get a trail like this one. I can investigate making a version that does this, but are you trying this work flow I mentioned above now? David ... View more

I would also consider using the "Add Field Delimiters" function. It makes sure you have appropriate delimiters for your SQL queries. AddFieldDelimiters—ArcPy Functions | ArcGIS for Desktop Example: GeodesignToolkit-GIS-CityEngine-Integration-Tools/SplitFeaturebyAttribute.py at master · Holisticnature/GeodesignToolkit… def constructSQLEqualityQuery(fieldName, value, dataSource):     # Creates a workspace sensitive equality query to be used in arcpy.     return "{0} = '{1}'".format(arcpy.AddFieldDelimiters(dataSource, fieldName), str(value)) ... View more

Hey Kenneth, I am go to generalize this post for street imports generally, but also include some OSM specific thoughts. The short answer is this: CityEngine's street clean up tools are limited in scope and power. Keep in mind the graph tools were meant to create logical shapes so that the network resembled the city in question in large scale renderings (think Zootopia/Big Hero 6). Neighborhood scale cross sectional design scenario work that might be done with the Complete Street Rule can be hard for the tools to meet the intended need. My general thought process as of late is to do two separate things: Do More Data prep IN GIS: This includes tools like Simplify Line (vertices cause street shapes breaks), Smooth Line, Snap, Point to Line, Topology Tools, and combinations in between. For example, if you can identify intersections and key points of directional change in your line network, you can simplify it, use vertices to points, do querying to isolate bad intersections and then turn it back to lines in a logical fashion you choose. In addition, if you can determine angle of intersections, you can put as  a mapped attribute the shape parameter you want. I experimented on a few occasions to test smart model joining, and the results are pretty good for similar segments (General rules being: if it has more than 5-6 legs at an intersection, make it a round about, if the angle of intersection is high, make it a freeway/junction, everything else looks best as crossing NOT Junction- makes intersections more compact with predictable behavior). A lot of problems can be dealt with with preprocessing shape parameter attributes in GIS. An overview of the Generalization toolset—ArcGIS Pro | ArcGIS for Desktop Repair Geometry—Data Management toolbox | ArcGIS for Desktop Try A Record Based Approach: The idea behind the CityEngine toolkit is to reject the geometry given to us entirely and focus entirely on the narrative of the records I am working with. I call this Narrative Tiling, because to some extent the issue comes down to problems of scale not in creating content, but sharing it. Specifically, I feel this approach makes digesting information more accessible because you only have to focus on one block/street at  a time. Imagine a web map where people click on individual symbolized streets in a Vision Zero (accident safety) study, and when they click on a link a pop up to a web scene of that individual streets improvements appear. This method of operation does two things: reduces load time on large scenes, isolates needed content to the narrative related to a particular asset. This only works on projects where it the story can be tied together by a web map looking at a network scale/city wide scale (data is relevant to a larger story), but the web scenes/infographics created supplement and drill down into the details. The added benefit of this is that there is almost no time spent on geometry clean up (past dissolving up to the records you want). Geodesign Toolkit: CityEngine-GIS Integration Tools OSM Thoughts: Generally, OSM even from GIS ready sites likes Metro Extracts​ is TAG based. This means there are hundreds and hundred of fields, each with a record that relates to what that record is. It is a pretty intense data set that requires cleaning for a variety of issues related to coverage, topology, and attributes. Even in network analyst, OSM data often requires some degree of clean up before even being considered close to routable. In addition, sometimes OSM does not provide much information about the street so it is hard to get a consistent image of what the world's streets look like. I will reply to your listed questions in an earlier email below: 1.      The import street only works well, if it is a very simple network. 2.      A boulevard drawn as to lines, needs to be deleted and recreated as one line. 3.      The CleanUp, will move the streets to strange locations 4.      Highway intersections needs to be modelled manually. 5.      Actually almost any street segments crossing with an angle, needs to be modelled manually. Will get to these later. David ... View more

Hi Sangyun, I would suggest trying a few things. The easiest thing I can think of for applications of alignment is to have the vector points have a "rotation" attribute, that you populate based on the heading of the lines used to form the streets. You could use the Add Geometry Attributes tool to get the heading, then spatial join the heading to all the points to populate the rule parameter with that desired rotation based on the side of the street, and the heading of the pole. You might need to add attributes for off-set and the like. Add Geometry Attributes—Data Management toolbox | ArcGIS for Desktop David ... View more

Was afraid you would say that. If you have any ideas on how to do something similar let me know. If not we might just go with the attached pop up route... Thanks Robert, David ... View more

Hey Robert, Thanks for helping me articulate this further. So I guess the user experience can go in a variety of directions. I was potentially thinking of a splash screen that explains how the application works and explaining that they just need to click on a polygon/point to see its individual service area related to it. After the splash screen I was thinking in the best case it would work like a pop up, except when  a feature is clicked, a new geography becomes visible. If that can't be done, the select features selection UI that comes with things like the charting widget would suffice if it had to be done in a custom app. I imagine what I want is similar to filtering "Ask for Values" except the value is  a spatial selection, which I am not sure is natively supported. Does this need a custom widget? David ... View more

Hey Robert! I hoped you would be the one to find this! Sorry for not being very clear. I essentially want to relate two feature classes to a "reference feature class". So for example imagine we have service areas created from network analyst, if we display all of them at the same time, it looks meaningless because you can't tell what the origin point is. I want to be able to select the origin point in the app, and only those origins service areas appear on the map. I was thinking about it like a field definition query that would change based on the selection of an arbitrary feature class. I think for AGOL this concept is called filtering. Does this make more sense? David ... View more

Oh this looks like a really neat app. Thanks for sharing it. Glad it worked, most 3D modeling software has the concept somewhere. 😃 ... View more

I was thinking about making a version of the script that just used numpy, but this was largely just to explore applications and useful ArcGIS connections (moving between data structures etc). I think as people move to 10.4 this will be more useful. I just wanted to start working with them more because I was very excited for arcpy's integration with the scipy stack. ... View more

Hey Dan, I just asked to join the group! I will change the tag. I have used numpy/pandas interchangeably, but I have always liked the representation and syntax of pandas data frames. Look forward to the discussions in the new group! Thanks! ... View more