CGA in ArcGIS Pro

[DavidWasserman]

is there a list of what functions exist in CityEngine that are not in ArcGIS Pro?

• So far I know:
  • Certain Annotations do not exist (File etc)
  • Street UVs do not exist
  • You can't sample textures the same way you do in CityEngine, requires GP tools, and sampling imagery for roof textures is likely not possible.

I want to add to this list though, can we get someone from the ESRI pro team to provide some background. Do we have Scope.Elevation for example? Which specific annotations are not available?  Are there any geometry operations or functions not available?

Relevant documentation:
Procedural symbol layers—ArcGIS Pro | ArcGIS for Professionals

Unsupported drawing—ArcGIS Pro | ArcGIS for Professionals

David

Chris Wilkins​ or Brooks Patrick do you know who might have an answer to this?

Message was edited by: David Wasserman

[Anonymous User · Accepted solution]

Hi David!

We don't have a comprehensive list yet, so I'll just add a few here:

- Order of edges is reversed. CityEngine goes either clockwise or counterclockwise (I don't remember off the top of my head), while Pro is the other one.

- Occlusion functions are not available in Pro.

- Range annotation for attributes is enforced in Pro, while they are only used to size the slider in CE. I'd like it if enforcing the range was optional. Sometimes you want it and sometimes not.

- Rules in Pro only run on the 3D layers.

- Start shape must be polygon or multipatch.

- If your rule runs on a point in CE (which is really a very tiny polygon in CE if you import a point feature class from GDB), then buffer your points in Pro to make a little circle to run the rule on.

- To make a rule run on multipatches in Pro, you must add "@InMesh" annotation over the start rule.

That's off the top of my head, but I'm saving these to a list now.

Chris

[DavidWasserman]

Hey Chris!

I think this will help a lot of people, including me.

It sounds like then Scope.elevation's functionality might be preserved?

Order of Edges is reversed...that is scary to contemplate. Does this mean that any use of AlignscopetoGeometry will need to pick different edge index numbers if they depend on a particular edge?  Also how do the street.selectors get changed by this if at all?

That is good to know about the Range annotation, and I agree with your assessment of it.

Good to hear from you!

David

[Anonymous User]

I haven't tried the street selectors yet. I assume they fall back to object selectors, which is the behaviour in CE when they are missing the street width attributes.

Scope.elevation I would want to test in several ways, because in Pro there are several ways to set the elevation, and I'm not sure how this would work.

No time to test these before the UC! But I have started another list of things to test.

Chris

[DavidWasserman]

Hi Chris,

I think as we learn more either posting here or making another post of lessons would be great. If you need help experimenting I could test the scope.elevation when I get time.

Thanks for the update,

David

[Anonymous User]

Sure. Any testing you can share is awesome.

As far as rules go, almost all of the rules I'm making now are being used in Pro, so I'll be documenting this stuff as it comes up.