Reduce Storage credit consumption

[KhoajaKhaled]

Hi GIS community, 

Is there a way to reduce ArcGIS online credit consumption. I cleaned the unnecessary files and layers, but still it consumed most of the credits. What is your experience and advice. 

Appreciate it.

Thanks

[Richard_Purkis]

Hi @KhoajaKhaled 

Thanks for getting in touch

It is difficult to provide advice that applies to your particular organisation without knowing how much content you are hosting on ArcGIS Online and what your workflows require.

From my experience in Technical support I can point you in the direction of the documentation to make sure you:

• Identify what services are using the most credits. Are these required?
• Analyse credit consumption. Are credits being used for services other than feature storage?

Following on from that it may be worth having a discussion with you Account Manager as they will hopefully know your workflows and be able to advise if there are any better solutions for more efficient credit consumption.

Hope this helps

[james-noble]

Hi @KhoajaKhaled, Esri also recently introduced functionality to generate credit reports to help you understand which items are consuming the most credits: Report fields—ArcGIS Online Help | Documentation

[MichaelVolz]

Where is most of your credit consumption originating from - storage vs analytics vs other?

If storage is a problem, do you also have an enterprise environment where you can serve the data from on-premise source thru an enterprise service and reference the data in AGOL from the service URL so you would no longer be using feature storage credits?

I would look into seeing if some of your AGOL content can be obtained from external services so you could then delete that content from AGOL and free up storage.  An example of this would be if you have floodplain data and hosted it up into AGOL.  AGOL and/or Living Atlas has references to a FEMA floodplain service which you could possibly use instead.

[ChristopherCounsell]

Feature storage consumes 200x more credits per mb than other items. If you have large, complex layers (e.g. property boundaries for a country) they will likely consume the most.

There are a lot of great resources. Here is one that walks you through all of it - including how to identify and approximate the credits for each item.

https://esriaustraliatechblog.wordpress.com/2021/06/22/which-arcgis-online-items-are-consuming-the-m...

[kreansanm]

I used drive time analysis tools in map viewer classic, for 5-30 minutes driving time with 5 minutes interval. And just a single analysis used 90 credit. Is it common for this to happen?

Before doing this, I've tried doing similar analysis but that didnt take much credit.

The different between the two is the point file input. For one, I create the point file in arcgis online (didnt take much credit), but when I upload a zip file containing point shp to do the analysis it takes 90 credit.

[ChristopherCounsell]

For generating travel areas (also known as drive-time areas), you are charged for each travel area generated, so if you were to generate three travel areas (2, 5, and 10 miles) for eight locations, you would be charged for 24 travel areas. For more information about credit consumption when using analysis tools, see Understand credits for spatial analysis.

https://doc.arcgis.com/en/arcgis-online/analyze/generate-travel-areas-mv.htm

I would assume the credit amount is different because:

• The number of features in the point file input is different
• The number of service areas (minute intervals) is different
• The service areas have a secondary analysis, such as geo-enrichment

[LindsayRaabe_FPCWA]

We're stuggling to reduce our credit consumption too at present. Ours is all around feature service storage (no analysis) and it seems that a lot of it is from 3 or 4 layers that have a lot of offline replicas (most of our data is offline enabled). Is there any way of reducing the consumption from those services without breaking the offline connections in our field staff offline maps?

[ChristopherCounsell]

How many maps?

Replicas and backend tables can be stored against the Hosted View Layer.

You may be able to take an alternative approach of:

1. Create new Hosted Feature Layer Views
2. Create new maps with the new Views
3. Encourage users to sync data (check in replicas) over a period and migrate to new maps
4. Unshare original maps and feature service / view (removing sharing over delete means you still have an opportunity to sync if users didn't bother syncing in step 3.
5. You can now delete other views, or delete replicas from the original feature service.

Toggling sync would achieve this but if you shared the original feature service it will require sync to support the views, so you would need to use python to drop all the replicas while still allowing sync on the new view layers. You'd also have the benefit of using Views moving forward. I always encourage people to never share the original feature service.

You could also manually or programmatically delete replicas but I'm not sure how you'd identify which are still in use.

[LindsayRaabe_FPCWA]

A bit of context from our org summary:

LindsayRaabe_FPCWA_0-1692239573953.png

LindsayRaabe_FPCWA_1-1692239579095.png

LindsayRaabe_FPCWA_2-1692239585313.png

Thankfully we already use Views for the majority of feature services in our maps. I've just gone through and done some Change Log Trimming to see if that makes any difference of significance on the 3 largest feature services. I'm hoping it does! 

We're also assessing what data we have in AGOL which may not be getting utilised enough to warrant the storage and removing where we can in full.