|
POST
|
Thinking on it, you remind me there were other solutions that had me think this was resolved as well in the past and it just resurfaced again. I should clarify that the issue is resolved for now, and I will check in with the forum again if necessary.
... View more
10-02-2017
08:33 AM
|
1
|
0
|
3058
|
|
POST
|
I also had a similar issue. I had some type of ArcGIS Administrator issue. Edit: The issue arose again and I will confirm this resolved the issue. Nuke Flex, and problems just seem to go away.
... View more
09-29-2017
02:15 PM
|
0
|
2
|
3058
|
|
POST
|
While I agree the best approach is to actually do this task in QGIS (same for KML import export), I have had some success getting a Gist to work with at least point features. If anyone has any thoughts for improvements, let me know. This gist is intended to share a sample worker function to write Geojson to an ArcGIS Feature Class using Arcpy. · GitH…
... View more
09-23-2017
09:35 AM
|
1
|
0
|
5930
|
|
POST
|
Another approach is when you get to this regional scale is to change the frame from which you are presenting by using batch generation workflows (focus on the facility/neighborhood rather than the whole region). There are scripts located here that might be helpful for this. At some point it actually makes sense break down the data into zones/batches for import and display.
... View more
09-19-2017
05:49 PM
|
0
|
0
|
4111
|
|
POST
|
Cheryl, this only applies to CityEngine Scenes correct? Does this mean a county scale project would require ArcGIS Pro in this case case?
... View more
09-19-2017
05:46 PM
|
0
|
1
|
4111
|
|
POST
|
Hi Kristian, Darn, I was really hoping it might have. Not past what is not discussed above. The only way I have gotten it to work is by assuming some creation of a "buffer" between the intersection and the street UV (so you have some crosswalk or stop bar spacing that separates the longer/distorted UV at the intersection from the rest). You have to use the UV space however to deal with curves (unitSpace for example). Beyond this problem is the one of orientation (you can't do speed tables very well for example because something about the alignment changes). Streets as they are very close to being able to do a lot of useful things for conceptual design, but there are gaps in their capabilities. If you have any ideas for this problem, would enjoy your thoughts. Potential things I have not had time to try include: Splitting the street width wise so that the mid-section is as wide as the minimum width in the center of the street (clip off the extract width, send it to asphalt). Buffers that adjust width based on distance to the intersection. For reference, I wrote the complete street example. An updated Repo is here. If you thought I used clever texturing you should take a look at the Standard_Street_Rule...that was way more clever than mine. If you have thoughts on how to make the CS rule more modular or have feature requests please don't hesitate to share them with a Github issue. I really want to be able to do more specific treatments, especially at intersections. Thanks, David
... View more
09-19-2017
12:34 PM
|
0
|
0
|
2805
|
|
POST
|
This is what I was referring to when saying the minimum and maximum values change in the texture/geometric space (those at the edge of the intersection where it extends is the new max). This is actually a great graphic explaining where this occurs. Does this split pattern work with curved streets in your experience? Does it still require a buffer provided by a crosswalk or some other split? I might want to give it a try for the CS rule if it does.
... View more
09-19-2017
08:39 AM
|
0
|
2
|
2805
|
|
POST
|
That was not the issue in this case I think. I think it has to do with the Tile requirements Thomas mentioned. When I tried custom, it gave a similar response.
... View more
09-13-2017
05:40 PM
|
0
|
0
|
640
|
|
POST
|
Hi Emily, Are you having a first edge problem? You might need to manually set the first edge on some shapes if the set first edge tool does not do what you want shapes. You also will want to make sure your streets have a streetWidth attribute for some types of setbacks. Help - From the docs: Set First Edge. This operation sets the first edge of a face to the currently selected edge. This step is often needed to orient a face's "zero" edge towards a street (e.g. for placing the buildings front correctly). If a face is selected, the highlighted gradient line indicates the first edge (with gradient from vertex 0 to vertex 1). Set Street Edges. This operation marks selected edges as street edges. More specifically, it sets the street width object attribute array to 1 for selected edge indices. When mapped to a CGA rule, the streetWidth() attribute can be used to identify edges or faces that are facing a street. (see also comp() in CGA reference) Compute First/Street Edges. This operation automatically calculates the first and street width attributes of the selected shapes. It works as follows: First it finds the nearest street (within 100m) for every edge of a shape. The corresponding street width attribute is set to the width of the nearest street. The edge closest to a street is set as the first edge (edge 0). Related docs on Setback: Help - Related Docs on Block Parameters: Help - Do any of these seem related? David
... View more
08-23-2017
06:09 PM
|
0
|
0
|
1328
|
|
POST
|
Thanks! I just wanted to check from a Jedi master if I was missing something.
... View more
08-17-2017
12:02 PM
|
0
|
0
|
1666
|
|
POST
|
Hi All, I have a hypothetical question about importing outside rules. Is it possible to set up conditional imports? I know in python it is very easy to do something like this: try:
import pandas as pd
except:
# Pandas is shipped with ArcGIS Pro and ArcGIS 10.4 and higher. The previous logic should hopefully prevent users from ever hitting this error.
arcpy.AddError("This BetterBusBuffers tool requires the python library pandas, but the tool was unable to import the library.")
I was curious if something similar is possible in CGA. In my earliest attempts, I start with a simple import statement: import Street_Text : "Street_Text.cga" Then, I figured, because the text for import is just text, I can just replace it with a const. const conditional_text_import= case fileExists("Street_Text.cga"): "Street_Text.cga" else: "/ESRI.lib/rules/General/Text.cga"
import Street_Text : conditional_text_import This however returns an error. I have since tried doing the import statements within rules and other variations (I did not think they would work but I thought I would try). Is this simply not possible in CityEngine? Any alternatives? My goal is to essentially make a rule not being in the folder not be catastrophic to the rules function. It is a small thing, and there are other options, but I just want to keep a rules user experience a little easier. I think I am especially concerned when the functionality being added is not critical to many people's use cases. Relevant docs: import Using CE 2017. Any thoughts appreciated. CWilkins-esristaff to your knowledge is this possible?
... View more
08-12-2017
12:53 PM
|
0
|
2
|
2165
|
|
POST
|
Hi Thomas, I had a question about scene creation workflows. I can create hundreds of web scenes using just the Python API, but it sounds like the same cannot be done with Local Scenes? Is that correct? Is there anyway to template a local scene in CityEngine so that you can go from selected layer to local scene with a URL using the python API? Or would it have to be a mixed workflow? David
... View more
07-27-2017
01:28 PM
|
1
|
0
|
1823
|
|
POST
|
Good question. This actually took some research. I did not originally write the bridge rules. Pier --> case heightOverTerrain > 0: split(v,unitSpace,0){ '0.15: NIL | '0.70: PierStep2 | '0.15: NIL } else: NIL It seems the actual width is set to be about 70% of the street width. I might expose this in a later version, but for now I think you need to adjust this bold element. You should also adjust the other two numbers in italics as well. Hope that helps, David
... View more
07-23-2017
09:19 AM
|
0
|
1
|
7766
|
|
POST
|
Understood thanks for clarifying. I don't really want a time window as a constraint, but a measurement of the passengers travel time from the start of their trip to the end at their destination. So for the person involved it would be (wait time+ service time+ travel time for delivery). I thought I could use the ArriveTime you mentioned. My concern is for ordered pairs I am not sure what the passengers "start time" is. If it varied at all etc. My uncertainties are : I am not sure is if everyone is starting their trip at 8 AM or if I need to compare the ArriveTimes of the pick up order and the delivery order? If it is 8 AM I just need to say ArriveTime- 8 AM, but if it is pick up and delivery pairs I need to compare the two pairs (ArriveTime of Drop off- ArriveTime of Pickup) times correct? David
... View more
07-21-2017
01:56 PM
|
0
|
1
|
3578
|
| 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 |