POST
|
Regarding your first question about ArcSOC.exe, you won't need to do anything for that process if you address the ArcGISServer.exe process because CPU affinity is inherited by child or spawned processes.
... View more
yesterday
|
1
|
0
|
11
|
POST
|
Looks to have a misconfigured certificate on the web server: NET::ERR_CERT_COMMON_NAME_INVALID
... View more
|
0
|
0
|
34
|
POST
|
Spent time working through the issue with Esri Support, and it is complex. The issue has nothing to do with any specific type of workspace, nor anything with CalculateGeometryAttributes itself, it has to do with how Esri has structured their code for hundreds of Python-based tools like CalculateGeometryAttributes. There are literally hundreds of tools that will all fail to run with Python multiprocessing. The crazy part is, for most of the tools only a single line of code needs to be changed to make it work. The question then becomes are these issues with documentation or the software, are these defects or enhancement requests, etc.... I haven't closed out the Esri Support case yet, but I suspect it will be a mixture of documentation defects and software enhancements that come out of it. In the meantime, one can at least roll their own code with ArcPy DA cursors.
... View more
2 weeks ago
|
1
|
0
|
70
|
POST
|
Beyond the filters, you are not correctly using the ArcGIS Arcade DateOnly function. You are passing the function a feature set and column name, which it has no idea what to do with, so that could be why null is getting returned.
... View more
3 weeks ago
|
0
|
0
|
147
|
POST
|
Are you sure the issue is date related? If you remove the date-related queries do the other queries work as expected? If the GRID_ID query is not working correctly for some reason, then it won't matter whether the MARKED_YEAR query is working or not.
... View more
3 weeks ago
|
0
|
1
|
161
|
POST
|
Commented at python - ArcPy function produced None values in multiprocessing - GIS SE, it looks to be a defect with CalculateGeometryAttributes. I was able to create a minimum reproducible example and have submitted to Esri Support to log a defect.
... View more
3 weeks ago
|
2
|
2
|
277
|
POST
|
Although the name is zoomToAllLayers, the documentation shows there is a selection_only parameter. The ArcMap script using dataframe.zoomToSelectedFeatures is not layer specific so all selected features across all layers determine the extent, which is the same as zoomToAllLayers.
... View more
4 weeks ago
|
0
|
1
|
258
|
POST
|
I suggest you start here: ArcGIS Enterprise Pricing | Contact Us for Cost & Configuration Options (esri.com) . Although the web page title says price, it is really more information about licensing than pricing itself. You need to call Esri to discuss pricing.
... View more
4 weeks ago
|
1
|
0
|
143
|
IDEA
|
I think this is impossible to implement. Currently the Select Layer By Attribute tool is a SQL clause builder, and the available conditions in the drop down all map to standard SQL operators that nearly every data provider supports: SQL operator = is equal to <> is not equal to < is less than <= is less than or equal to > is greater than >= is greater than or equal to [NOT] LIKE begins with does not begin with ends with does not end with contains the text does not contain the text [NOT] IN includes the value(s) does not include the value(s) IS [NOT] NULL is null is not null When you go outside the common SQL operators above, the implementation of a given operator starts to vary widely across data provider, to the point of not being supported at all. Additionally, all of the common SQL operators above operate on a given row where finding duplicates requires looking beyond a given row to an entire dataset itself. There are numerous ways to find duplicates via SQL, and someone can always write custom SQL in Select By Attributes, but that requires knowing what the underlying data provider supports for SQL. I understand the convenience factor of having such an option, but I just don't see it implementable without completely refactoring the tool.
... View more
4 weeks ago
|
0
|
0
|
161
|
POST
|
Have you tried anything yet? Which part of translating arcpy.mapping code to arcpy.mp are you stuck on? I would start with Migrating from arcpy.mapping to ArcGIS Pro - ArcGIS Pro | Documentation, it has good code examples to at least get you to opening a specific map.
... View more
4 weeks ago
|
0
|
0
|
291
|
POST
|
I just tested the text template in Pro 3.3, and it works fine for me. Without more details about the exact workflow/steps you took to testing the expression, I can't offer anything else.
... View more
a month ago
|
0
|
1
|
186
|
POST
|
The OP's comment was more about the poor performance of shared instances after warm-up compared to dedicated instances, so raising the minimum instances of the dedicated instances that are already performing better isn't going to change anything.
... View more
a month ago
|
0
|
2
|
145
|
POST
|
The change was forced because of a Windows system limitation that prevents Portable Executable (PE) files, which include self-extracting ZIP archives, from being larger than 4 GB. When the contents of a self-extracting ZIP archive get larger than 4 GB, a sidecar file has to be used. See 64 bit - what is the maximum size of a PE file on 64-bit Windows? - Stack Overflow for a bit of discussion on the topic.
... View more
06-06-2024
07:12 AM
|
3
|
0
|
280
|
POST
|
You should be using Part-1 Introduction to Spatially enabled DataFrame | ArcGIS API for Python
... View more
06-05-2024
10:11 AM
|
1
|
0
|
186
|
Title | Kudos | Posted |
---|---|---|
1 | yesterday | |
1 | 2 weeks ago | |
2 | 3 weeks ago | |
1 | 4 weeks ago | |
1 | 06-02-2017 07:59 AM |
Online Status |
Offline
|
Date Last Visited |
7 hours ago
|