*Message sent from a system outside of UConn.*

Our single largest credit cost by far comes from hosted feature layer storage. We have been pretty good about doing our geoprocessing locally rather than on AGOL, where it is quite expensive. We are considering limiting it through roles, just to be on the safe side. If someone truly needs AGOL geoprocessing for some reason, the role with the necessary privilege can always be granted temporarily to that person.

As for storage, you won't be in trouble if you have analysts creating hosted feature layers using input tables of a few thousand rows, but once you get to 500,000 and up (statewide roads, tax parcels, roof prints, etc.) you are talking real dollars (credits). To keep a lid on the credit costs you need to foster a practice of always asking, "Has someone else already published this data in a way I can consume?" It could be within your own organization, or even better, from an external authoritative source (the state GIS agency, for example). We try to nudge our analysts away from creating hosted feature layers with any data that we didn't develop in-house, ourselves because, chances are, it's already being served elsewhere.

The credit quotas per user can be helpful, but as far as I can tell, storage credits being burned by hosted feature layers are not associated with any particular user, including the user who created the hosted feature layer, and thus are not caught by the quota limits. Some of my most expensive culprits, host feature layer-wise, show up as having used 0 credits. Caveat emptor! 

David Knudsen  |  he, him, his
Chief GIS Programmer/Analyst
Central Transportation Planning Staff
Boston Region Metropolitan Planning Organization
857.702.3669 | [log in to unmask] | bostonmpo.org

 


On Wed, Jan 10, 2024 at 11:42 AM Dawn F. McCall, GISP <[log in to unmask]> wrote:

*Message sent from a system outside of UConn.*

Hi Jeff,

 

After you research what costs credits, I have also found it very helpful to set daily credit limits on all staff, including myself.  This will prevent any unexpected large credit consumption from processes. I set a 5 credit limit on all staff members and up the limit if I know we are doing a process that I expect a large credit consumption, then I set the limit back down the next day.  I have found that this is a great safeguard.

 

Good Luck, and please reach out if you would like to discuss further.

 

Thanks,

 

Dawn

------

 

CPA_Logo- BoldCodeTwo.png
Dawn F. McCall, GISP
Director of GIS
OFFICE: 609-857-2099 x2167
CELL: 609-850-1470
[log in to unmask]

www.cpasurvey.com
     

It is understood and agreed, that Control Point Associates, Inc., upon release of these electronic files no longer maintains control of its use, reuse or modification. Whereas we continue to certify the accuracy of the subject signed and sealed record documents prepared by this office, the user of this electronic media accepts full responsibility and liability for any consequences arising out of use of this data.

From: Northeast Arc Users Group <[log in to unmask]> On Behalf Of Tito Sanchez
Sent: Wednesday, January 10, 2024 10:37 AM
To: [log in to unmask]
Subject: Re: Expected Credit usage?

 

[EXTERNAL]: This email originated from outside of Control Point.

*Message sent from a system outside of UConn.*

 

Hi Jeff,

 

My primary reference is ESRI's 'Understanding Credits' webpage, which details the credit consumption for various capabilities like feature storage, imagery, etc. As Jen mentioned, additional credits can be purchased as needed. Understanding the credit usage for each capability is super helpful, especially for estimating monthly credit consumption.

 

 

 

Service credits are the currency of ArcGIS Online.

 

Don't hesitate to reach out if you have any questions.

 

Tito Sanchez, GISP

Senior Project Manager/GIS & Asset Management

BETA Group, Inc. | 401.333.2382

 

Build your future at BETA. Apply now!

From: Northeast Arc Users Group <[log in to unmask]> on behalf of Jeff Borofsky <[log in to unmask]>
Sent: Wednesday, January 10, 2024 10:09 AM
To: [log in to unmask] <[log in to unmask]>
Subject: Expected Credit usage?

 

CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you recognize the sender and know the content is safe. Hover over any links before clicking them and forward questionable emails to IT if you are unsure. Forward spam to [log in to unmask]

 

*Message sent from a system outside of UConn.*

 

Hi everyone, we are looking to start using ESRI products. We want to find out your experience with hosting datasets, research and shapefiles  to the public and how many credits we should expect to use annually.

 

Any advice and recommendations you can give me are welcome.

Thank you,

 

-- 

Jeff Borofsky

State Data Center Coordinator

Census State Data Center
CTData Collaborative (CTData) 

2389 Main St, Glastonbury, Connecticut 06033

Phone: 860.969.4360 ext 4360

https://link.edgepilot.com/s/35e46199/IfTv9Hc_qUGAyqZKIAclAw?u=http://www.ctdata.org/

 Click here to sign up for CTData’s newsletter!

Have data questions? Email our Data Helpline! 

       

 

 

 



Links contained in this email have been replaced. If you click on a link in the email above, the link will be analyzed for known threats. If a known threat is found, you will not be able to proceed to the destination. If suspicious content is detected, you will see a warning. ------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to https://link.edgepilot.com/s/cb27853d/RUb9nzQOOUCEJOnG_0LQZw?u=http://s.uconn.edu/nearcsubscribe.



Confidentiality Notice:

This email message (and any attachments) contains information from BETA Group, Inc. that is confidential. If you are not the intended recipient(s), you may not disclose, copy, distribute, rely upon, or use its contents. Please reply to the sender immediately and delete this message. Thank you for your cooperation.

------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to http://s.uconn.edu/nearcsubscribe.

------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to http://s.uconn.edu/nearcsubscribe.


Please be advised that the Massachusetts Secretary of State considers e-mail to be a public record, and therefore subject to the Massachusetts Public Records Law, M.G.L. c. 66 § 10. 
------------------------------------------------------------------------- This list (NEARC-L) is an unmoderated discussion list for all NEARC Users.

If you no longer wish to receive e-mail from this list, you can remove yourself by going to http://s.uconn.edu/nearcsubscribe.