Latest Contributions by Michael_Kraus

Yes this is required.  Now that we can use Arcade for symbology expressions, it is frustrating that users can see the results of Arcade expressions in the symbology when symbolising by an Arcade expression, but when they want to look at the table or export just the records from a symbol class, they can't. Also expressions aren't available in the Analysis Tools --> Manage Data --> Extract tool either.  So the users can't use these analysis tools to extract a filtered dataset either. Please ESRI include either the ability to use Arcade in the filter or give the filter access to previously defined attribute expression "fields". This was raised awhile ago and was closed as a "documentation error" https://community.esri.com/t5/arcgis-online-questions/filter-expressions-arcade/m-p/1141612/highlight/true   ... View more

Looking forward to seeing this (well overdue) update ... View more

The best I found at this point is this 7 minute YouTube clip from GeoMarvel.  https://www.youtube.com/watch?v=Ex8I_uU9l0k This is what I am sharing with my users for the time being.  It is not the latest, so misses out on the Analysis options.  I would hope / expect that ESRI will put something on the ESRI Academy sometime? ... View more

Thanks Jonathan - the videos at learn.arcgis.com should be useful in this case. ... View more

Adding a few more observations and issues to the list.  We are now in the middle of migration. Size of data - there is a bug somewhere. Running an item report in ArcGIS Enterprise (10.9.1) we used the feature size to estimate how much space we would need in AGOL and how many credits we would use.  Unfortunately there is a bug somewhere that means this information is quite meaningless. Enterprise "Item Report" was telling me that our feature storage was about 3Gb total.  For our 2500 or so items I thought this was a bit low.  During migration we quickly realised this was wrong.  A typical example - a polygon layer with 6000 suburb boundaries - ArcGIS Pro catalog view tells me this is 20Mb.  Published to Portal as a web feature layer, it is reported ad 4Mb, and doing the same to AGOL gives me 56Mb of feature storage.  So this error of 1400% makes our estimation of future AGOL credits fairly pointless (ESRI Case Number 03425687) We thought with 25 creator users and the 12500 credits their user type includes would satisfy our annual storage, but with the current numbers it looks like we will run out in 3 months. Map Services - features This one fell through the cracks for us in our initial assessment.  Publishing a web layer from Pro as a web map with feature access was a quick way of getting multiple layers to our clients to consume in the map viewer.  They were presented a single layer with sub-layers they could toggle on and off in one motion, and this was grouped for logical reading in the map TOC. I have now gone through all of these map services and made a choice to republish as feature services in most cases, but occasionally map tile services where there was annotation involved or the grouping / hierarching was significant.  The users won't like the flat structure / non-grouping when they add these to their maps. As a workaround, I will need to do further work to understand the way these are used and it could end up that tile services are sufficient for the users, and give that simpler user experience and more user friendly handling / grouping of layers.  Alternatively we may accellerate our move to the "new map viewer" which does have layer grouping, but was hoping to delay the user training / documentation update that the change of map viewer will imply. Backup solution Moving from a hosted solution which included nightly backups to SAAS without any backups has us looking for a solution.  We are leaning towards GeoJobe Backup My Org.  No worries with the fairly low cost annual licence, but this needs a server for hosting the backup software and cloud storage for the backups.  So while we are trying to move away from reliance on IT department and the issues associated with needing to spin up a server and manage it, it looks like we will be needing a server for this.   ... View more

Following up to my original post - we are currently testing functionality and migration to from Enterprise 10.9.1 to AGOL.  A couple of things we have found so far. Most things work fine! Publishing from Pro with the "support all clients" seems to be required to render services correctly in AGOL Map Viewer Classic vs not being required in 10.9.1 Map Viewer Classic Seems to be zero support for Annotation in AGOL.  We work with a lot of CAD and have been converting annotation to points before publishing to Portal anyway (it seems faster to display labels from points than anno), but Enterprise does have some support for annotation Labelling supported by Enterprise from a published web layer / map image layer is not supported by AGOL.  Particularly rotated labels which is quite annoying.  Several in the AGOL community have been asking this from ESRI for some years, but nothing on the horizon to support point labels rotated by an angle (attribute driven) in AGOL.  Workaround would be publishing tiled layers which do provide the label visual you see in Pro, but at the downside of losing dynamic labelling and not being able to move the labels to the top of the TOC.  Again another workaround is to add the labels to the basemap and then make the labels a reference layer in the basemap but these multiple steps are beyond the skill level and tolerance of my viewer users. No support for configured / customised map templates.  I was hoping to add a logo and standard disclaimer to a print template, but all of the AGOL documentation points to having an ArcGIS server configured to support this.  It seems standalone AGOL cannot do this?  We will have non-maintained perpetual Enterprise licences available but the biggest driver to migrate from Enterprise is the hosting cost, so don't want to rely on keeping an Enterprise licence alive somewhere to support this. Some bugs we have had to deal with from 10.8.1 to 10.9.1 are fixed in AGOL Our migration process will include scripts / processes that will be reused for AGOL archives / backups, so seem to have a solution there. Still looking for some definitive documentation that provides a comparison. Also considering some 3rd party add-ons such as those from GeoJobe to support some administration things. ... View more

Hi Robert - I did a similar thing with Arcade (using a sample that I can't find the source of right now - apologies to the author).  I did "Top 5", you could change the first line to = 1 to just get the top one.  Below is a screenshot of the popup and the code.  The only bug / issue at the moment is that equal ranks / scores are all showing up - I would prefer it to just take the first one in that case. Screenshots below... Example with equal ranks:   Code below.... var numTopValues = 5; var groups = [ { value: $feature["P_Afghanistan_Tot"], alias: "Afghanistan"}, { value: $feature["P_Bangladesh_Tot"], alias: "Bangladesh"}, { value: $feature["P_Bosnia_Herzegov_Tot"], alias: "Bosnia and Herzegovina"}, { value: $feature["P_Brazil_Tot"], alias: "Brazil"}, { value: $feature["P_Cambodia_Tot"], alias: "Cambodia"}, { value: $feature["P_Canada_Tot"], alias: "Canada"}, { value: $feature["P_Chile_Tot"], alias: "Chile"}, { value: $feature["P_China_Tot"], alias: "China"}, { value: $feature["P_Croatia_Tot"], alias: "Croatia"}, { value: $feature["P_Egypt_Tot"], alias: "Egypt"}, { value: $feature["P_England_Tot"], alias: "England"}, { value: $feature["P_Fiji_Tot"], alias: "Fiji"}, { value: $feature["P_France_Tot"], alias: "France"}, { value: $feature["P_Germany_Tot"], alias: "Germany"}, { value: $feature["P_Greece_Tot"], alias: "Greece"}, { value: $feature["P_Hong_Kong_SAR_Ch_Tot"], alias: "Hong Kong"}, { value: $feature["P_India_Tot"], alias: "India"}, { value: $feature["P_Indonesia_Tot"], alias: "Indonesia"}, { value: $feature["P_Iran_Tot"], alias: "Iran"}, { value: $feature["P_Iraq_Tot"], alias: "Iraq"}, { value: $feature["P_Ireland_Tot"], alias: "Ireland"}, { value: $feature["P_Italy_Tot"], alias: "Italy"}, { value: $feature["P_Japan_Tot"], alias: "Japan"}, { value: $feature["P_Korea_South_Tot"], alias: "South Korea"}, { value: $feature["P_Lebanon_Tot"], alias: "Lebanon"}, { value: $feature["P_Malaysia_Tot"], alias: "Malaysia"}, { value: $feature["P_Malta_Tot"], alias: "Malta"}, { value: $feature["P_Mauritius_Tot"], alias: "Mauritius"}, { value: $feature["P_Myanmar_Tot"], alias: "Myanmar"}, { value: $feature["P_Nepal_Tot"], alias: "Nepal"}, { value: $feature["P_Netherlands_Tot"], alias: "Netherlands"}, { value: $feature["P_New_Zealand_Tot"], alias: "New Zealand"}, { value: $feature["P_Pakistan_Tot"], alias: "Pakistan"}, { value: $feature["P_PNG_Tot"], alias: "PNG"}, { value: $feature["P_Philippines_Tot"], alias: "Philippines"}, { value: $feature["P_Poland_Tot"], alias: "Poland"}, { value: $feature["P_Scotland_Tot"], alias: "Scotland"}, { value: $feature["P_Singapore_Tot"], alias: "Singapore"}, { value: $feature["P_South_Africa_Tot"], alias: "South Africa"}, { value: $feature["P_Sri_Lanka_Tot"], alias: "Sri Lanka"}, { value: $feature["P_Taiwan_Tot"], alias: "Taiwan"}, { value: $feature["P_Thailand_Tot"], alias: "Thailand"}, { value: $feature["P_North_Macedonia_Tot"], alias: "North Macedonia"}, { value: $feature["P_Turkey_Tot"], alias: "Turkey"}, { value: $feature["P_USA_Tot"], alias: "USA"}, { value: $feature["P_Vietnam_Tot"], alias: "Vietnam"}, { value: $feature["P_Wales_Tot"], alias: "Wales"}, { value: $feature["P_Zimbabwe_Tot"], alias: "Zimbabwe"} // ADD MORE FIELDS AS NECESSARY ]; function getValuesArray(a){ var valuesArray = [] for(var i in a){ valuesArray[i] = a[i].value; } return valuesArray; } function findAliases(top5a,fulla){ var aliases = []; var found = ""; for(var i in top5a){ for(var k in fulla){ if(top5a[i] == fulla[k].value && Find(fulla[k].alias, found) == -1){ found += fulla[k].alias; aliases[Count(aliases)] = { alias: fulla[k].alias, value: top5a[i] }; } } } return aliases; } function getTopGroups(groupsArray){ var values = getValuesArray(groupsArray); var top5Values = IIF(Max(values) > 0, Top(Reverse(Sort(values)),numTopValues), "Insufficient Population"); var top5Aliases = findAliases(top5Values,groupsArray); if(TypeOf(top5Values) == "String"){ return top5Values; } else { var content = ""; for(var i in top5Aliases){ content += (i+1) + ". " + top5Aliases[i].alias + " (" + Text(top5Aliases[i].value, "#,###") + ")"; content += IIF(i < numTopValues-1, TextFormatting.NewLine, ""); } } return content; } getTopGroups(groups); ... View more

This seems to be a fairly new setting.  I have had the same issue publishing to AGOL recently (but works fine without using this compatibility setting for Map Viewer Classic on Enterprise 10.9.1) When you publish from ArcGIS Pro, you need to check the "Use symbol types compatible with all clients" check box to convert ArcGIS Pro symbols to web symbols that can be rendered by all applications, or "symbols appear downgraded in older clients, such as Map Viewer Classic." https://pro.arcgis.com/en/pro-app/latest/help/sharing/overview/share-a-web-map.htm   ... View more

Agree that ArcGIS online needs to be able to rotate point labels by a numeric attribute. While not a solution, I noticed even sharing as a map layer to AGOL has point text ignoring the rotation settings from ArcGIS Pro - while ArcGIS Enterprise honours these settings. A potential workaround is to share as a tiles, which means AGOL can display the labels rotated.  Whether this is suitable to switch your entire layer to tiles or just the annotation component and continue to publish your other geometry as feature layers.  It does take away the dynamic ability to switch to another label field, but may be suitable for text elements that are static. ... View more

Thanks for confirming this as a another 10.9.1 bug.  When I try the workaround of editing the description, my portal screen just sits waiting when I press the save button of the field description, so I can't seem to employ this workaround to get around the bug.  I have tried seeing if I can edit the description or domain in Pro, but no good for a hosted feature layer.  Is there a behind the scenes, eg  REST interface, way of adding a field description or the domain? Thanks. ... View more

It's difficult to use settings that refer to page units - such as duplication distances for labelling or minimum feature size for labelling if there is no measure tool that works on the layout using page units.  Can this idea please be considered for implementation? ... View more

This is now confirmed as a bug.  BUG-000137059: Unable to get the correct statistics based on the second selection in ArcGIS Pro. ... View more