Latest Contributions by JeffThomasILM

‎11-08-2021

I found a workaround - a "cheat" - to do what I need: create a copy of the feature class, then overwrite the main case (field A) with the related case (field B), where the related case is not null. Then it's a simple, normal dissolve geoprocessing task on field A (and field C). While it's not quite how I intended to use my data and I've had to alter it a bit to accommodate this method, it works. But... I'm still interested to know how to find where Feature 1, Field A == Feature 2, Field B in the same feature class. Basically, joining a table to itself. I know SQL can do that, though I was envisioning (and have now avoided) a messy scenario.

‎11-05-2021

Thank you, that sounds like a step in the right direction. However, I'm far from figuring out how to do this. I'm not even sure how to write a query to match multiple features in the same FC where FieldA==FieldB. Here's what I'm trying to do. I have a bunch of features in a FC. Every feature has a case number (field A). Some of them also have a related case number (field B). I want to merge features that have related case numbers with their related cases (field B == field A, retaining the latter features' attributes). To make things more interesting, case numbers are not unique identifiers, so I also need the feature type (field C) to match on all features being merged (that's a straightforward field C == field C). There are more details, but I'm trying to boil this down as much as possible in the hopes that someone can point me in the right direction. Thanks!

‎11-04-2021

There will be dozens or hundreds of A==B feature pairs, so I need to create a tool that iterates over each feature in the feature class. Also, I don't think what you described would dissolve their geometries?

‎11-04-2021

I apologize if this question has been asked & answered before, but it's hard to search for the concept. I need to merge/dissolve features where the value in Field A for Feature 1 matches the value in Field B for Feature 2. Much like an attribute join, except they're all in the same feature class. I'd like the result to be a new feature class, leaving the original unchanged. I'm trying to figure out if this can be done with geoprocessing tools or if it will require a Python cursor. Thanks!

‎07-04-2021

The answer to my question appears to be, you cannot saveAs with ArcPy. So my follow up question is, why not? Will it be added in the future or is there some technical reason they don't want to?

‎06-30-2021

I understand I can use saveACopy, but that forces me to close my template (without saving!) and then open the new project to continue working. I'm trying to figure out if there's a better way.

‎06-30-2021

Is there a way to "save as" a project from ArcPy? I know there's "save" and "saveACopy" but not "saveAs". I'm trying to establish a workflow where I open a template project, customize it by running a script, then save it as a new project (and further customize it manually) without having to close the template and then open the copied project. I can "save as" manually, but not with ArcPy?

‎06-18-2021

I'm trying to create a custom pop up that includes attributes from multiple layers. Based on this example, it seems like FeatureSets should be the way to do this. The problem is this requires a geometry evaluation; e.g., return any features from layer B that intersect the feature I selected on layer A. This is overly complex; all I want returned are the features (if any) from layer A or B located exactly where I clicked - plain old popup behavior. I looked at all the geometry functions available but none of them seem to emulate a simple click. Is there a completely different way to accomplish this? Thanks!

‎06-15-2021

It would be great if rectangle (and polygon, circle, ellipse) layout text elements had fitting strategies like map labels. Legends already have some control for columns and text size. The idea is for all these elements to have additional fitting strategies like abbreviations and font width compression. This would help tremendously with ensuring layouts work for all pages of a map series with dynamic text of varying lengths. This idea would help with fitting text in a single element, but a closely related idea of mine would help prevent overlap or clipping between multiple layout elements in a layout used for map series: Intelligent grouping (flow) for layout elements

‎06-15-2021

Hi, @JeffBarrette. I was thinking about adding "rectangle text fitting strategy" as an idea, but it sounds like this is already on Esri's radar. Do you know when this might be available? It would be really cool if text fitting strategies for legends and other layout text boxes included options like abbreviations and font width compression (as is already possible for map labels). This is closely related to an idea I posted about a year ago that hasn't gotten much attention: Intelligent grouping (flow) for layout elements Thanks!

‎05-26-2021

I'm wondering what determines whether you can change version or refresh a data source in a map view. In one of my map views, I can refresh the data source of one SDE database connection but not another. Both databases are stored on the same SQL Server. I have read-only access to the one I can refresh, while I have write access (to FCs I own) to the database I can't refresh. I don't know if read/write access has anything to do with it, but if anything it seems backward of what I would expect. I can refresh both databases from the Catalog view, just not the map view. Regardless, I have to restart Pro to see changes made outside the project. This is related to another question I'm still working on: Joined table edits not showing on map. I'm wondering if not being able to refresh that database is related to the fact that I can't get edits to a joined table in the same db to show up in that map view until after restarting Pro.

‎05-17-2021

Can't have everything, I guess. Thanks for your help. Even if I still have to do some manual steps to output my maps, using the linked map frame extent is still superior to the way I was doing it before.

‎05-17-2021

I've played around with this a bit and it's close but not quite. In your example of states (my "A, B" features) and counties (my "1, 2" index features), you are not filtering to show just the subject state, which is what I need. Pro clearly knows what feature A is, because it's able to zoom to its extent based on index feature 1, but I can't get a page query to work on feature A. It either shows all of A, B (query off) or none of A, B (query on). I tried every combination of page queries on layer A, B between the two map frames. There are a couple other minor issues, but that's most because of my data. I would figure out how to work around that if could figure out how to make page queries work on features A, B. So close! Thank you for your help.

‎05-14-2021

Thanks for your quick reply, @AubriOtis. This looks very promising! I'll give it a shot and report back. It's great that this option would retain my project as a "real" map series that can be seen in Pro. Whereas the Python option (as I'm envisioning it) would mean the resulting map pages only exist as exported PDFs.

‎05-14-2021

I'm trying to create a map series where the extent of each map is based on features other than the series' index layer. E.g., index feature 1 is within feature A, and I need the map extent to cover the entirety of feature A. Index feature 2 is within feature B, etc. The problem is map series extent isn't designed for such a scenario. I'm trying to brainstorm a workaround. I could use features A, B... as the index layer, but then I'm not sure how I'd create a page query to get the corresponding feature 1, 2... There is not a 1-to-1 ratio of features A, B to 1, 2. Feature A might contain features 1, 2, 3, 4 and I need a map page for each feature 1, 2, 3, 4. Plus, there are dynamic text elements in the layout driven by features 1,2..., so that really wouldn't work. It's probably possible to do this with Python, but I'm not entirely sure how. I'm thinking it would be a For loop, looking for the index features (1, 2, 3) and an attribute of each feature would be used use to select the corresponding feature A, B, C. Could also use a spatial selection. Has anyone else attempted something similar? Would this even be handled like a map series in Python? I'm thinking probably not. Should this be an idea suggestion for a future version of map series in Pro? Thanks for reading my ramble!

Online Status	Offline
Date Last Visited	Wednesday

My Ideas

Latest Contributions by JeffThomasILM

Re: Merge/dissolve 2 features in same feature class where field A matches field B

Re: Merge/dissolve 2 features in same feature class where field A matches field B

Re: Merge/dissolve 2 features in same feature class where field A matches field B

Merge/dissolve 2 features in same feature class where field A matches field B

Re: Project SaveAs using ArcPy

Re: Project SaveAs using ArcPy

Project SaveAs using ArcPy

Create popup with attributes from multiple layers

Fitting strategies for layout text elements and legends

Re: Programmatically check if paragraph text fits in provided envelope?

Can't change version or refresh data source in map view

Re: Map series extent based on non-index features

Re: Map series extent based on non-index features

Re: Map series extent based on non-index features

Map series extent based on non-index features

Dynamic text for symbology labels

Re: Proper case for ordinals using Arcade

Editor tracking not preserved when using Paste Spe...

Re: Could not analyze datasets DatabaseName.DataOw...

Re: Interwoven layer drawing