Latest Contributions by DrewFlater

This has been developed in ArcGIS Pro 3.1. Here is the new syntax that will copied to the clipboard when using the various Copy Python Command options.  arcpy.management.CalculateField( in_table="main.random", field="testfield", expression="200", expression_type="PYTHON3", code_block="", enforce_domains="NO_ENFORCE_DOMAINS" ) As we feel this syntax matches best practices and standards for Python code, as well as having much improved readability, this is the default and only option when copying Python commands from geoprocessing tools.   ... View more

This isn't something that would be provided as a core software geoprocessing tool in ArcGIS Pro. Based on the connections in the comments there might be other ways to achieve the desired goal. ... View more

This can be accomplished using the "Use field alias as name" parameter in Export Features. https://pro.arcgis.com/en/pro-app/latest/tool-reference/conversion/export-features.htm#GUID-D4C68514-1D1E-483B-B239-D4208BF0E847 ... View more

This is more of a bug in the Calculate Field tool's Arcade expression builder, as it works in Label Expression builder with Arcade, and other tested areas. The issue will be investigated and addressed in the Near term (next 1 or 2 releases). ... View more

It is unclear how having a field with the length 255 matters in the workflows described. If a field with only 18 characters but length of 255 is field mapped to a target field with length 18, the first 18 characters from the field with length 255 will automatically be transferred into the field with length 18. Given the lack of significant support in the last 6 years this will not be prioritized. If a case is uncovered where the field length 255 with 18 characters is not correctly mapped to a field with length 18, we will treat that as a bug and fix it. ... View more

@DWR_BuckEhler we are working on this in development now. Exporting to kml vs. kmz will be driven by the provided extension on the output file parameter.  In testing we continue to see more limitations of basic KML. All point features become pins regardless of input layer symbology (kml points/placemarks don't support embedded PointStyle without additional resources included in a kmz archive), only basic symbology is supported for line and polygon layers. If a symbol has multiple layers only one of the layers will be added to the kml as the format does not support multi-layered LineStyle or PolyStyle. Attachments from the input layer cannot be included. Raster layer input will not be supported since kml itself is feature-geometry only, ground overlay rasters require storage in the kmz archive. And advanced behaviors and styles in labels are not supported unless output to kmz, since the kml file itself cannot store style sheets (they are another resource inside KMZ archive).  With all these conditions, it will still be possible to generate the basic kml using Layer To KML in the near term (next 1 or 2 releases). ... View more

This bug should be directed to Esri Technical Support. Please see these guidelines and information about usage of ArcGIS Ideas. https://community.esri.com/t5/community-help-documents/arcgis-ideas-submission-guidelines-and-statuses/ta-p/904874 ... View more