Latest Contributions by PeteJordan

 @RhettZufelt , I did run into an issue though.  As I mentioned before, the WIDTH can actually be a string in some cases or numeric in other cases.   So right now this code works if the WIDTH is a String, but it fails if it's numeric and WIDTH=0.  So I've tried to add in just a 0 into the code, but it doesn't seem to ignore that.  I've also tried to use the None as well without success. (Note I had to change the name of the Width_1 to WDTH_TMP to make it easier.   Here's what I'm trying without success if the value is 0 and WIDTH is actually a numeric field.     if str(WDTH_TMP).strip() not in (None,"<NULL>","<Null>","0",0):         ... View more

  Thanks so much, and I actually used the code block in the past and just forgot how to use it, so thanks for that refresher for my future questions on the forum.   I liked how you explained everything and that made it much easier to understand why you changed what you did.  Now I can update my document with this and make it a lot more inclusive to the types of naming conventions we get.   With the Width, yes we can get just numeric values or such things like "8FT" or "Varies", so I always have to treat that as a text field (I forgot to include the "varies" back into the code, but that's an easy fix).   Thanks so much for this help... ... View more

Ok I got the Name part working with the & which is great and thank you for that. In the larger code (which is different than the example I showed you),  I am trying to apply that to 2 fields out of 4.  In this example NAME and ALT_NAME. I run into issues when trying to do it for a 2nd field.  Here's the code that I can't seem to get working.  One issue is that you stated the <ITA> and such may not be supported in this fashion, 2nd I can't get this code to work at all regardless of where I place the ALT_NAME1  if statements for the &: def FindLabel([NAME],[ALT_NAME],[ROUTE],[WIDTH]): str_list = [] NAME1=[NAME] ALT_NAME1=[ALT_NAME] ROUTE1=[ROUTE] WIDTH1=[WIDTH] if '&' in NAME1: NAME1=NAME1.replace("&","&amp;") if NAME1 not in (None, "<NULL>","<Null>", "", "0"): str_list.append(NAME1) if '&' in ALT_NAME1: ALT_NAME1=ALT_NAME1.replace("&","&amp;") if ALT_NAME1 not in (None,"<NULL>", "", "0"): altname_str = "<ITA><FNT size = '6'>({})</FNT></ITA>".format(str([ALT_NAME])) str_list.append(altname_str) if ROUTE1 not in (None,"<NULL>", "", "0"): route_str = "RT#: {}".format([ROUTE]) str_list.append(route_str) if WIDTH1 not in (None, "<NULL>","<Null>", "", "0", " "): width_str = "<ITA>Width = {}'</ITA>".format(str([WIDTH])) str_list.append(width_str) label_str = '\n'.join(str_list) return(label_str) ... View more

So that at least shortened the script a bit by removing like you said the extra itallics from the WIDTH part, but I still have the same issue with the NAME and using & in the name as in my last screen shot... ... View more

  Well first off, the WIDTH is not always a numeric field, it can sometimes be a text field depending on who gives us the data.  This is also one of the simple labeling functions I do, there could be a number of other fields that also get displayed.  I just used these two NAME and WIDTH as an easy example.   The code you suggested returned an error:   Here's an example of what I am experiencing This is how my names should look and in this case I substituted the '&' with'and'.  It also has the width field shown as well in itallics.   Example 2 (amp_ex2.jpg) shows what I am getting if I use the '&' instead...    ... View more

Just what's shown in the code above.  The actual fied is a text field though in the dataset...   ... View more

If you used the Attribute Editor and click on the selected part (in the red box in the lower right) it should have shown the selected features when using the Statistics on your field.  It will bring up the Char Properties pane and then you can see the Selection listed there beside the entire dataset.  This is of course if you were doing it this way and not the data engineering method as it looked like you originally did since you had the distribution chart showing (which I don't use or need either)...     ... View more

I am suggesting the Goto XY (esri_mapping_gotoXYControl) to allow a single entry of both the Lat/Long rather than forced to using it as it currently is as two separate boxes.     I find it frustrating when using the Copy Location (esri_mapping_copyCoordinates) from one map and want to find that location on another, I have to paste the full Lat/Long in the Long box, then cut out the Lat and re-paste that in the Lat box. It would be easier to have the option to paste the entire coordintate into the a Lat/Long box option (similar as to how Google allows pasting of both and it will jump to the location) as well as have it separated as it currently has to deal with both types of coordinates to paste in.   It would also be helpful to allow the Long box and Lat box to also be expanded to paste in longer coordinates as well.    ... View more

@JeffBaker2:  That acutally seemed to work for me right now and a good workaround... ... View more

They have changed how this works yet again.  Seems every update they move things around or change the way things behave and this is just another one that has changed.  I made an ArcGIS Pro document for myself to guide me thought it all and I'm always having to revise it and rewrite things.  It's kind of annoying... ... View more

@Scott_Harris I just tried this (in my example having <CTRL-R> assinged to Reshapeand <ALT-R> for Trace, using your suggestion and I am getting the same result that the trace still now selectes the editing polygon and not the one I want to trace to.   However, if I instead just press <SHIFT> and release and then <CTRL> and release it then selects the correct tracing feature...   ... View more

@Scott_Harris :  This issue I just found out is still a problem with using the <CTRL> for accelerators (my case <CTRL-R> for Reshape in ArcGIS Pro 3.0.3... ... View more

Hey @Scott_Harris,   Ahhh, got me again with my extensive use of mutiple accelerators and guess what?  My Reshape (esri_editing_ReshapeCommand) is set to <CTRL-R>, Trace (esri_editing_ReshapeCommand) set to <Alt-R> and this is the problem.   Tried it without using my accelerators and yes, it now works and I don't have to close down ArcGIS Pro each time I want to do a trace polygon at all.   So I assume this is on the bug list correct for a future fix when those accelerators all get that possible overhaul in an upcoming version then?   I'm glad @m3 already had this asked as I was about to fill out another bug report (until I saw this thread) and his video is much better than my images... ... View more

@Scott_Harris Thanks for that, I thought we were missing something... ... View more