Latest Contributions by MarianneFarretta

Hi Molly! The link below describes Esri's use of "Customer data," which I believe directly addresses your question. Overall, both data security and privacy are core values of the ArcGIS Online product; we do not distribute your data; we provide a structure from which you can create, secure, share, and ultimately control your content. If you have additional questions beyond what's covered here, let me know and we'll connect to find the right path forward. https://www.esri.com/en-us/privacy/privacy-statements/privacy-supplement ... View more

I see, thanks Amanda! I missed the nuance in your original post " hex value's #" but I understand it now. Thanks for the update, and stay tuned... ... View more

Hi Amanda, and thanks for the feedback! I see the inconsistency you're describing and I can understand how it disrupts your workflow. One thing that may help for the short term: the hex value is available within the label settings--it's just not labeled "Hex" as it is in the Style options.  We'll take a look at this and the gradient as we continue refining the labeling options--thanks again! Update: my colleague @RussellRoberts1 just reminded me this enhancement is targeted for March 2022, so we'll expect the same layout in the labeling as presently found in the Style options.  Thanks again!   ... View more

Hi Tim, thanks for posting! Can you share an example URL/item?  ... View more

Hello Sam, I’ll be happy to schedule a time to discuss your individual organization, and will leave this info here to get us started: When following best practices for high volume apps (linked below), your organization’s read-only public apps will not incur rate limiting. Rate limiting is a protective measure which has been in place on ArcGIS Online’s infrastructure for many years and continues to evolve and improve over time. This is how we ensure “noisy neighbors” cannot draw resources away from other users of the shared multitenant SaaS architecture. Premium Feature Data Stores are dedicated databases, but other components e.g. web servers remain shared and their resources allocated equitably. Essential Configurations for Highly Scalable ArcGIS Online Web Applications (Viral Applications) Premium Feature Data Store (e.g. M4) is intended to support high volume concurrent editing, complex analysis, and other database-intensive workflows. Although an M4 may successfully support viral load for a specific public application, it is likely not necessary if the layers and app are configured following the recommendations for public apps. These recommendations offload the database work to a Content Delivery Network (CDN), supporting scalability well beyond what the database could handle directly. ArcGIS Online Best Practices for Configuring Public Viral Layers Here are some additional resources to review, and please send me an email if you’d like to discuss your organization’s needs directly—I’d love to learn more about what your org is doing and how we can help streamline your efforts. --Marianne Scalable hosted feature layers in ArcGIS Online: Tile queries and response caching ArcGIS Online: Best Practices with Hosted Feature Services ... View more

Hi Thorsten!  This is a good idea, thanks for articulating it and sending it to the community. There are ways to achieve similar functionality, but the ones I'm thinking of aren't exactly what you describe. Here's why: If the legend changed dynamically with the map window, each and every movement by any user on the planet would initiate a different query. The extent of their map window would be unique--to their browser, their machine, etc. Much of what we engineer in ArcGIS Online aims to facilitate repeatable queries--those for which responses can be cached on edge servers which are close to the end users. This is how ArcGIS Online scales its maps and apps to meet the viral demands of Covid dashboards, utility outage viewers, etc. So although we might be able to engineer what you're describing, for an application which generates high usage, I'd recommend using repeatable queries consistently. We're always pushing the technology, so the story isn't over yet... we'll see what the future holds. In the meantime, you can learn more about repeatable queries and response caching here: https://www.esri.com/arcgis-blog/products/data-management/data-management/scalable-hosted-feature-layers-in-arcgis-online-tile-queries-and-response-caching/ And in another week or so, we'll have some links available from our 2021 Developers Summit which dive deeper into the details. I'll make sure to post them here for your review. Hope that's helpful! Marianne ... View more

Hello everyone! I'm one of the ArcGIS Online Product Managers, and a colleague recently drew my attention to this thread which I see is still active, but hasn't had recent input from the Product Management side. Nested folders make good sense to my mind; I organize everything in this manner. Even file cabinets have drawers >> dividers >> folders >> tabbed folders. It feels like the natural order of things.  The good news is: Content Categories achieve the same organizational continuity offered by nested folders.    In the screenshot above, the Marianne DRP Work has two sub-categories, one of which has its own subcategories. This is analogous to a root folder and the subfolders within. You can make these as sophisticated or as simple as suits your requirements. I find Content Categories organizes my content as I am accustomed. And I gain flexibility unavailable with subfolders: a single map, app, or layer may be associated with multiple content categories.  Kelly Gerrow has also written a more in-depth analysis of Content Categories in this blog: https://www.esri.com/arcgis-blog/products/arcgis-online/administration/content-categories-four-ways-... Hope that's helpful, and happy categorizing!   ... View more

We do not publish a hard limit for number of Hosted Feature Layer Views in ArcGIS Online, but generally recommend staying aligned with the ArcGIS Enterprise limit of twenty. ... View more