Latest Contributions by CraigWilliams

Line offset exists in the specification but the ArcGIS JavaScript API and therefore the ArcGIS Online map viewer doesn't support it at this time. It's on our list to add in a future release where we want to ensure 1) excellent performance and 2) handling of complex geometries. ... View more

Unfortunately these are a few cases where this string has been embedded within the source list of the service itself. For some Esri services, we will be looking at the possibility of removing these. In the meantime, unfortunately the only workaround is to create a text element with the sources without this string and put the real service layer credits off the page. ... View more

Interesting, that's not what the field delimiter was designed for! Backstory: In ArcMap when creating unique value symbology from many fields, we typically store "<value 1>,<value2>" etc with each value being separated by a comma. This approach worked for many cases, but went horribly wrong when the unique value from a field actually contained a comma. We added analysis code to detect this when generating unique values and would switch the separator to another character. The UI under Advanced was just there to provide an annotation place to edit it. In ArcGIS Pro, we don't store unique values for the comma delimited case in a single string with a separator. We store an array of values. Therefore, we don't need the delimiter for the above purpose. Obviously you can hand edit the labels for the classes to not be commas, but I can imagine that would be time consuming as you note. It appears the sort is primarily an issue for 1-9 and then things are ok after that, so maybe re-ordering just those won't be too bad. Looks like we have a few things to look into including the sort. ... View more

Is there any chance you can share code or a small example case? Is it Apache POI you're using? ... View more

What exact issues are you seeing with either scenario and which Java version does your build target? ... View more

This case you're showing in the UI is Vary symbology by color—ArcGIS Pro | ArcGIS Desktop  which is for linking data values to a color not color values to a color. See Attribute-driven color in symbology—ArcGIS Pro | ArcGIS Desktop for color to color. ... View more

This is achievable as well using the attribute driven color approach. What issues are you having? ... View more

The text out of the expression needs to match the examples in the above linked help topic. If you're specifying alpha, you need a value from 0 to 1 with 0 being fully transparent and 1 being opaque. You also don't need the concatenate function in this case So, use: "rgb(" + $feature['Units_in_M$.R'] + "," + $feature['Units_in_M$.G'] + "," + $feature['Units_in_M$.B'] -or- "rgba(" + $feature['Units_in_M$.R'] + "," + $feature['Units_in_M$.G'] + "," + $feature['Units_in_M$.B'] + ",1)" Depending on what you're fields are, you may need to use the Arcade Text() function to format numbers to correct format as a string. ... View more

We've been focusing on documenting the JSON variation of this spec (see https://github.com/Esri/cim-spec). We've had requests to have a JSON schema version of this which we're considering, but no plans to do an XML schema at this point. mapx, lyrx, pagx, and items in styles all use the JSON spec. ... View more

This type of conversion is typically handled during the sharing process when creating weblayers, webmaps, or when handing out such layers from MapServices. There's not a direct API call to convert between these specifications. ArcGIS Pro uses the CIM specification while the JavaScript API uses the WebMap specification. Can you explain more about your workflow and what you're looking to create? ... View more

APRX files are zip archives. STYLX are SQLite databases. At this point there are no plans to change this. ... View more

In many contour datasets, the features are very large with a single contour value being one long winding feature with a large extent. This may explain why even with 500 feature you're hitting memory limits. It's also the reason why the Contour tool now has a Maximum vertices per feature parameter. For existing contours, you may want to run the Dice tool to make these larger geometries smaller. If generating contours from scratch, I'd highly recommend preprocessing the input raster with a Focal Statistics operation with the Mean option or the Filter tool with the Low option. This will create smoother contours from the start and will produce better results than generating contours from a noisy DEM and attempting to smooth or simplify them after the fact. ... View more

With Python, VBScript, and JScript expressions, the field values always passed through the field formatting of the layer and were brought into the label expression as strings. While that achieved your desired effect in this case, it caused problems in other scenarios where some expected raw field values. It also caused problems for portability as cases like feature services, web maps, and feature-linked annotation lacked the layer formatting. For Arcade, we made a conscious decision to pass the feature itself into the expression with raw field values. This itself is quite powerful as it provides access to geometry and arithmetic operations can be performed on raw data values. As Wendy Harrison‌ noted above, we have documented the difference in behavior here from the very introduction of Arcade. In future releases, we'll be revisiting layer field formatting with the goal of greater portability and look at whether we can default Arcade expressions on field insert to match field formatting in appearance much like we do for coded value domains. ... View more

This should not be occurring on MXD import and is something we would like to look at. The best path for that would be to submit an issue to Esri support services. ... View more