|
POST
|
Well it might be possible to use a mapped attribute to deal with the direction issue. If you use buffers around intersections to split segments near the intersection, then calculate a heading for that line (see line bearing), you could then do an object insertion that takes that mapped value as a parameter using the world coordinate system. Help - Rotate operation. I have never tried this, but I have intended to experiment at some point. It would involve, finding a way to split a line at the intersection approach, calculating line bearing, then doing spatial joins from the line to the sign points (data required would be angle of rotation, and the obj file to be used), and then figure out how to use that line bearing to guide insertion angle in CE. EDIT: Cheryl's suggestion is great if you want to do a street based approach (a hybrid approach is possible). The Complete Street Rule might give a good starting point for such an insertion. Just an idea. David
... View more
01-15-2016
03:43 PM
|
1
|
0
|
3399
|
|
POST
|
I think this is a very helpful example Chris. Thanks for the code example.
... View more
01-15-2016
03:32 PM
|
0
|
0
|
1783
|
|
DOC
|
Hey Julio, The split line at point workflow (either randomly generated or densified) works very well too. I really made this tool to get more control and to deal with overlapping lines/more exact split points a little better. I have not got the split line at point workflow to deal with lines that overlap very well (network routes, etc). I am glad you were able to find a solution for your project now. I would love input into the functioning of this tool and any bugs you encounter. David
... View more
01-14-2016
09:42 AM
|
0
|
0
|
5430
|
|
POST
|
For Line Files I have found the split line at point workflow to be very good for this. For example when I need to weight a spatial join, I actually break my lines into equal length segments so that when they have statistics run on them they are "approximately" weighted to the length of the line. I have seen similar workflows with polygons where a blank fishnet is created and then intersected with the polygon layer to break it up into many pieces. In this way, on average your statistics are weighted to the larger area polygons. You dissolve at the end of this process of course in both examples. I realize this thread is old, but this method just goes in a direction opposite of a field based method (and works for ALL the fields in the database). Let me know if this makes sense. David
... View more
01-07-2016
01:21 PM
|
0
|
0
|
2905
|
|
DOC
|
Hi Ben, This is a personal distribution of the rule I created while working at ESRI. Since then, I have continued work on it. I have discussed letting ESRI just take the rule and distribute, and I kept it pretty open to use like that by putting it on an Apache License. If you want to message me about discussing another way for you to get this version of the rule let me know. The improvements made are listed on this page. Does your company allow Drop Box? I can change how the rule is distributed if it would be easier The reason why the original project is no longer used is that I no longer work for ESRI, thus do not have access to it. David
... View more
01-07-2016
09:31 AM
|
0
|
0
|
42944
|
|
DOC
|
Hi MINVU, The toolbox itself is a 10.3 toolbox so that might be a source of a problem. That said, the code itself is not using 10.3 only functions I think. It is possible you could create a new toolbox and import the script and recreate the input parameters for the tool based on the help file. I hope this helps. Other than that I am not sure what could be the source of the problem. David
... View more
01-04-2016
11:57 AM
|
0
|
0
|
3532
|
|
DOC
|
Hi Andre, Questions about the rule in use are best put here: Esri Complete Street Rule Discussion-Feedback? Documentation for the rule is here: The Official Unofficial Guide to the ESRI Complete Street Rule.pdf Relevant attributes are in the Median Planting and Center Section attributes. In this case check to see if your Walkway_Width is overriding your current planting settings. David
... View more
12-23-2015
12:13 PM
|
0
|
0
|
42944
|
|
POST
|
In that case, I think I will make a revision that zeros it at non-intersections for now. For your purposes though, delete line 1446. I might get to it this week or later. Depends on a current project's progress. I think the case of a large intersection will be dealt with conflict space because it does not use relative space, but absolute space to allocate geometry. It will be able to push it as far back as it needs till it zeros out. I think zeroing them out at non-intersections is a good compromise and is consistent with various other aspects of the rule. I will likely implement the same change to bus and hov lanes, so I appreciate the feedback. As per the option to remove it at all times, I will add a hidden parameter to nuke them all if it arises for a project, will not be hard to incorporate. Thanks for the development feedback. David PS: Scott I recently made a quick change to do make the second stamp disappear at intersections. I can look at this more in the future, but for now, this should help you quite a bit. Thanks for the help on this, it is really hard to predict some of the edge case behavior given the number lane types. The change I made applies to both bike, bus, and HOV lanes.
... View more
12-23-2015
12:01 PM
|
0
|
2
|
12191
|
|
POST
|
Hi Scott, When I try to do the same thing except I use conflict spacing, they all disappear, and my experiments with symbol spacing eventually get them to be very small like you show in 3. Symbol spacing as it stands will not remove it. I think after your experience I will make a function that zeros out the symbol width if the spacing goes above some really large number (5000?). Delete the line I mentioned above and it should remove the last symbol. I might remove the last symbol entirely from future iterations. As a user would you prefer the last stamp be removed entirely? Under what circumstances would you want it kept? If the rule zeroed out the second stamp when the segment ahead IS NOT an intersection would that be better? I am starting to question its usefulness, and I think I know what I might do when I have time to fix this depending on your answers. David
... View more
12-23-2015
11:06 AM
|
0
|
4
|
12191
|
|
POST
|
Hi Giuseppe, There are two main approaches I could suggested. Raster Based: One option is to drape a raster showing pollution intensity based on the distance from/intensity of traffic. I have for example used regression formulas in various papers tied with a euclidean distance to create particulate pollution dissipation bands in the image below (falling to zero at about 300 m). It might be possible to tie this with 3D Analyst and have this approach create draped rasters over your exported multipatches from CityEngine. Vector Based: Another option is to summarize pollution/traffic exposure by building on the building level. Once you do a few spatial joins you can use that information on the lot level to color buildings on a relative scale of pollution exposure. In the image you displayed, you could buildings with high exposure have more red than white as it ascends up the floors. I have used similar approaches to simulate flooding as part of a sea level rise rule, but instead I color the flood level blue, but the rest of the building based on the percentage of floors exposed. I hope this is helpful. David
... View more
12-20-2015
03:50 PM
|
0
|
0
|
1075
|
|
DOC
|
Hi Julio, I actually have recently had a breakthrough with modular functions to do just this using insert cursors. I will be uploading a new version of the tool this week that not only has copied fields, but also will split a feature by field ( you can have a field determine how many sections it gets split into). If you could please comment and provide feedback that would be great. I have noticed some issues with potentially non-sorted vertices creating issues by making some multiparts, but let me know if it works for you. David
... View more
12-20-2015
09:00 AM
|
0
|
0
|
5430
|
|
POST
|
Hey Scott, For the segments that have closer symbol spacing, is that intentional? Did you try changing the symbol spacing on those segments while selected? It will likely continue to do two IF it has enough space because it is long enough to support it (and the conflict spacing does not push it all the way back). This should though allow a minimum on two on each segment which does not look bad in the selection in number 2.I can't take another look any time soon, but as a potential route of experimentation for you if you really want go to line 1438 in the rule BikeLane(sideflip,Width)--> and start removing "~" from Bike_Symbol_Spacing or delete all of line 1446: | ~Width :BikeLaneStamp(Width ,Bike_Lane_Color+"_stamp.jpg",Bike_Lane_Color). That would get rid of the second stamp. Not sure I want to make that a general change, but I will think about it now. I think if the bike symbol spacing goes over 50, I will make it width for that stamp go to 0. I can see this being an issue for the bus lanes/hov lanes too because the use a similar pattern. Glad the rule is helpful. Your feedback helps me too. 😃 David
... View more
12-11-2015
02:27 PM
|
0
|
6
|
12192
|
|
POST
|
Yes. That is the current hosting spot. The geonet page there will reflect updates. Let me know if that fixed it. 😃
... View more
12-11-2015
01:06 PM
|
1
|
0
|
12192
|
| 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 |