Latest Contributions by KateNewell1

I guess another workaround would be to use the "Sort" tool in Data Management.  Seems like more work and a new table creation than should be necessary but could work. ... View more

That is a good idea! I tried it but when I sorted and then hid the field, it reverted back to the old sorting.  I have alpha-numeric data I am sorting on. I created a new field that is numeric to sort the table/legend but don't want to display the numeric information (SA_NUM needs to be used to sort but not shown on layout. See below: ... View more

Here are the errors from the Developer Tools/Console for both Chrome (which works but still shows errors) and IE, where the map doesn't render... Chrome: IE: ... View more

Thank you so much Thomas and Kory.  I appreciate the time and effort.  Enjoy your weekend. ... View more

UPDATE: As part of the huge python script the this featureclass is a part of, at the end of the script I added code to delete the parcel copy and re-copy it into the file geodatabase, then compact the database.  This has fixed the issue.  Still not clear where or why it is getting corrupt in the script, as really there is very little other than the copy and field calcs being done to that feature class...but somehow it is gets messed up.  There were no errors when I ran fix geometry, so not exactly sure.  I'm guessing your theory on "...it appears that Pro has higher data quality standards than ArcMap" is playing into this as the issue never arose in ArcMap. ... View more

blank schema: https://www.iqmap.org/resources/images/pcd/PARCELJOINISSUES.XML The join is between PARCEL_CODE and SITE_APN I also have a new workstation and install of ArcGIS Pro, so this could be playing into this as well...some strange new setting? I appreciate you looking into it.  I'm also ready to throw in the towel and work in ArcMap as deadlines approach. Thanks! -Kate ... View more

The file geodatabase was created manually in ArcCatalog (Desktop).  The feature class that is problematic is created through a python script as part of a huge process that aims to show achieved density vs zoned density.  The only part of the python script that involves this layer (copy of parcel layer) is where I copy it from SDE and place it into the file geodatabase and strip/replace some values in the address field (since our assessor address field is messy).  Beyond that it is used in joins in the script only to attribute other featureclasses and is not actually altered. Here is the portion of the script that creates the copy...super straightforward but obviously PRO doesn't like it. import arcpy, sys, string, os, time, datetime, shutil, traceback, math arcpy.env.overwriteOutput = True arcpy.env.workspace = r"N:\Users\ke\BuildableLands\BuildableLands_WorkingData.gdb" #Variables D_TaxParcelPolys_Original = r"N:\ArcGIS\Connections\Speedsong_sdepub.sde\sdepub.COBGIS.D_TaxParcelPolys" D_TaxParcelPolys = r"N:\Users\ke\BuildableLands\BuildableLands_WorkingData.gdb\CurrentParcelCopy" arcpy.MakeFeatureLayer_management(D_TaxParcelPolys_Original, "copyparcel", "Feature_Source = 'COB'") arcpy.CopyFeatures_management("copyparcel", "CurrentParcelCopy") arcpy.CalculateField_management(D_TaxParcelPolys, "Site_Address", '!Site_Address!.replace(" "," ")', "PYTHON", "#") arcpy.CalculateField_management(D_TaxParcelPolys, "Site_Address", '!Site_Address!.strip()', "PYTHON", "#") In order to share my data, I probably need to strip everything out of the parcel featureclass other than the parcel number, as I'm not sure our county would want us sharing that publicly.  I'll try to do that and attach. ... View more

Yes the original data from SDE works but is so painfully slow that querying the feature class or table with the join on it is almost impossible.  It takes almost a minute to open the table and trying to symbolize the data is unbearable.  I'm trying to symbolize with Graduated Symbols and get the spinny-thing for about 45 seconds before the symbology window is functional on the joined SDE layer.  That is originally why I created the copy of the SDE parcel data in a file geodatabase.  Obviously something corrupt or wrong with my copy though....but I can't get over that it works in ArcMap! I also wanted to create a report on this information...and I see now that reports are not part of PRO yet.  So, back to ArcMap it is   I'm trying to like PRO, really I am ... View more

Yes it is very specific to this feature class.  I have tried a join with "Keep Common" on other datasets and it works fine in PRO. I tried a copy of this dataset and still have the issue ONLY when I try to "Keep Common".  If I Keep All Target Features for this dataset, then it is fine.  I have no doubt its somthing funky with my feature class, but its really weird because the exact same process with exact same feature class/table works fine in ArcMap with "Keep Common". I have rebuilt spatial indexes and the map is using the same coordinate system as feature class.  Its definitely specific to this feature class.   Thanks for all the ideas and troubleshooting...gotta move forward on this project so I will just join it up to the original parcel feature class from SDE and take the performance hit or "Keep All Target Features" and query out the ones that didn't join. ... View more

Ya, I agree it's acting like multi-part, but it's not multipart. Unique parcels/shapes.  If I "Keep All Target Features" it works in ArcGIS Pro (other than being painfully slow, almost a full minute to open the table).  So I guess I could do that and then just use a definition query to get rid of seeing all the ones that didn't join. FYI, the exact same process, data, join, etc...works perfectly in ArcMap 10.5.1 and is not slow at all.  I can "keep common" and select/pan/zoom through the table with no problem.   Thanks for all the help suggestions! ... View more

I just updated to 2.2.1 and the issue is still persisting. ... View more