Latest Contributions by DavidSolari

‎09-28-2023

Clone the toolbox, export the relevant embedded scripts to Python files, rewrite the scripts so the critical paths are functions you can call with standard Python data as parameters, then throw your profiler at that. E.g., if you have a script like: import arcpy table = arcpy.GetParameterAsText(0) output = arcpy.GetParameterAsText(1) table_data = get_table_data(table) new_data = transform_data(table_data) write_data(new_data, output) Export that script and change it to something like: import arcpy from scalene import scalene_profiler def main(table, output): table_data = get_table_data(table) new_data = transform_data(table_data) write_data(new_data, output) if __name__ == "__main__": scalene_profiler.start() main("/path/to/input", "/path/to/output") scalene_profiler.stop() And so on. The more complex your process is, the more functions you'll need to factor out so you can find the true critical path. You might also need to tweak your functions to read and write preformatted data from memory that you prepare before the profiler engages, that way you eliminate I/O operations from the benchmark as much as possible; this makes finding slow computations easier. Note that for most arcpy code, the true bottleneck is the synchronous I/O functions that arcpy provides so don't be surprised if your code runs several orders of magnitude faster with the I/O stubbed out. Happy hunting!

‎09-08-2023

For future travellers, here's the unfathomably hacky workaround I figured out: Copy and paste the map to a "label map". Remove all layers in the label map save for the label layer. Ensure the map has a transparent background. Remove the label layer from the original map. Return to the layout and copy-paste the original map's frame to a "label map frame". Copy and paste the extent from the original map frame to the label map frame. Align the label map frame to the original map frame. Ensure the label map frame has no background, borders etc. set at the frame level Order the label map frame over the layout graphics. Et voila! Labels on top of graphics on top of maps! Just make sure you have the rest of the layout 100% locked in before you do this, even with feature-linked annotations this adds a lot of work to each iteration.

‎09-08-2023

Thanks Tom, that first paragraph lines up with what I found through experimentation. I'm confused by the wording in the second paragraph, are you saying there's a way to sandwich layout graphics in-between map layers? That seems like a contradiction, maybe I'm reading it wrong.

‎09-08-2023

I need map labels to draw over a number of layout elements. I've converted my map's labels to a graphics layer, how do I convert that into layout graphics? Alternatively, can I force the map's graphics to draw over the layout's graphics?

‎09-07-2023

If a Feature Service is published with the symbology set via an Arcade expression, the feature class's subtype info is not carried into the service definition. This means subtyped data has to be published with simple symbology classes which isn't ideal for displaying all types of data. I assume this has to do with an ancient limitation of the Server platform where subtypes and symbol classes have to be tethered somehow, either way this restriction should be lifted to support more expressive symbols in web GIS workflows. (Apologies if there's a better hub for this idea, figure the same fix should work for both portal types)

‎08-24-2023

I created a polygon FC in Web Mercator, then created a 2m radius using the method described around 49N. The resulting circle had a planar diameter of 4m but a geodesic diameter of 2.62m for an error of 1.53x. This seems like the most likely culprit of your error.

‎08-24-2023

This could be an issue with the chosen coordinate system of the data and/or map but we'll need more information. What tool is used to create the circles? How are they entering the desired radius?

‎08-22-2023

Note that this will add new fields to the shapefile. If you have existing fields ready to go, try Add Join followed by Calculate Field (one field at once) or Calculate Fields (many fields at once, trickier to use).

‎08-22-2023

Are you in Pro or one of the web-based platforms? Pro maps have a coordinate system you can set yourself, it defaults to whatever your first layer or basemap uses. You'll have to keep track of what datum transformations are in play but otherwise it'll try and sort itself out. Web maps and anything derived from them (EXB, Field Maps etc.) pin the coordinate system to the basemap. This means if you don't want datum transformations, you'll have to ensure the basemap was published with the same GCS (and PCS ideally for performance reasons) as your layers. The standard ESRI basemaps are Web Mercator only so you'll have to source, process, host and serve your own basemaps if you want to go down this route. Alternatively, you'll need to store your layers as Web Mercator before you publish them out, then post-process the data to a projected and transformed copy before you run proper analysis and cartography.

‎08-15-2023

What do your tool parameters look like when you defined the tool in Pro? Your script has 2 inputs and 1 output, these same inputs and outputs must be defined in the tool's structure. The docs can explain this better than I can: link. In your case I think you can eliminate both inputs as everything is hardcoded into the script, or you can turn some of the inputs into parameters to make your tool more flexible, up to you. The output parameter will have to be a Derived Output as you're creating the feature class wholly within the script, if this causes issues you can let the user pick the output FC as a Required Output parameter instead.

‎08-15-2023

If you add a script tool to a model it should show up as a rectangle, just like the normal tools. Your screenshot is highlighting a variable, try dragging the script tool from the catalog into the ModelBuilder canvas and see if that gives you a more sensible item to work with.

‎08-11-2023

Here's one script structure you can use: from __future__ import annotations import arcpy def main(param1: int, param2: str): return str(param1) + " " + param2 def execute(params: list[Parameter], messages = None): param1 = params[0].value param2 = params[1].valueAsText params[2].value = main(param1, param2) if __name__ == "__main__": execute(arcpy.GetParameterInfo()) This structure puts all the main program logic inside a "main" function that accepts standard Python types. If you run this through a standard toolbox (or bridge the call to execute from a Python toolbox) you extract the parameter values, pass them into "main" and set a derived parameter using the return value. However, you can import "main" from this file into a test file and call it with premade parameters and test the results. This makes it easier* to write unit tests for your script tools as well as launching the tool from outside of ArcGIS Pro which enables proper debugging. That said, you'll still need to AddMessage debug your parameter object related code if you don't have Visual Studio 2019 on hand. *The actual hard part with writing script tool tests is wrangling the GIS data and making meaningful comparisons against "good" data but that's a story for another day

‎08-11-2023

Editing the "x" files directly is possible but very fragile, there's nothing stopping ESRI from redefining how these files are laid out and breaking your code. The preferred method is to go through the CIM Interfaces as they have explicit versions that are guaranteed to remain stable across Pro versions. Note that CIM editing is very different from your usual arcpy workflows, you have to work with the various types as they're defined and instantiate new instances using the provided factory functions.

‎08-11-2023

I strongly suggest learning how Python classes are written, the official docs are a good reference and there are many tutorials online that can walk you through creating your first class. That said, there's nothing stopping you from defining functions within another function or method and then calling them. The catch is functions are bound to the scope they're defined in, which means you can't call an inner function outside of the method/function/etc. it's defined within. The most likely reason your first example is failing is because you defined a method with no "self" parameter or no "@staticmethod" decorator, which makes it useless. Instance methods need self as the first parameter, decorated static methods do not.

‎08-02-2023

In general, nothing in arcpy is designed to run in a threaded context. You might be able to hack something together using the multiprocessing library but in general, no GP tool can execute until the current one is finished. If you want a dedicated window for your tool you'll need to dive into the full Pro SDK and write some .NET.

Online Status	Offline
Date Last Visited	Thursday

My Ideas

Latest Contributions by DavidSolari

Re: Has anyone used a python profiler on python code in an atbx?

Re: How Do I Move Graphics from a Map to a Layout?

Re: How Do I Move Graphics from a Map to a Layout?

How Do I Move Graphics from a Map to a Layout?

Support Subtyped Features with Arcade Symbols

Re: Issues with ArcGIS Pro scaling while creating radius

Re: Issues with ArcGIS Pro scaling while creating radius

Re: Add data from Excel sheet to attribute table based on same name

Re: Correcting Data Projection Issue in ESRI Offline Base Map

Re: Using output from script tool as input to common tools

Re: Using output from script tool as input to common tools

Re: Debugging a python script running in a toolbox

Re: Creating/Editing Feature Templates via arcpy?

Re: python-toolbox: is it possible to define a function wihtin init or execute?

Re: Python tool - how to run in background - or how to run multiple geoprocessing tools simulataneously?

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