POST
|
I can't say it is the cause of your issue, but don't mix the field name wild card while also explicitly naming fields because it results in duplicate columns in the cursor.
... View more
Wednesday
|
1
|
0
|
104
|
POST
|
Regarding page file size, where did you get or see that statement? If a server needs a page file 3x the size of its RAM, I can guarantee any applications running on it are performing quite poorly. If you are not familiar already with the concepts and information in Introduction to the page file - Windows Client | Microsoft Learn and How to determine the appropriate page file size for 64-bit versions of Windows - Windows Client | Microsoft Learn, I encourage you to read both. A page file serves multiple purposes, and even with a given purpose, the use of a page file can vary greatly. Most of the rules of thumb were created in the early days of the Windows NT operating system when machines had much smaller amount of physical RAM, and they are far from optimal for modern servers with large quantities of RAM. In the articles I linked to, Microsoft explains how the "system managed" page file settings generally work. Unless you want to dive into process performance data to get a better understanding of how your applications are using memory, virtual and physical, it might be best to just let Microsoft manage it. As an example, the Windows 11 Professional workstation I primary use has 64 GB of RAM and currently the system-managed page file is 3 GB, that is 1/20th the size of physical RAM. The page file will occasionally grow by tens of GBs when I start pushing RAM consumption, but it seldom goes above 30 GB, which is still 1/2 the physical RAM. Could I provision a 128 GB or 192 GB page file manually? Sure, but why waste 128 GB of SSD storage on a page file that isn't used.
... View more
Wednesday
|
0
|
1
|
37
|
POST
|
The SQL LIKE predicate is a form of pattern matching, but it is not regular expression pattern matching. Although support for SQL LIKE is much more consistent across database platforms than regular expressions, there may be cases where it is implementation specific, so it is best to state what data source you are working with. UPDATE: An update to the question indicates you are working with file geodatabase data. As I mentioned already, SQL LIKE is not regular expression, and regular expression patterns will not work with LIKE, especially since Esri does not support character-class wildcards with the file geodatabase implementation of LIKE. Although undocumented, Esri does support a fairly robust regular expression implementation in the file geodatabase with the SIMILAR TO predicate. Oddly, they even kept the wildcard the same as LIKE even though actual regular expression uses different wildcards.
... View more
a week ago
|
0
|
0
|
156
|
POST
|
Can you explain where the server and desktop machines are located relative to the data sources behind the map? Is the map connecting to file geodatabases, enterprise geodatabases, something else, all the above?
... View more
a week ago
|
0
|
0
|
87
|
POST
|
As I mentioned in my first reply, I am not aware of any structural changes in the URLs of GIS services between ArcGIS 10.8.x and ArcGIS 11.3. As long as you define the map cache using the same parameters between 10.8.x and 11.3, the same tiles should be retrieved. I have republished cached map services on 11.x and re-used old/original tile caches so I didn't have to rebuild them.
... View more
3 weeks ago
|
0
|
1
|
121
|
POST
|
Does your field name have a period in it? For example, it looks like the field name is "inspection.date", which will definitely cause issues since that would make for 010085: <value> is an invalid field name.—ArcGIS Pro | Documentation Field names should only contain characters a–z, 0–9, and underscores. Do not use spaces, hyphens, parentheses, brackets, and other special characters, such as $, %, and #. Avoid using field names that contain words that are typically considered reserved keywords. These are typically data, day, month, table, text, user, when, where, year, and zone. Note that each underlying DBMS can have its own set of reserved keywords.
... View more
3 weeks ago
|
0
|
1
|
116
|
POST
|
With Calculate Field, there is no way to ensure row order, truly ensure it. So, doing order-dependent row operations is kludgy at best and generally error prone. With cursors, you can specify an ORDER BY statement to ensure row order, or you can loop through a cursor twice using a dictionary to store and update values. If someone else doesn't offer up some code, I will take a look in a day or so.
... View more
3 weeks ago
|
2
|
0
|
154
|
POST
|
Why does it have to be Calculate Field? This is much more straight-forward with cursors.
... View more
3 weeks ago
|
0
|
2
|
176
|
POST
|
Instead of manually checking it and cleaning it up, just create a scheduled task on each ArcGIS Server machine that will delete all the temp files on some regular basis. If a temp file is actively in use and has a lock, the file won't be deleted, but everything else will be.
... View more
3 weeks ago
|
0
|
0
|
119
|
POST
|
There are no structural changes in the URLs of GIS services between ArcGIS 10.8.x and ArcGIS 11.3, that is an existing image service that is upgraded will have the same URL as before, and a republished image service with the same name will also have the same URL as before. Is that what you are asking?
... View more
3 weeks ago
|
0
|
1
|
220
|
POST
|
If it is the datetime field causing the issue, then share an example or two of the datetimes from the web service and save community members the effort of having to go retrieve it themselves to help you. Retrieving the JSON, it looks like the web service is returning datetime as a string in the following format: "2024-08-21T13:08:33.583Z". That looks to be an ISO8601 compliant time format string, but currently the Data Access cursors cannot parse it (I have logged a defect already). So, you are going to have to manipulate the time string into a simpler format that can be parsed.
... View more
3 weeks ago
|
1
|
1
|
202
|
POST
|
As Chris is trying to help you tease out, there are a variety of issues that may be occurring. Instead of trying to troubleshoot what has happened over the past 18 months, why not clear out the temp folder and then start watching it more regularly. That way, you will have a much better idea of what is happening on ArcGIS Server around the time a bunch of temp files are created and not cleaned up.
... View more
3 weeks ago
|
0
|
0
|
134
|
POST
|
Are they using an Esri tool or software program to query? I am guessing not since you mention having "to provide multiple solutions for them," so how exactly are these users interacting with the REST API?
... View more
3 weeks ago
|
0
|
1
|
92
|
POST
|
You are mixing the two patterns of use for Editor—ArcGIS Pro | Documentation. In addition to the Esri documentation, there are lots of good primers online about the Python with statement and context managers.
... View more
a month ago
|
1
|
0
|
245
|
POST
|
If you ignore the error and hit Apply/OK, does it work correctly? It might be a validation defect for the expression rather than an actual error in the expression.
... View more
a month ago
|
0
|
1
|
121
|
Title | Kudos | Posted |
---|---|---|
1 | Wednesday | |
1 | 3 weeks ago | |
2 | 3 weeks ago | |
1 | a month ago | |
2 | 08-12-2024 11:56 AM |
Online Status |
Online
|
Date Last Visited |
3 hours ago
|