Latest Contributions by JoshuaBixby

@TanuHoque , thanks for chiming in on this discussion and for considering the idea.  @DavidFotheringham1 , thanks for posting the idea and getting the discussion wrong.  I am always open to being wrong, even happy at times about it, when it means improvements come quicker than I expected. ... View more

Although I understand the value of having this functionality dynamic, and I don't think implementing a naive approach to it would be difficult, the fact that spatial operations are so compute intensive makes implementing an efficient means of doing it very challenging.  For the example given here, even a naive approach would likely perform fine, but what happens when there are millions of points or the polygon itself has tens of thousands of vertices?  In that case simply panning or zooming a basic map would result in the noticeable, if not significant, delay in refreshing the screen. Raising ideas is good, and I think the discussion around them in the community is good for Esri to read, but this is one where I would not hold my breath.  ... View more

Unfortunately, no, this is a major shortcoming of Esri's Named User licensing model.  My personal belief is that the shortcoming is purposeful, i.e., they could have addressed it by now if they wanted to address it.  So, organizations are left to come up with their own myriad of automations to address time-based Named User licensing. ... View more

More information would have to be shared before community members could provide anything beyond anecdote and links to general documentation.  For example, is this a hosted feature service or a referenced one?  If referenced, what is the back-end data store and what style of versioning is being used with the data?  Depending on the answers to these questions, there are even more questions. ... View more

Esri will fully retire ArcGIS Pro 3.1.x in 6 months (April, 2026).  If you upgrade to a recent version now, these questions/issues are moot. ... View more

Are the data sources stored locally on your computer or a shared network drive? ... View more

When asking about data management-related issues, it is helpful to state what the back-end data source is because whether something is a shape file vs file geodatabase vs enterprise geodatabase can make a difference. ... View more

What is the context?  Is this for labeling, visualization, analysis, etc...?  Knowing the context can open the door to context-specific options.  Regarding SQL, it is complicated because SQL support depends on the back-end data source, and the more advanced the SQL the less standard the support becomes.  That is, SQL isn't always very portable as a solution. ... View more

Although ArcPy Data Access (da) cursors are newer, and better in nearly every way, Esri continues to maintain the original cursors for backwards compatibility.  You should be able to run old code and even write new code using the old cursors, so are you encountering errors?  If so, what are the errors? ... View more

When you say "relies on," are you importing ogr2ogr.py or calling it as a command?  If the latter: C:\Program Files\ArcGIS\Pro\bin\Python\envs\arcgispro-py3\Library\bin\ogr2ogr.exe ... View more

Huh, interesting.  It may be a defect in the Copy Snippet functionality.  I am glad it is working for you now. ... View more

Why are you prepending "memory\" to the name of your layer?  That is likely confusing the Delete tool. ... View more

The inclusion of "memory" in the layer name makes me think the OP is trying to create something in an in-memory workspace.  Make Feature Layer always creates a temporary layer, and that layer is not stored in an in-memory workspace.  The Delete tool likely is looking in an in-memory workspace given the path passed, and since feature layers aren't stored in an in-memory workspace, nothing is there to delete. I think the tools are not being used correctly, which is causing confusion for them. ... View more

Lessons learned?  Since you didn't say where exactly you are deploying, e.g., on-prem or in a cloud, it is hard to provide specifics.  What I would say is make sure you really need high-availability before deploying it.  What I have seen numerous times are "high-availability" deployments that have multiple single points of failure so they are high availability in name but not in reality.  Doing truly highly available deployments comes with a non-trivial cost. ... View more

Start by looking at ArcGIS Maps SDK for JavaScript Life Cycle.  The oldest supported version is 4.24, which supports down to Safari 14, but that version of the SDK also is retired on 12/01/2025.  ArcGIS Maps SDK for JavaScript 4.27 was the last version to support Safari 15, and it doesn't retire until 11/01/2026, so that is probably your best bet for now. Although Apple sometimes backports critical security patches to unsupported versions of iOS, it isn't guaranteed, and Apple currently supports iOS 18 and newer.  Supporting unsupported software is one thing, doing new development on unsupported software is something else entirely.   ... View more