Latest Contributions by DavidSolari

‎10-27-2023

Oh wow, I had no idea ESRI was uploading the arcpy package to Anaconda, this makes things much easier. Thank you!

‎10-26-2023

parent_key = "GlobalID" child_key = "ParentID" parent_fields = [parent_key, "fields", "to", "copy"] child_fields = [child_key, "into", "the", "child"] # Start an edit session if needed with arcpy.da.UpdateCursor("parent_table", parent_fields) as update, arcpy.da.InsertCursor("child_table", child_fields) as insert: for row in update: insert.insertRow(row) update.updateRow([row[0]] + [None] * (len(row) - 1)) # Close the edit session if needed Untested, but this should simultaneously create related records with the relevant fields while nulling out the old data to avoid confusion.

‎10-26-2023

Is there a list of which Python version (e.g. 3.7, 3.9 etc.) is included with each version of Pro? My team has had to keep an old version of Pro around to maintain version compatibility with our Enterprise Python environment and a table like this would've saved a few hours of trial and error installing different versions. This table already exists for Enterprise so I'm not sure why I can't find the same resource for Pro.

‎10-26-2023

I'm not sure where this ms level noise is coming from (especially with strptime) but this StackOverflow answer looks like a valid solution when combined with a good old Field Calculation run.

‎10-26-2023

Here's a (untested) Field Calculator code block: def reclass(value): lookup = { "Coniferous": "Tree", "Deciduous": "Tree", "Igneous": "Rock" } return lookup.get(value, value) You write something like "reclass(!my_field!)" and it'll map the inputs to the outputs as defined in the "lookup" dictionary, but leave them unchanged if it's not in the list. Alternatively, you can load the old and new values into a table, join the tables on the common key field, then field calculate over the data. This'll let you maintain a lookup table as standard ArcGIS data instead of Python code if that works better.

‎10-24-2023

When Power Automate is connected to Survey 123 using this method for Enterprise the only surveys available are those owned by the account embedded in the workflow. I propose expanding this to any survey shared with the embedded account so they can run workflows for surveys other organization members own. Our team needs to grant access to an external user solely for working with existing surveys, which is impossible to control if the embedded user also owns the survey. Expanding what the workflow can access without changing the user's scope would fix this issue.

‎10-24-2023

To keep things simple: we can't give the Power Automate users the ability to alter the surveys in any way, their only ability should be to pull completed surveys through the webhook. Unless there's a way to get that working I'll have to take this to the Idea Zone. Thanks for the clarification.

‎10-23-2023

For context: we're hosting all of our data in our Enterprise (10.9.1) and using Survey123 thorough the usual website with our portal URL glued on. We've tried to use webhook with Power Automate using the documented method and everything seems to work well, but only if the registered user owns every single survey. This is untenable for us as the team feeding off the webhooks is separate from the team managing the surveys, which means they need a separate account. My question is: is there a way for Power Automate to pull every survey that's shared to the registered user, not just the ones it owns? We might be able to hack around things by hosting a custom swagger file but I'm not even sure if processing surveys that are just shared to a user is allowed. More info on what we can do here is greatly appreciated!

‎10-20-2023

Untested, but this should get you in the ballpark: # Get this polyline object somehow, cursors with the "SHAPE@" token work well line = get_line() sr = line.spatialReference start = arcpy.PointGeometry(line.firstPoint, spatial_reference=sr) end = arcpy.PointGeometry(line.lastPoint, spatial_reference=sr) angle, distance = start.angleAndDistanceTo(end, "GEODESIC") Peep the "angleAndDistanceTo" part of the PointGeometry docs for more info.

‎10-19-2023

I noticed this in the new parameter controls document: To support a parameter that accepts a multiline block of text, use a controlCLSID value of {E5456E51-0C41-4797-9EE4-5269820C6F0E}. Does this mean text boxes that pass multiline string data are implemented in 3.1? I don't have 3.1 to test but at a glance it seems like this was silently implemented. If so this is an easy "Already Implemented" idea for whichever community manager stumbles across this, wink wink.

‎10-18-2023

The multiprocessing module has a lot of caveats due to how Pro manages its Python environment. This link has a lot advice and some sample scripts, this might be enough to get you started.

‎10-13-2023

Currently we have one big git repo that holds all the scripts and supporting files, a copy of which is cloned to our shared network drive and referenced by toolboxes on said drive. Clunky, but it hasn't collapsed so far. Our next move is to switch to geoprocessing modules which have a dependency on a "master" package, that way we don't have to implement common utilities over every project. This has its own set of challenges (teaching users how to manage environments, potential dependency conflicts, keeping the Servers in sync for web tools etc.) but it's a bit easier to manage than one fat folder full of junk.

‎10-13-2023

Based solely on the quoted passage, I'd assume each path segment in the network has a fixed impedance that can vary per segment. If you want to confirm this, run several routes with various types of paths (e.g. only highway, then only local roads, then local to highway to local etc.) and graph the travel times vs distance for each route. If every route has the same impedance then you'll get a linear correlation between distance and time, if not then you won't.

‎10-10-2023

The publishing process is rewriting your script to adjust embedded paths but the heuristic is terrible and it'll often break your scripts. The workaround is to edit the server's copy, adjust your tool to avoid referencing external files that aren't standard ArcGIS resources, or copy those external files to the server directories.

‎10-10-2023

Not a C++ guy, but a quick search brought up std::stoi if you're on C++ 11 and up and you're using exceptions in your codebase. If neither applies to you, this post covers a few options and shows an implementation using a standard C function. This all assumes you're using standard C strings, other strings will need a conversion or a custom implementation.

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by DavidSolari

Re: Table of Python Versions for Each Pro Release?

Re: Is there an easy way to populate a new related table with data that is currently stored as an attribute of another feature class?

Table of Python Versions for Each Pro Release?

Re: String to Datetime with Python in ArcGIS Pro

Re: Merging 10 vector polygon classes into 5 classes

Webhooks & Power Automate: Allow Enterprise Workflow to See All Shared Surveys

Re: Webhooks & Enterprise: Accessing Surveys Shared With User

Webhooks & Enterprise: Accessing Surveys Shared With User

Re: Obtain bearing of a geodesic line using arcpy

Re: Text box parameter for script tools

Re: Python multiprocessing module in toolbox

Re: Reusing python scripts and modules across projects

Re: "Fixed Speeds" for countries using Network Analysis

Re: Publishing a Model from Pro to Server - g_ESRI_variable_1 issue

Re: C++ String to Integer Conversion

Re: Are changes to ArcPy scripts needed when acces...

Re: Update feature geometry?

Re: Arcade: Get Measure from Coordinate?

Re: Why Must Survey 123 Folders Change When Changi...

Re: Creating a dynamic field?

Experience Builder Custom Widgets