Latest Contributions by JeffThomasILM

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! ... View more

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. ... View more

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. ... View more

Thanks for your quick reply, @AubriKinghorn. 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. ... View more

I did not realize until just now that those 2 options existed! I was using the Table Attribute Value, but for my situation the Map Series Attribute is exactly what I need. Learn something new every day! Thanks! ... View more

Ah! MS vs. Layout also explains why the code complete wasn't working. You were of course right about removing the single quotes from the field name. I thought they were required if using a file GDB, but apparently not. A lot of trial and error went into formatting the SQL statement properly for Python, and that was what I finally arrived at that didn't create an error. However, it also didn't create a selection! Thanks again! ... View more

I'm trying to actually implement the knowledge this morning I got from this thread yesterday. I'm getting an error when I try to run my script. I can't figure out what I've done wrong.   import arcpy, os, sys aprx = arcpy.mp.ArcGISProject('CURRENT') HPCcase = aprx.listLayouts('HPC Case Layout')[0] ms = HPCcase.mapSeries if ms.enabled: ms = HPCcase.mapSeries indexLyr = ms.indexLayer PDFpath = 'V:\\projects\\DevSvcs\\Planning\\HistoricDistrict\\HPC\\' HPCdate = '20210513' arcpy.management.SelectLayerByAttribute(in_layer_or_view=indexLyr, selection_type="NEW_SELECTION", where_clause=f"'HPCDate'='2021-05-13'") pageName = ms.pageRow.ConcatAddr HPCcase.exportToPDF(out_pdf=os.path.join(PDFpath, HPCdate, f"HPC_{HPCdate}_{pageName}.pdf"), page_range_type="SELECTED", multiple_files="PDF_MULTIPLE_FILES_PAGE_NAME", resolution=300) Traceback (most recent call last): File "<string>", line 19, in <module> File "C:\Program Files\ArcGIS\Pro\Resources\ArcPy\arcpy\utils.py", line 191, in fn_ return fn(*args, **kw) TypeError: exportToPDF() got an unexpected keyword argument 'page_range_type'   In addition to the export error, I'm pretty sure nothing is getting selected in my index layer. Since a date is the selecting criterion, it's an additional syntax hurdle to make sure I'm doing it exactly right. When I create the features, I only care about the date, not the time. (Time should always be 00:00:00, but I'd rather it not be a factor just in case.)  Also, I want to make sure I understand how the selected page range works for exporting in Python. Does it only work by selecting index features also in Python? Is it possible to select one or more pages manually in the Contents pane, then export with Python without further specifying a selection? Thanks! ... View more

Thank you, @JeffBarrette and @DanPatterson. I'm realizing a few good nuggets of information from your responses. What I called a loop in my o.p. is not a loop; it's a conditional. You don't have to specify every single parameter for the method (but you can, as long as you follow the specified order); you just need to specify the name of the parameter(s) you want. Booleans are like integers, no quotes. A few outstanding questions: Why are the page_range parameters not included in the full, non-named parameter array for the method? Are there other (hidden) parameters? Is it common to have additional parameters that can only be called by name? Thanks! ... View more

Unfortunately, the bus routes would need to geometrically match the streets exactly. There may be some ways to get them to align, but in the end it's probably no quicker or easier than doing it manually, sorry! I'm still not entirely sure what you're trying to do. Assign street names to bus routes? So that only those street names are labeled? One last idea. You did mention you envision "clipping" the street data. You might be able to do that. Create as thin of a buffer on your bus routes as you can to get the traversed streets in their entirety. Clip the streets and export them as a new feature class. This will still include very short segments of cross streets, but you can set a minimum feature length for labeling, which hopefully would result in a pretty clean selection of streets that actually have bus routes. ... View more