Latest Contributions by CraigWilliams

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

Closing as we have no plans to implement this and 512 tiles can be used with 256 tiles as mentioned above. ... View more

ArcMap's label styles stored both the placement and the text symbol. We found that there weren't heavily used because many wanted the placement but not the specific text symbol - so we separated them to allow for more free mixing and matching. ... View more

We have updated the display field logic at ArcGIS Pro 3.5 to avoid the Shape_Length and Shape_Area fields. In the specific case of a polyline or polygon feature class with no additional fields, you'll now have the OBJECTID field as the display field. We are not defaulting to it for cases where other fields are present as there is usually a better choice that OBJECTID which is essentially an implementation detail. So, the logic looks for fields with the word "name" in English or the localized language and then walking through other non-OBJECTID field names in the order of string fields, date fields, numeric fields, and then finally OBJECTID is the last resort. ... View more

That issue ended up being converted to an enhancement ENH-000172553 which was then closed with the public explanation: "This is the expected behavior. Fields cannot be permanently reordered at the database level. https://support.esri.com/en-us/knowledge-base/how-to-permanently-reorder-fields-in-a-feature-class-us-000025984" Is something being lost in the communication here? If the desire is to save the field re-order, you can use a layer file for layer level re-ordering without altering schema.     ... View more

The Generate Contiguous Cartogram tool was added at ArcGIS Pro 3.5. There are a few other requests in this idea about non-contiguous and Dorling cartograms. We are collecting requirements on these. See also this blog post Ken Field and Chris Wesson about the addition: https://www.esri.com/arcgis-blog/products/arcgis-pro/mapping/marmite-maps-now-available-in-arcgis-pro ... View more