Latest Contributions by PeteJordan

‎12-21-2021

@AyanPalit , thanks, and I know you have been able to view LRS measurs in the past, but my question is why I'm not able to simply select a line feature, and use any of these commands that are listed in Pro the same way as in ArcMap? Drop Measures - esri_editing_RouteSetAsDistanceContextMenuItem Set As Distance - esri_editing_RouteSetAsDistanceContextMenuItem Apply Factor - esri_editing_RouteApplyFactor_ContextMenuItem Currently it seems if I want to add measures to a route, I have to use the Make Route in the Modify pane, but this seems to create a duplicate record for the feature (minus some of the fields that don't transfer over) and I have one without any measures and a new one with measures which seems confusing, unless I'm missing something. If I want to edit the verticies on the line feature, the verticies start point is now a circle and not just a normal vertice. Dropping measures also doesn't seem to work in case you need to remove all measures from a feature in case you want to re-do it, etc. Maybe unless I'm missing it, maybe that I need to put into the ArcGIS Ideas then as it seems now this is a lot more work and more time consuming with more possibilities for errors...

‎12-21-2021

So, 2.9 has been released and has a number of LRS updates associated with it, but again, it seems it's still only under the Pipeline Referencing System. I know it was mentioned before that the LRS creation and modification was going to be implemented at some point as it was in ArcMap so we can create, modify and edit our LRS systems we have without having to pay for a separate license. Is this still the plan or has it now just been incorporated into a new cost? We are still having to use ArcMap for all LRS editing functions at this point and was hoping 2.9 would have introduced what ArcMap had in regardles to all LRS editing functionality (such as "drop Measures", "Set as Distance", "Apply Factor", "Identify Route Measure", etc)...

‎12-02-2021

Thanks Wendy for that workaround. I just feel I have a lot of scripts and taking the time doing this to every one of them might not be worth it. I think I'll just skip over 2.9 until this (and another bug I have that prevents me from using 2.9) are resolved...

‎11-23-2021

Good to know then it's not just me who has had issues. I can't even get my keybinds to save anymore and for editing in Pro, that's a nightmare without that ability. I might just way for the next 2.9 patch then and hopefully that fixes some things, but good to know it wasn't just me that's having 2.9 issues at all...

‎11-23-2021

Yeah I have no idea. I've always just copied the code and it's always worked until 2.9. As I rolled back to 2.8.3 due to other issues I've found in 2.9, the same code works as it should in 2.8. I don't get it at all. I had even copied the code directly from 2.9 and tested it in ArcMap and it worked there as well. So I have no idea other than some freak glitch with the 2.9 install or something?

‎11-22-2021

Hopefully they see it then, but at least I know it's a version issue then and one of 2 bug issues that is enough for me not to continue using 2.9...

‎11-22-2021

@JoeBorgione: Due to another unrelated bug that prevents me from properly working in 2.9, I actually did just that and uninstalled 2.9 and reinstalled 2.8 and the 3 service packs and now that I'm back in 2.8.3, the code works fine. So yes, it seems to be yet another bug I've found in 2.9. Bad thing is I'm unable to even submit a bug report due to the website having issues for the past few days (I did get ESRI support on the phone and they're looking into the issue now), but it will be another bug I'll have to remember to submit with 2.9 then...

‎11-22-2021

@DuncanHornby I tried your suggestion, but, no luck and I continue to get the same issue that it can't define the "FindLabel" name that I defined in the first line. Just seems really strange. Yeah I think it might take me way too long to learn Arcade, I'm not the quickest at learning languages at all...

‎11-22-2021

@JoeBorgione: Yes I was on 2.8.3 before and the label script has worked just fine in all previous Pro versions for the past year or more. In fact I used the script the week before without any issues.

‎11-22-2021

Before upgrading to 2.9, I never had an issue with my labeling code at all: def FindLabel([TrailName],[Width]): str_list = [] if [TrailName] not in (None, "<NULL>","<Null>", "", "0"): str_list.append([TrailName]) if [Width] not in (None, "<NULL>","<Null>", "", "0", " "): width_str = '<ITA>Width = {}\'</ITA>'.format("<ITA>" + [Width] + "</ITA>") str_list.append(width_str) label_str = '\n'.join(str_list) return(label_str) Now that I switched to 2.9, I'm now getting the following error: Invalid Expression Traceback (most recent call last): File "<expression", line 1, in <module> NameError: name 'FindLabel' is not defined I have pasted the exact same code into ArcMap 10.8.1 and it works just fine. So I'm very confused why all of a sudden a labeling script I've used for over a year now just fails in Pro? Any ideas?

‎11-17-2021

I upgraded to 2.9 and have noticed that it seems some of the names for tools and command seemed to have changed and it can be hard to find exactly what command you want to keybind. The big issue I'm having with 2.9 is that the keybinding (accelerator) for <ALT>-E which is one of my most used binds, no longer seems to save after I set it. It doesn't say I can't use that bind, it accepts it, if I click another command and then go back it's still there (see Arc 1.jpg), but when I press OK it removes it each time (see Arc 2.jpg). This was fine back in 2.8.x, so now I'm wondering how many other of my keybinds are no longer properly saving? It seems that a number of other keybinds I had set in place before 2.9 are not saving either (<CTRL>-A, <ALT>-T, etc) I have an exported ArcGIS Pro Customizations.proExportedUI.proExportedUI from 2.8.x that had all the binds that worked in it, and many now appear to no longer being imported or saving properly that I can send for testing if required (I can't upload it to here). Is this a bug (should this be in the bug forum?) or is there another reason behind this? (P.S. I would love for Pro to have a way to show what you have bound already to hotkeys so I know what has failed and not) Thanks

‎08-18-2021

UPDATE: I figured out the problem after re-visiting it today. It turns out the issue was caused by me switching over from DirectX to OpenGL in the Diplays under Options. Reverting back to DirectX solved the issue. I originally did this switch recently in order to see if that would improve editing performance in Pro. Issue resolved...

‎08-13-2021

Thanks Tom, I'll have to try and do that next week then. I did figure a work around and does seem that if I have one of the layouts open when I start Pro, it works fine. It's only when I close all layouts and reopen one or another one is when the issue happens. Strange, but at least for now it's a temporary solution. I also need to see if anyone else in the office is also experiencing this as well. Thanks for the link...

‎08-13-2021

I can't seem to find the Pro bug section, so will post it in here instead. Recently (not sure how long it's been actually happening as I haven't dealt with layouts for a few months), I've encountered an issue that I'm now seeing on every single Pro project I have layouts for. I always have been updating to the newest versions, but back in March at least, this was not an issue (can't recall the current version back then) and I've only discovered it this week, so it's hard to pinpoint exactly when this issue occured otherthan between March of 2021 and Aug 2021. The issue is I can open up any Pro Project that has layouts for the maps and all the guidelines are completely fine and in the correct spots on the ruler. However if I close that layout and open a new layout or even the same layout, a strange buffer happens at the top and all the guidelines no longer match to the correct rular points. If I close out of Pro and reopen, everything is good again until I open another layout, etc. Any idea why this is happening to every project I have now and/or how to fix this issue? Here are the image examples: Here's how it looks when first opened and is correct Here's how it looks when the layout is either closed and reopened or a new layout is opened showing the weird guidelines no longer matching to the ruler positions: Finally, here's the buffer that shows up only at the top, despite both the X & Y axis guidelines no longer matching up to the correct ruler values:

‎04-22-2021

Great thanks again Zach. I just have issues with the indentation a lot, so that's something I need to spend more time getting to know. I like that little tutorial you gave as well and will use that as a sample code for my own personal Python doc I'm making for myself so I can learn how things work better in Python. Thanks again

Online Status	Offline
Date Last Visited	‎03-12-2026 07:12 AM

My Ideas

Latest Contributions by PeteJordan

Re: Is there an 'Identify Route' tool?

Re: Is there an 'Identify Route' tool?

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

Re: ArcGIS Pro 2.9 - Python Script Failing for Labels

ArcGIS Pro 2.9 - Python Script Failing for Labels

ArcGIS Pro 2.9 - Bug with Accelerators (Keybinds)

Re: Layout Guidelines Bug 2.8.2 and Earlier Version

Re: Layout Guidelines Bug 2.8.2 and Earlier Version

Layout Guidelines Bug 2.8.2 and Earlier Version

Re: Label Expression via Python

Re: Imagery Issues with ArcGIS Pro 3.6

Re: Imagery Issues with ArcGIS Pro 3.6

Re: Imagery Issues with ArcGIS Pro 3.6

Re: Imagery Issues with ArcGIS Pro 3.6

Imagery Issues with ArcGIS Pro 3.6

Roads and Highways User Group (RHUG)