Latest Contributions by SamuelKrueger

I want to make a polygon representing the exact extent of my layout's map frame that I can view when working with data in the map itself. The concept would be similar to the existing Extent Indicators, but they would be an actual feature class. Two reasons I used this in ArcMap (used a third-party tool): For placing annotations. When I'm hand-placing my annotations in the map view, I want to know precisely where the edge of the map frame is. For setting up map books. I used to set up a layout based on one view extent, then create the extent polygon feature and copy it multiple times and move those polygons around to set view extents for each sheet in the map book. Seeing the polygon in the map view is necessary in order to be able to predict the exact extents that will be visible on each resulting page. If I could see the existing Extent Indicator in the map view even though it wasn't converted to a feature class, that would at least solve problem 1, but it wouldn't solve problem 2. Same goes for activating the map frame in the layout view, although in my experience that adds so much processing overhead as to be a very frustrating workaround. ... View more

Fully expose to each individual user exactly how many credits each of their individual items consumes. Add "Credits per month" or some similar attribute to the details section of each item. Allow users to sort their own content by credit consumption. It's not fair for me to ask my users to moderate their credit usage when there's not enough information available to them to make such basic decisions as, "Is this item worth this many more credits than that item?". Exposing to the user their individual credit budget is not sufficient. They need information that will allow them to make decisions about the relative value of their individual items. Additional benefit: Many users are afraid to do anything because the credit consumption is so opaque. If you want people to use AGOL, you need to let them know how much it is (and isn't) costing them. ... View more

My organization would like to allow users to create web maps and apps from existing data and layers without allowing them to upload files themselves. We have two problems with users uploading files: Users upload unnecessary copies of existing data which soon go stale. Other users then find those copies and use them. The new Authoritative Data tag is helpful but not sufficient to address this problem. Users upload data that, for security reasons, needs to remain within our firewall. But we want to encourage users to make their own story maps and such. We would like to provide authoritative layers that should be sufficient for most users, and restrict the upload of files to only a select few users whom we will train and mentor. Our proposed solution: Under the "Content" section of the user role privileges, the "Create, update, and delete" privilege should not include upload privileges. "Upload files" should be a separate privilege. ... View more