Latest Contributions by CraigWilliams

Label placement for vector tiles is quite simplified and geared towards performance. The type of control you're looking for is best achieved with feature data in the map and using the Maplex label engine. ... View more

Generically speaking, we can not anticipate all outputs of a script that processes a data value as input. Your case is quite simple, but not all scripts are making this a problem that is not solvable for all cases. Additional classes that are not found can be added in the unique value symbology. I'd recommend looking at coded value domains for your scenario. ... View more

The tools in the Attribute Rules toolset can be called via Python for automating creation and changing values. ... View more

The Replace Colors command allows for this. It's available with an ArcGIS Topographic Mapping license. ... View more

This was implemented in ArcGIS Pro 3.1 ... View more

This limitation was relaxed at ArcGIS Pro 3.5 (and other clients supporting Arcade 1.30 or higher). All coordinate systems are supported for Geodetic operations. ENH-000151609 has been updated accordingly. ... View more

The Arcade Layout profile (https://developers.arcgis.com/arcade/profiles/layout/) does not support the $datastore profile variable or the Data Access function bundle. Validation was updated at the 3.5 release to more strictly enforce profiles and this case that previously had been undocumented and unsupported behavior stopped working. Furthermore, in ArcGIS Pro 3.6 the code editor now includes profile-specific code hints to indicate when variables outside the scope of the profile are in use. We understand from your viewpoint that this is a regression in functionality, but execution of such scripts was accidental and as mentioned above unsupported and undocumented. Including support for feature set functions and profile variables such as $datastore may be considered for a future enhancement, but feature set functions are generally not included in drawing profiles due to performance impact. An alternative approach would be to perform the necessary computation in a calculation attribute rule and consume the calculated field. ... View more

You can do this with Arcade in Calculate Field. Given the names you have above and with the Field Name of the calculate field tool being ASSET_ID on the Points layer: var polygons = FeatureSetByName($datastore, "POLYGONS",['ASSET_ID'], true); var polygonFeature = First(Intersects(polygons, $feature)); if (!IsEmpty(polygonFeature)) { return DefaultValue(polygonFeature, 'ASSET_ID', "9999"); } else { return "9999"; }   ... View more

We've identified the issue and logged BUG-000180302. Since Ideas isn't intended for bug submission, I will close this Idea. ... View more

We have no plans to deprecate / drop annotation subclasses. They are the foundation of many workflows where different feature types need different annotation handling. There are also several misconceptions in the post. Multiple annotation classes are supported in feature services, have no effect on drawing performance vs. a single annotation subclass, and are significantly faster than multiple feature classes from a rendering perspective due to a reduction in cursor creation. ETL experiences are going to be highly dependent on how varied the data you're merging and don't significantly change with respect to multiple classes when dealing with symbol differences. The log issue is due to the sublayer not being supported as an individual layer end point. Reducing the log impact is something we will look at.   ... View more

Marcel, Can you provide an example of the expression you're experiencing this with? I'm unable to reproduce this with a FindLabel function (which we look for to detect the advanced expression) ... View more