IDEA
|
Please provide documentation on the limits on the number of REST API calls that can be made for ArcGIS Online or ArcGIS Enterprise. When I try to iterate over the thousands of items in my AGOL org and obtain data about them using the REST API, I will often get errors like the following: {"error":{"code":400,"messageCode":"GWM_0026","message":"Too many requests. Please try again later.","details":[]}} These messages don't appear at first, but after a few minutes of a tools like FME or Python iterating and calling REST endpoints, this message will appear. If I knew what the limits were I could tell my FME or Python script to slow down to stay within the limits. The only documentation i've seen on API limits talks about how many responses you can get for something like a call against a feature service. They don't talk about how many times you can call that endpoint per second or per minute.
... View more
11-07-2022
11:47 AM
|
0
|
0
|
882
|
IDEA
|
@Bud Maybe database triggers would work if the data is branch versioned since that eliminates the complication of delta tables being involved that the triggers aren't aware of. We are still getting familiar with how the branch versioning works so maybe we'll rediscover some tricks that weren't applicable with traditional versioning and the delta tables However, the better thing would be for Esri to allow calling a function. That way our RDBMS savvy developers can build the functions, and then allow our GIS analysts to leverage them in attribute rules on the feature classes they maintain. The nice thing about attribute rules is they live with the feature class definition, so no matter which Esri method you use to edit the data (Pro, Enterprise feature service, Geoprocessing tool), the same attribute logic is applied and esri handled, and the management is exposed on the ESRI GUI side for GIS analysts. We are already having to implement attribute rules that come with newer Esri data management solutions, so it would be better to have all the custom data entry logic in one place, rather than having some in attribute rules and some in custom database triggers, and then you have to wonder which fires first. Esri already allows calling a sequence from Arcade with the NextSequenceValue function. This expects that the user/dba has setup the sequence and granted the appropriate privileges for it to be used. If they are okay with that then I don't see harm in expanding to also allow referencing a database function and assume that the DBA/Analyst will manage the function and privileges. Esri may have to stipulate that the function only return one value, but that should cover most situations.
... View more
11-07-2022
07:01 AM
|
0
|
0
|
816
|
IDEA
|
I'd also add that query layers that are not spatial should be included as well. Not sure if those kinds of views will appear as "Standalone Tables" instead of Feature Layers, but I think they should be included as well, so their data source can be parsed in python as well.
... View more
10-06-2022
02:45 PM
|
0
|
0
|
1572
|
IDEA
|
We have several aprx files in our organization, and I'm trying to iterate over them and determine the data sources for each layer in them. We have some query layers that are commonly used throughout our organization for viewing certains datasets in our enterprise geodatabases. Currently when I use Arcpy.Describe on these query layers, the dataset type returned is 'FeatureLayer, which isn't accurate. Through the Pro UI, this same layer shows a type of "Query Feature Layer" when I inspect it's properties. The propertie window also shows the actual database query used by the layer, a property that is unique to query layers. It would be great if query layers returned a unique dataType when being described so I know to process them a little differently. Then it would also be nice if the describe object returned also included a "Query" property that contains the text of the SQL query. This way I can parse that text and determine what table (or multiple tables) are referenced by this map layer.
... View more
10-06-2022
02:35 PM
|
4
|
3
|
1597
|
IDEA
|
Add a new arcade function to the library that allows the code to call a database function. The value returned by the function will be populated into the field. This could be very similar to the NextSequenceValue function, but instead of providing the sequence name, the user would provide the database function name. For my organization, this would allow us to build attribute rules that could call other Oracle databases (like our permitting system) via database links. For example if a GIS user is entering a new subdivision record, they would enter the permit number in one column. This new feature would allow us to call a database function with that permit number, retrieve information about the permit from the other database via a database link, and then auto-populate that information on the GIS record in other columns.
... View more
10-06-2022
05:57 AM
|
1
|
3
|
926
|
IDEA
|
I noticed that the copy and paste does not bring over the precision and scale if they are present. So I guess I'll open up a follow up enhancement request along the lines of "copy and paste all columns in the fields view regardless of what is displayed."
... View more
09-21-2022
11:16 AM
|
0
|
0
|
3934
|
IDEA
|
I am trying to create a python script to catalog all items in our geodatabases and their configuration using arcpy.Describe. Currently there is no way to determine if a feature class, table, or other item is branch versioned. The closest thing is the '.isVersioned' property for datasets (link). However, this is just a boolean value. So if a dataset is versioned there is no way to return if it's configured for traditional versioning or branch versioning. This is becoming important for us as we transition many of our geodatabase items into a ArcGIS Enterprise web services model for editing. It would be helpful to run a scan of all geodatabase items and return a table documenting which are not versioned, which are still traditional, and which are now branch to assist with our transition. I guess the best way to add this information to Arcpy is to add a new property named "versionType" to the dataset object(link). If the dataset is versioned it would return the value "Branch" or "Traditional". And if the dataset isn't versioned then I guess this property could have a null value or just not be present at all on the object.
... View more
09-20-2022
08:24 AM
|
20
|
5
|
1575
|
IDEA
|
Please add Microsoft's python libraries for interacting with Azure Blob Storage and Azure Data Lake storage to the standard installed libraries. After processing some reports in Notebook server about our geodatabases, Enterprise portals ,and ArcGIS Online environments, I want to then write the csv results to a folder in an Azure Data Lake. However, those libraries aren't in the standard library list. With notebook server focused on data science and ML, I figure being able to read and write from Azure, AWS, and Google's Blob/Data Lake storage platforms would be a common use case. Thank you,
... View more
08-21-2022
01:28 PM
|
0
|
1
|
1006
|
IDEA
|
Please create some way to obtain the definition query applied to existing map/feature services that reference an enterprise geodatabase. From my experience, once the service is published from Pro, there is no way through the REST API to determine if a layer in the service is applying a definition query against it's source geodatabase feature class. On the admin side of the REST api, you can access the manifest .json file, but it only tells you the feature class names....not if the definition query is applied. The only way I've been able to find some info on this is to inspect the manifest .json, find the name of the onserver .msd file that was uploaded by Pro, log into the server and browse to that file, then open it and inspect the definition query on the layer.
... View more
07-28-2022
08:55 AM
|
1
|
0
|
829
|
IDEA
|
Add a column for the folder the item is in to the administrative item report. The folder item's are stored in often helps with organization, especially for accounts that manage many items on behalf of the organization. Having these folder names on the report next to each item would help admins filter data on the output report csv data. I will create a separate idea for this to be implemented on this report's counterpart in ArcGIS Enterprise 10.9+
... View more
07-06-2022
06:02 PM
|
0
|
0
|
184
|
BLOG
|
@Anonymous User , I tried to click the link for the "Create Detailed AGOL Usage Report for Every Item " bullet point, but the article was removed. Was wondering how this was partially implemented so I can go try it?? Trying to get daily (or at least monthly) counts for 20,000+items in our org on a regular basis, without blowing up the API's.
... View more
06-22-2022
08:55 AM
|
0
|
0
|
215
|
POST
|
Thanks Josh, I'm not that getting those elements when I navigate to the json for my layer. I'm looking at this URL logged in with an admin account: https://<myArcGISServerUrl>/server/rest/services/<MyServiceName>/MapServer/0?f=pjson my portal and arcgis server are 10.9.1 Was your example from a hosted feature service by chance? I found this article that walks through how to navigate to this spot in the json, but it's for a hosted feature service. In my scenario I am trying to find the definition query for a layer in a service referencing an enterprise geodatabase. The service creation process would be something like 1)a GIS Analyst opens pro and adds a feature class from the geodatabase to the map, 2) adds a definition query to the layer, 3) then publishes to Portal or Server as reference with features access. Now 6 months later someone asks me the admin "why doesn't this feature layer have all the features in it from the original feature class? -Andrew
... View more
06-17-2022
12:02 PM
|
0
|
0
|
1359
|
POST
|
I'm trying to determine if a definition query is applied to a layer in a feature service referencing one of our enterprise geodatabases. Does anyone know how to grab the applied definition query via the REST or Python API's? Here's where I've looked so far. The REST API response(documentation link) for a service layer doesn't contain this information. I am able to grab the service manifest via REST (documentation) and inspect the JSON. It contains the connection properties for source geodatabase, and the name of the feature class used by each service layer. However but it doesn't contain any information about the definition query either. The manifest does show a serverpath for the location of the service's .MSD file on the server's disk. Therefore I'm guessing this definition query information only lives within the MSD file itself. My server admin was able to grab the msd file for me off disk and I verified the definition query is buried in there. I guess I could write a script to grab the file and parse it, but figured this would be somewhere in the server admin interface or API's.
... View more
06-17-2022
10:05 AM
|
1
|
5
|
1418
|
POST
|
Thank you both for your responses. I got confirmation from the product team that state zero is not required for the upgrade. After speaking to our team about the history, seems like there were some problems in the early years of our geodatabases, circa 2007-2012. Details are fuzzy, but at the time there were problems with the upgrade. One of the things support recommended was "let's try upgrading with things unversioned", and so after that we started doing it as a practice to be conservative. We usually used the opportunity to do large schema revisions anyways so unversioning wasn't a bad thing anyways. Still good to know what's required and what's a nice to have. Thanks again!
... View more
06-02-2022
12:44 PM
|
1
|
0
|
902
|
POST
|
Does anyone out there follow a practice of compressing your enterprise geodatabases to state zero before upgrades? For example when upgrading your geodatabase version from 10.6.1 to 10.7.1, or upgrading the Oracle version from 12c to 19c. We have done it in my organization on our Oracle geodatabases as far back as we can remember. I think it was a requirement in really early versions of the geodatabase that supported versioning (8.3 or 9.0??) or maybe it was required to avoid a bug in early versions, but I can't find anything to back that up. Regardless, compressing to state zero prior to upgrade is not spelled out as a requirement in any of the documentation for recent versions. I'm wondering if we could start eliminating this step as it seems to just be a cautionary one to make the geodatabase a little simpler before the upgrade, so I'm just curious if others do upgrades with lots of transactional versions floating around without any issues. Thank you, Andrew
... View more
05-27-2022
07:12 AM
|
0
|
3
|
970
|
Title | Kudos | Posted |
---|---|---|
1 | 07-28-2022 08:55 AM | |
6 | 12-14-2023 07:15 AM | |
8 | 12-14-2023 06:52 AM | |
3 | 11-08-2023 06:34 AM | |
5 | 07-14-2023 07:32 AM |
Online Status |
Offline
|
Date Last Visited |
Friday
|