Latest Contributions by CraigWilliams

Labeling respect the map frame edge in all cases except when it's told not to. Settings that tell it not to  include: Label class level property: Never remove (place overlapping) The map level property: Allow labels to overlap border There is zero buffer applied to the boundary, so labels may be right against it if they fit. It's a bit hard to tell in your images, but some examples may be that. As for the overlap case, it's hard to determine what is going on there, but perhaps Never remove is enabled. ... View more

I'm marking this implemented but it's a bit different than the approach being used here. The shape field of an annotation object is just the bounds of the item. Changing it does not affect the annotation in the way you're expecting. At ArcGIS Pro 3.4 we introduced a new ANNO@ token to work with an Annotation object in cursors and modify properties using the arcpy CIM access. Use that path to make modifications you want to make. ... View more

We implemented an approach for annotation in arcpy.da cursors in ArcGIS Pro 3.4 that uses an Annotation object tied with arcpy CIM access to fully expose the annotation feature content. See https://pro.arcgis.com/en/pro-app/latest/arcpy/classes/annotation.htm for more details. ... View more

The ArcGIS Pro UI takes the decimal value. 63113 is the decimal value of the hexadecimal f689. ... View more

Remove duplicates does work across label classes and layers but it's limited to prevent accidental removals. Currently only labels from the same feature type (point, line, polygon etc.) and in label classes with the same font and size will be considered duplicates as documented here. You're requesting unlimited removal for any matching text string? ... View more

As noted in the tool documentation for the Conversion Scale parameter, it's "The scale at which labels will be converted. If a reference scale is set on the map, the reference scale will be used for symbol sizing and annotation feature class creation, but conversion will occur at this scale." Since reference scale can be combined with multi-scale behavior both scales need to be taken into account when performing the conversion to ensure conversion matches what is on the screen. The reference scale known from the map, so it doesn't need to be another parameter. ... View more

@MarcelSt-Germain If you have a reproducible case of a crash we can gather more information from the actual data than an error report. This is why I requested you log a support case. ... View more

The status of whether annotation has been upgraded is in the source tab of feature class properties in the Annotation section.   ... View more

Marcel, please log a support incident for your issue here. ... View more

Unique values are always stored as strings, but we're sorting numerically for number fields which is why the behavior is different. Thanks for bringing this to our attention. ... View more

256 x 256 raster tiles can be used with 512 x 512 vector tiles. The ArcGIS Online basemaps that use raster hillshades demonstrate this very concept. If you're unable to combine two services, it's likely that they're incompatible in another way. 256x256 is a in inefficient size for vector tile workflows. Since the content is vector and there are optimizations when the tile contains more data, 512 x 512 is a good compromise between size and efficiency. ... View more