Latest Contributions by GregBazhaw

Recently there was an ArcGIS Blog post comparing the New Map Viewer and Map Viewer Classic and when certain workflows are available in one but not the other viewer (https://www.esri.com/arcgis-blog/products/arcgis-online/mapping/tale-of-two-arcgis-online-map-viewers-functionality-guidance/). Is there a similar blog post or article that compares web apps, especially Web AppBuilder widgets, with the new map viewer vs classic map viewer? Our users are provided apps (mostly web appbuilder apps) and not the map viewers themselves. There are many great enhancements to new Map Viewer, but those enhancements do not translate into many apps or widgets used within web appbuilder. It's frustrating to spend time designing a great map in the New Map Viewer, only to find 20% or more of the functionality of that map fails to cross over as expected into an app or widget in web appbuilder. A side by side comparison of New Map Viewer functionality and web apps and widgets that work and don't work would be useful. I have searched but cannot find a blog post/article that provides this comparison. Thank you. ... View more

Please allow us to change the selection/highlight symbology for the Search Widget in Web AppBuilder. Currently when the widget is configured to "Show pop-up for the found feature or location," the resultant color is an opaque orangey-brown, and we are unable to see underneath this color at the underlying layers. It would be groovy if you would allow us to configure the widget to either (1) change the fill transparency and color, and/or (2) remove the fill and just have the standard default cyan outline. Users are generally unaware they can clear the selection to remove the color, but when they do, they lose the selection color altogether. Having some sort of selection color when using the widget really helps users keep track of their found item when panning and zooming around. Thank you. ... View more

When using the scroll bar in an attribute table in Desktop, one can visually browse all the records as they scroll by, even on large datasets. In Pro, when you scroll the attribute table, you get a blank screen with the word "Scanning...". One has no idea where they are in the long list of records, until they stop scrolling, only to discover they need to scroll further, or they scrolled too far. This is terribly inefficient. The Desktop way to scroll works way better. Please implement this method of scrolling for the attribute tables in Pro. ... View more

In ArcGIS Online, it seems impossible to prevent a user from opening a Hosted Feature Layer (or any of its Views) in ArcGIS Desktop. Once a Hosted Feature Layer (or any of its Views) is opened in ArcGIS Desktop, the user is able to export that data. This is a severe security issue. There should be a way for ArcGIS Administrators to prevent users (named users and/or Everyone) from opening Hosted Feature Layers (or any of their Views) from within ArcGIS Desktop (including Pro), and through extension, being able to download the data. ... View more

In ArcGIS Online, it seems impossible to prevent a user from opening a Hosted Feature Layer (or any of its Views) in ArcGIS Desktop. Once a Hosted Feature Layer (or any of its Views) is opened in ArcGIS Desktop, the user is able to export that data. This is a severe security issue. There should be a way for ArcGIS Administrators to prevent users (named users and/or Everyone) from opening Hosted Feature Layers (or any of their Views) from within ArcGIS Desktop (including Pro), and through extension, being able to download the data. ... View more

be able to manage tags for the organization. View all tags and delete or rename misspellings. We have many misspelled and retired tags, or tags used for testing, that need to be cleaned so users don't inadvertently use them or when you start to type a tag you don't get a long list of bogus out of date tags. ... View more

Currently there are 4 ways to download data from Open Data: Spreadsheet, KML, Shapefile and API. Not all these download types are appropriate for all datasets. It would be great if when designing an Open Data site, the designer had the option to choose which download type to allow for any given dataset. This could be done by having a check box next to the download type and you can check the box to allow that download type. For example, KML does not work well for all datasets. Why allow a user to download a KML if it will fail with a dataset that doesn't play well with KML? The poor user has a frustrating experience thinking they can download a KML and plop it into Google Earth and expect it to work, when that dataset was never intended for that purpose. Similarly spreadsheets do not make sense for some datasets. The designer of the Open Data site should be allowed to choose from among the download options which option(s) will be best for their data. thank you.   ... View more

The Web Appbuilder could benefit from a widget similar to the functionality found in the FINDER Configurable App. In the FINDER Configurable App, one is able to select a layer and a field, from one of the many layers in a map. For instance, I can configure the FINDER app to search on my Parcel layer, by Parcel Number, and the app will zoom into the found Parcel. It's beautiful. But once found, we CAN'T turn any of our layers on or off, or do much of anything else that are basic map functions. If this FINDER functionality were incorporated as a Widget into Web AppBuilder, this would solve almost 90% of our problems with using Web Maps and Apps on ArcGIS Online. We could search a desired layer (parcel search by parcel number), zoom to the found object, and then do other things, like turn layers on and off (a basic function of any map), draw, measure, print, etc. We could even use the esri Geocoder to get close to the area of interest if the user did not have a parcel number available, or one was not found in the data. Icing on the cake would be able to have the FINDER widget allow us to search on more than one layer, or have the ability to add multiple finder widgets to the app so the user can search by several different layers by the attributes we allow. Now if this happened, that would get us 98% of the way to nirvana! Thank you for your consideration ... View more

The Web Appbuilder could benefit from a widget similar to the functionality found in the FINDER Configurable App. In the FINDER Configurable App, one is able to select a layer and a field, from one of the many layers in a map. For instance, I can configure the FINDER app to search on my Parcel layer, by Parcel Number, and the app will zoom into the found Parcel. It's beautiful. But once found, we CAN'T turn any of our layers on or off, or do much of anything else that are basic map functions. If this FINDER functionality were incorporated as a Widget into Web AppBuilder, this would solve almost 90% of our problems with using Web Maps and Apps on ArcGIS Online. We could search a desired layer (parcel search by parcel number), zoom to the found object, and then do other things, like turn layers on and off (a basic function of any map), draw, measure, print, etc. We could even use the esri Geocoder to get close to the area of interest if the user did not have a parcel number available, or one was not found in the data. Icing on the cake would be able to have the FINDER widget allow us to search on more than one layer, or have the ability to add multiple finder widgets to the app so the user can search by several different layers by the attributes we allow. Now if this happened, that would get us 98% of the way to nirvana! Thank you for your consideration ... View more