Latest Contributions by JoshuaBixby

Looking at Portal for ArcGIS 11.3 system requirements—ArcGIS Enterprise | Documentation for ArcGIS Enterprise, there is no mention of .NET components being a requirement.  Looking at ArcGIS Server 11.3 system requirements—ArcGIS Enterprise | Documentation for ArcGIS Enterprise, .NET 8 is only required if you are enabling the .NET Extension Support feature. ... View more

@DuncanHornby, since Esri only supports a few versions in that drop-down list, one would have no idea if a tool was introduced in 3.1, 3.0, 2.9, 2.8, etc....  All someone could tell from the drop-down list is whether it already existed in version 3.2. ... View more

Since different versions of products have different versions of requirements, and even different requirements entirely at times, it is best to state the version you are using.  Also, ArcGIS Server itself doesn't have any .NET requirements, the .NET Extension Support feature of ArcGIS Server does, but that feature only has to be installed if you are using .NET-based server object extensions (SOEs) and server object interceptors (SOIs). ... View more

Given how straightforward writing a simple URL redirect rule is on IIS or Java web servers, I doubt Esri will invest the effort to add this functionality.  My organization deploys numerous IIS URL rewrite rules to block access to certain functionalities on our external web adaptors, e.g., preventing generating a token to access an authenticated service. ... View more

"Enterprise 11.x" covers 5 versions, so making general statements about software requirements should be avoided since requirements can, and have, changed over 2 1/2 years. No version of ArcGIS 11.x requires any version of .NET unless one is using Server Object Extensions (SOEs) and Server Object Interceptors (SOIs) and has installed the .NET Extension Support feature.  If that feature is not installed, talking .NET versions is moot. For the .NET Extension Support feature, ArcGIS 11.0, 11.1, and 11.2 depend on .NET 6 while ArcGIS 11.3 and 11.4 depend on .NET 8.  Given ArcGIS 11.2 is a short-term support release, and ArcGIS 11.1 enters Extended Support in May 2025, I would not expect Esri to make any big changes to those releases at this point. ... View more

ArcGIS Enterprise 11.4.0 has Apache Tomcat/9.0.93 ... View more

@ToddW_stl, the link provided is dea. ... View more

Looking at the documentation, Geometry objects | ArcGIS REST APIs | ArcGIS Developers An open circular arc is represented by the c property. This is defined by an end point and an interior point. { "c": [ [<x>, <y>, <z>, <m>], [<interior_x>, <interior_y>] ]} It appears that the interior point of a circular arc cannot specify a Z or M value, only the end point can.  The same behavior with center points and control points exists for elliptic arcs and bezier curves. ... View more

I thought I have stated the following somewhere on Esri Community, but I can't find it right now, so I will excerpt one of my response on GIS StackExchange:  arcgis desktop - Calculate Sequential Values based on Boolean field - GIS SE. Looking to the section of the SQL standard that defines the behavior of cursors, ISO/IEC CD 9075-2 Information technology — Database languages — SQL — Part 2: Foundation (SQL/Foundation), it clearly states (at least through SQL:99 that I have seen in person, but I assume the same language exists in later editions): When the ordering of a cursor is not defined by an <order by clause>, the relative position of two rows is implementation-dependent. The importance of that statement can't be emphasized enough. Without including an explicit SQL ORDER BY clause, the user is leaving the order of records returned in a cursor up to the application or database management system. In this specific situation with ArcGIS Pro, Esri does not document how Calculate Field constructs the underlying SQL used to create the cursor. Additionally, many DBMSs explicitly state that no consistent ordering is guaranteed without including a SQL ORDER BY clause. For example, from Microsoft SQL Server SELECT - ORDER BY Clause (Transact-SQL): The order in which rows are returned in a result set are not guaranteed unless an ORDER BY clause is specified. With vendors either not documenting their ordering rules or saying no order is guaranteed without a SQL ORDER BY clause, a user can't know for certain the order ahead of time, and worse, the order may change over time even for the same data set. If one wants or expects a certain order of records, the only way to guarantee it is by using a SQL ORDER BY clause.  For file geodatabases, the unspecified order commonly is by ObjectID, but Esri has never stated that is a guarantee so they feel no need to share the internal mechanics of what may change row ordering in a FGDB table. ... View more

Thorough response, nice.  (Assuming generative AI didn't do it for you, but then maybe I should be impressed if it did) ... View more

@MarkZollinger, I made changes to the idea to focus on adding the information directly to the tool page itself like licensing information.  Please change the status of this idea since it isn't offered as now proposed. ... View more

The ArcPy Geometry constructors do not support true curves of any kind.  You will need to use AsShape—ArcGIS Pro | Documentation and feed it an Esri JSON definition based on the syntax from the 'Curve objects' section of Geometry objects | ArcGIS REST APIs | ArcGIS Developers ... View more

Although Esri supports "*" for fields with ArcPy DA cursors, they did so reluctantly, and it is a bad practice.  You should always explicitly list the fields in a cursor, then you always know the order regardless of the order of the fields in the table. ... View more