Latest Contributions by Jay_Gregory

Yes, I realized I was not a Professional or Professional Plus - thank you! ... View more

@SeanCulpan No resolution.  Curious to hear your sad story of failure if it has to do with collaboration - I've been having major issues maintaining a functioning distributed collaboration environment between AGE and AGOL and am considering just updating AGOL data sources separately.   ... View more

Anyone come to any solutions here - running into the same exact issue and tired of the sharing/unsharing hamster wheel ... View more

Thanks @ChristopherCounsell I was wondering if it was a threshold thing, but Esri told us with the M4 and that number of users we shouldn't be close.  We also spoke with @MarianneFarretta on one of our support calls.  We've looked at the DataStore metrics and the CPU is NOT plateauing, but still intermittently receive those errors - seems like a quota limit could be reached without stressing the datastore on an M4 though.  Out of curiosity, when you say "view the number of request units and total against your organization", what exactly are you referring to?  How would we do that?  ... View more

@JakeSkinner Thanks - though this seems a little beefy for a lot of use cases.  But my question is specific to large feature classes - I would like to use the following two methods:  def truncate_portal_data(fl_url:str)->object: """Truncates a feature layer or able through the REST endpoint Args: fl_url (str): REST endpoint of the feature layer Returns: object: results object """ ids = fl_url.query(return_ids_only=True)['objectIds'] results = fl_url.edit_features(deletes=ids) if len(ids)>0 else {"results":"No features to delete"} return results def update_portal_data(df:pd.DataFrame, fl_url:str, truncate:bool=True, chunk_size:int=500)->object: import numpy as np from time import sleep """Adds features from a dataframe to a Portal / AGOL feature service. Args: df (pd.DataFrame): DataFrame from which to update features fl_url (str): Feature service URL truncate (bool, optional): Truncate table before updating. Defaults to True. Returns: object: results of update operation """ if truncate: truncate_portal_data(fl_url) numchunks = int(len(df)/chunk_size) or 1 chunks = np.array_split(df,numchunks) for chunk in chunks: fl_url.edit_features(adds=chunk.spatial.to_featureset()) sleep(5) return True But my question is is there any reason your script is preferable over the much simpler API methods above for large feature classes? ... View more

This is an excellent script - thought seems a little beefy for a simple truncate and append if your schema is the same.  Seems like doing it with two methods is simpler.  However I was trying to understand if this was supported in truncate/appending large feature classes in AGOL.  def truncate_portal_data(fl_url:str)->object: """Truncates a feature layer or able through the REST endpoint even if sync is enabled Args: fl_url (str): REST endpoint of the feature layer Returns: object: results object """ ids = fl_url.query(return_ids_only=True)['objectIds'] results = fl_url.edit_features(deletes=ids) if len(ids)>0 else {"results":"No features to delete"} return results def update_portal_data(df:pd.DataFrame, fl_url:str, truncate:bool=True, chunk_size:int=500)->object: import numpy as np """Adds features from a dataframe to a Portal / AGOL feature service. Args: df (pd.DataFrame): DataFrame from which to update features fl_url (str): Feature service URL truncate (bool, optional): Truncate table before updating. Defaults to True. Returns: object: results of update operation """ if truncate: truncate_portal_data(fl_url) numchunks = int(len(df)/chunk_size) or 1 chunks = np.array_split(df,numchunks) return list(map(lambda x: fl_url.edit_features(adds=x.spatial.to_featureset()), chunks))   ... View more