Latest Contributions by JeffJacobson

There is a discussion about this in a different thread with some alternative interfaces. My agency has an SOE that depends on these interfaces and opened a support case with Esri about it. They plan to reintroduce these interfaces in some future version at some undetermined point in time. ENH-000130183: "Add the ArcObjects Location library to the ArcGIS Enterprise SDK" Use Case One use case: the user has existing SOEs created for ArcMap. [It's actually the ArcGIS Server ArcObjects SDK, but they're referring to the fact that that these are map services that are published with ArcMap.] They would like to migrate to the Enterprise SDK to use them with Pro services. They use geometric networks and linear referencing to determine locations and relevant attribute information in the soe, so it will not be easy to migrate without this library. Specifically: IRouteLocator2, IRouteLocation, IRouteMeasurePointLocation, IRouteLocation, IRouteMeasureLineLocation, IEnumRouteIdentifyResult, and IRouteMeasurePointLocation. We are also investigating some non-Esri alternatives. NetTopologySuite - NetTopologySuite is .NET port of the Java library, JTS. We got this working but encountered an issue (not sure if its a bug or if we were somehow using it wrong) that prevented us from using it: if you specify a begin and end measure on a polyline, and those measures span two different lines within the polyline, the output segment should also be a polyline, but instead the gap between the lines is incorrectly connected. I do not know if JTS has the same issue. GDAL ogrlineref - The open-source GDAL is installed when ArcGIS software is installed. We haven't had time to do must investigating of this option. At the time we looked into ogrlineref, the Python implementation of GDAL didn't expose ogrlineref. PostGIS - PostgreSQL has built-in support for linear referencing via PostGIS. Migrating our LRS data from SQL Server to PostgreSQL / PostGIS would allow LRS functions to be carried out in database queries. We haven't tested this option at all, so we don't know if the LRS functions work the way we think they will. (I.e., it's possible we could encounter the same issue that we did with NetTopologySuite.) ... View more

@ReneRubalcava: I have created an improved type definition for $arcgis.import and put it on GitHub. It is Unlicensed, so anyone can use it and incorporate it into their own code without asking for permission. I used ChatGPT to help generate a script to dump a list of mappings, so developers using $arcgis.import no longer need to specify the type parameter. I haven't yet packaged it and put it in a repository (e.g., NPM), but I think users can directly add the GitHub repo as a package to their project. (I haven't tested this. If that doesn't work, they can just copy the d.ts file into their own project.) Edit I have since published it as an npm package: @wsdot/arcgis-core-helper I renamed the GitHub repo, so I have updated its link. ... View more

Yeah, Esri should really include the typing information. I have a GitHub repo containing arcpy typestubs, but they are not complete. I used pyright to generate typestub files as a starting point, then have been cleaning them up gradually as I actually use the various classes, functions, etc.. ... View more

Thanks, but what I was asking is if there was a simple "Reset to defaults" REST endpoint or button in Manager or something of that nature. (I already am aware of how to look up what the defaults were and change them.) On our production ArcGIS Server, I can't make these changes myself and have to instruct someone else on what I want them to do. I was hoping there was a simple "reset" command I could point them to that I was not seeing in the documentation. ... View more

I encountered this recently and opened a support issue. They told me it's a known bug. (They've not yet given me an ETA on a patch or fix yet.)  #BUG-000146430 This is a really serious issue, as it prevents you from publishing GP services or sharing in a GP package from tools in an atbx. You're not allowed to publish tools without metadata, and you can't add metadata to the tools. This is how I found out about the bug. Luckily the logic of the tools were in Python scripts, so recreating the toolbox portion in the legacy format wasn't too difficult. I'd hate to be the person that had to recreate all their model builder models because of this bug. ... View more

.NET 5 (the next major version of .NET Core) is scheduled to be released in 2020, and will supersede the .NET Framework. Targeting .NET Standard going forward would be a good idea so you will be ready by then. ... View more

After upgrading to ArcGIS Pro 2.0, I am no longer having this issue. Perhaps there was a bug in earlier versions, but I don't know for sure. ... View more

You're not assigning the URL to the esriConfig.portalUrl. You're currently creating an unrelated variable called portalUrl and assigning a value to it, while esriConfig.portalUrl remains unchanged. ... View more

The ArcGIS JavaScript API only runs on the client-side (i.e., in the browser), so it shouldn't matter what technology you use on the server-side. ... View more

Have you tried using arcpy.da.UpdateCursor rather than the Calculate Field tool? That's how I would accomplish this task. ... View more

I happened to be looking at the Bower site today and noticed this message: ...psst! While Bower is maintained, we recommend yarn and webpack for new front-end projects! Also their latest blog entry (from last Oct.) is about using yarn instead of the Bower API. ... View more