Hi, apologies if this has been requested before although I couldn't see anything in the ideas search but I would like the ability to put a limit on the size of feature services our users can publish to ArcGIS Online.
We have a lot of users and limited credits and whilst as an administrator I can limit users credit usage for some activities I cannot limit their credit usage for feature storage. Currently we have alerts configured using a python notebook whenever a user adds a feature service over a certain size so we can review whether it needs to be on the system. We try to educate our users on what should be published and ways to to reduce the size of their layers but we still get plenty of datasets going up that cover large areas not needed (e.g. the whole country rather than just the project area), contain data and fields not needed or just don't need to be published at all as the data already exists as an external service.
As an admin it is extremely frustrating and time consuming having to regularly check this and remind our users of their datas credit consumption. Without our custom notifications the first we would know about these datasets is when we spot the jump in credit usage, which cannot be got back once consumed. It would be great if instead we could simply configure a size limit to any datasets so when a user tries to publish they are blocked from doing so. If the larger dataset was really needed there could maybe be an option to add an exception list for feature services with a certain name.
It feels like this should be very do-able as Esri allows us to limit credits for other activities and also provides ways to see credit consumption for some tools in ArcGIS Pro so would be great to know if this could be considered for feature service publishing.
Thanks
Anthony
Great shout. At the very least a warning message based on projected credit use of larger datasets (over a certain size) to make the user aware would be beneficial. It's probably fair to say a large number of people with the power to upload data, don't necessarily have the foresight to think about this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.