|
IDEA
|
There are a lot of parameters with Select By Location, it would be helpful if you shared what you are passing the tool, what results you expect, and what you are getting. The default for Selection Type for Select By Location is "New selection", and that starts fresh against the whole data set. If you already have records selected and want to select a subset, the "Selection subset from the current selection" would be the option you want to select.
... View more
yesterday
|
0
|
0
|
56
|
|
POST
|
Troubleshooting ArcGIS Enterprise performance problems is challenging enough when you have access to the systems and lots of detailed information, doing it with limited information via a forum is nearly impossible. There are so many factors that can impact ArcGIS Enterprise site and service performance that one has to be very detailed and specific when sharing information. Saying the machines are " all well spec'ed" doesn't really tell anyone anything. There are literally hundreds of Azure VM SKUs, and what one person might consider "well spec'd" another might few as barely up for the job. The comment "shared config on Azure SMB share" is also ambiguous since there are many ways to consume files over SMB in Azure ranging from Azure fully-managed cloud offerings to self-managed infrastructure, and a similar comment goes for saying "EGDB SQL Server." I am not saying the above to nitpick or detract from the situation and question, but to offer context for why it will be difficult to get meaningful feedback from community members. Even Esri Support has its limits in situations like this because it is focused more around addressing breakage rather than performance matters, and you stated nothing looks overtly broken from the logs. Maybe Esri Professional Services or some other consulting firm could help if the issue is impactful and important enough the business is willing to spend money on resolving it. I will say that I doubt the 500 mile WAN distance is the primary cause. That distance add 15 ms give or take to a network round trip, and modern web-based apps running in browsers are meant to tolerate 100s of ms of latency. I would start by taking the apps out of the equation and performance benchmarking the services they consume outside of the apps. The more layers you can peel away and isolate, the easier troubleshooting becomes.
... View more
2 weeks ago
|
1
|
0
|
124
|
|
POST
|
Are gridcode0 polygons only ever holes in a bigger polygon or can they touch multiple different gridcode1 polygons? A couple example graphics would be helpful for folks to see because there isn't enough information here for people to give a detailed response.
... View more
3 weeks ago
|
0
|
0
|
105
|
|
POST
|
Beyond Richard's questions, Python string comparisons are case sensitive. I noticed your code block shows if row[3] == "No Error" but your question states, "row[3] == "NO ERROR". Also, extra space padding in the string can cause an issue.
... View more
3 weeks ago
|
0
|
0
|
109
|
|
POST
|
Yeah, changing the licensing level from Advanced to Basic was a bit excessive. It is a trade-off going from Advanced to Standard, but going to Advanced to Basic really devalues the award/reward and personal use program.
... View more
3 weeks ago
|
2
|
0
|
250
|
|
POST
|
If you look closer at the __init__.py file, the class is not defined at the module level but within a specific function, so it cannot be imported and used directly from ArcPy. If you want to interact with it, you have to go through the object returned from the function. >>> import arcpy
>>> buffer_params = arcpy.GetParameterInfo("Buffer")
>>> type(buffer_params)
<class 'arcpy.GetParameterInfo.<locals>.ParameterArray'>
>>>
... View more
3 weeks ago
|
1
|
1
|
259
|
|
IDEA
|
I can't endorse/support this idea enough, any enterprise platform today needs to support multiple identity providers of the same type.
... View more
4 weeks ago
|
0
|
0
|
228
|
|
BLOG
|
@BrittanyLe , something the ArcGIS Pro Early Adopter program staff/teams do is send e-mails directly to former participants when new opportunities open. That doesn't appear to happen with ArcGIS Enterprise, at least it never has with me. Although I am regularly on Esri Community and usually see these kinds of announcements, relying solely/mostly on this announcement to notify folks isn't casting the widest net if engagement is what the product team wants during beta development and testing.
... View more
a month ago
|
0
|
0
|
229
|
|
POST
|
Are you using esriGeometryAny because you won't know ahead of time whether the geometry will be polygon? For testing purposes, does the following work? IGeometry geometry = this.jsonConverter.toGeometry(
jsonObject,
esriGeometryType.esriGeometryPolygon,
false,
false
);
... View more
06-18-2026
01:03 PM
|
0
|
1
|
461
|
|
POST
|
There are several registry entries related to licensing, not just AUTHORIZATION_TYPE. My recommendation would be to delete the following registry keys under HKEY_CURRENT_USER, doing so will reset the CONCURRENT_USE licensing for that user and prompt a user to login to a Portal or arcgis.com to get a Named User license. AUTHORIZATION_TYPE LICENSE_SERVER SEAT_PREFERENCE SOFTWARE_CLASS_FN All the keys but AUTHORIZATION_TYPE will be recreated for the user and set to default. Since the AUTHORIZATION_TYPE default has been NAMED_USER for a while now, it likely won't even get re-created. NOTE: Like anything involving registry changes, either backup the registry key involved or make sure you validate on test machines before deploying.
... View more
06-11-2026
07:04 AM
|
0
|
0
|
280
|
|
POST
|
If you run into issues with vertical scaling, one area I have seen people run into problems is managing memory, both physical and virtual, at the OS level. ArcSOC processes have a surprisingly large virtual memory footprint relative to their physical memory use, and when scaling RAM up to accommodate more services, I have seen virtual memory sizing and use become a problem. Without knowing a lot more details about the application and OS configuration and spec's, I can't really offer any specifics.
... View more
06-05-2026
10:30 AM
|
2
|
0
|
623
|
|
POST
|
Another aspect of why vertical scaling makes sense more than horizontal is licensing. I have always worked in large government organizations that deploy lots of what I refer to as "big brother" software, i.e., configuration management software, security software, monitoring software, etc.... Don't get me wrong, these types of applications are needed in today's environments whether they are small business or large government. As needed as they are, they consume resources and increase the amount of resources a machine needs compared to an idealized, bare-bones OS. For a previous organization I worked for, the rule of thumb was the first 2 vCPU were basically throw-away vCPU to support running all the big-brother software. This was more to do with poor management of the software by operations teams than the software itself. So, if capacity planning shows you would want 4 vCPU for a VM, we always spec'ed 6 to ensure the application would always have roughly 4 vCPU worth of capacity available. ArcGIS Server (not Portal, but Server itself) is licensed per core. Unlike some enterprise software like SQL Server where the cores can be set in the application, ArcGIS Server licenses all the cores on a machine. For situations like the one I describe where a certain number of vCPUs are set aside for other operations software on the machine, and yet those vCPU are still licensed for ArcGIS Server, horizontal scaling drives up licensing costs much quicker than vertical licensing because each new machine has those marginally used but still licensed vCPUs whereas adding more cores to an existing machine allows having the application use all those new cores. Regarding @Scott_Tansley comment about segmenting workflows into other ArcGIS Server sites, I agree, at least for medium to large customers. Each type of GIS service has its own unique patterns of use, both from the end-user consuming the service to the service consuming machine resources, and mixing them in large numbers often results in resource utilization and contention issues and capacity planning headaches.
... View more
06-02-2026
06:16 AM
|
1
|
0
|
756
|
|
POST
|
I agree with @MichaelVolz . ArcGIS 10.8.1 is fully retired in 2 months, 08/01/2026. Besides the imminent retirement of that version, there are also practical issues you will run into. Although it may technically work, trying to publish GIS services from ArcGIS Pro to older versions like ArcGIS 10.8.1 will lead to problems. You won't be able to publish GP services, and there is risk of corrupt or unexpected results in map and image services.
... View more
06-01-2026
02:01 PM
|
0
|
0
|
1063
|
|
POST
|
The largest multi-machine ArcGIS Server site I have ever deployed and managed was 6 machines, and I have deployed dozens of smaller multi-machine sites. The 6-machine site was always the least stable of all multi-machine sites, and I didn't realize how much horizontal-scaling was a factor until we added more resources to the machines and dropped from 6 machines to 4 and then eventually 3. I have come to strongly discourage scaling horizontally above 3 machines, and I encourage people to look at vertically scaling instead by adding resources to machines. Although Esri doesn't state there is a maximum to how many machines can be in a AGS site, there is definitely a practical limit, and I have found it is lower than one would think. The main issue with horizontal scaling becomes the shared working directories, especially the shared configuration store. The IOPS for adding a new machine to a multi-machine site have always seemed to scale linearly, which on the surface sounds OK when thinking of how algorithms scale with data set size. However, when the IOPS are as high as ArcGIS Server's shared configuration store, horizontal scaling really starts to chew up IOPS. Vertically scaling generates no extra IOPS except for those additional services you are running now that you have more resources. Without knowing more specifics of your service types and uses, it is hard to offer any specific suggestions. Is there a reason you can't vertically scale?
... View more
06-01-2026
01:55 PM
|
3
|
2
|
834
|
|
POST
|
I agree that ArcGIS Enterprise Functionality Matrix doesn't do a good job of explaining ArcGIS Enterprise Kubernetes functionality. There are statements about ArcGIS Enterprise Kubernetes, but they are more along the lines of "see this" or "see that" for information rather than clearly stating how Kubernetes functionality relates. That said, it seems like a simple question being asked, but it is hard to answer without knowing more of what you are really after. For example, since ArcGIS Enterprise on Kubernetes can federate with regular ArcGIS Server deployments, one needs to know whether someone's requirement is to only deploy in Kubernetes or whether a hybrid approach is allowed. If hybrid is allowed, than a lot more functionality and features are possible. The other complication is that the underlying architecture of deploying ArcGIS Enterprise on Windows or Linux vs Kubernetes is fundamentally different. Esri may make the REST APIs match, and the browser apps look and function the same, but under the hood they are very differently structured. Because of this, Esri will sometime use terms like "equivalence" instead of "parity," and they focus more on describing outcomes and workflows than features and functionality when talking about the two types of architecture. Overall, I agree with the sentiment that Esri does not do a great job helping customers understand the difference. Also, I really don't care for blogs as being "official" documentation, but the "Summary of Supported Functionality" in the What's New in ArcGIS Enterprise 12.0 on Kubernetes blog is about as authoritative as I have seen.
... View more
05-29-2026
08:22 AM
|
1
|
0
|
441
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 2 weeks ago | |
| 2 | 3 weeks ago | |
| 1 | 3 weeks ago | |
| 2 | 06-05-2026 10:30 AM | |
| 1 | 05-29-2026 08:22 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|