Latest Contributions by MarianneFarretta

Hello NR96--this sounds like a great lesson! Integrating csv with web GIS has so many practical applications. A few thoughts: Sketch layers will be supported as analysis input (including Join) in the June 2023 update, which is coming up on Tuesday. To achieve the equivalent functionality to your Map Viewer Classic workflow using Map Viewer, you would use a Hosted Feature Layer with point geometry. This will create both the geometry and also tabular data which can be used for joins and many other operations.  I hope you find that helpful--let me know if you have other questions and I'll be glad to offer additional direction. ... View more

Hello, I'm the Product Manager for Feature Data Store and Map Viewer; thank you for a great question! This limit is not quite what it appears at face value--the "query" limit does not mean a specific number of queries. Rather, it means a specific number of Request Units, which is a system we invented to tell our backend systems when the database is being asked to perform more work than it can comfortably handle. It is not a one-to-one relationship to actual queries; different query types are weighted and the query rate limit is based on the cumulative "weight" with which the Feature Data Store is being tasked. This limit is defensive--it's like the red line on your vehicle engine. It's not a proactive design tool; we use it to avoid overwhelming the database to the point of shutting it down. You can watch a parallel metric in your Feature Data Store usage chart, which shows you the draw on your database compute resources. This is the tool I recommend be used for design and planning. We expect to lift this chart into orgs using Standard Feature Data Store later this year. Tracking your ArcGIS Online Feature Data Store Key Health Indicators Once the organization's query rate limit is reached, a one-minute "cooling off" period is triggered during which non-repeatable queries (i.e. those which cannot be answered by a cache) are responded to with a 429 error. This gives the database time to cool off, and interrupts clients with a cautionary response.  The limit is in the header--and though it does apply to the entire organization, it is defined by the size Feature Data Store you are using. The query rate limit increases with Feature Data Store size. I'd like to understand more about your ideas regarding map performance. Feature Data Store is only one aspect of map performance, and its correlation to feature service performance is best reviewed using the usage chart. I'm interested to know what kind of performance you want to track, who in your org should see it, how it would be accessed--lots of questions! I'd love to schedule a chat for follow-up if you're available; you're welcome to send me your email and we can set something up. Thank you, Marianne Marianne Farretta Product Manager | ArcGIS Online Map Viewer | Premium Feature Data Store mfarretta@esri.com ... View more