Latest Contributions by Paul_Christensen

Amir, I have tried adding the fabric to a new map, and the default popup expression still gives me troubles. As far as I can tell, the default custom display expression (Layer Properties > Display >  Display Field > Set an Expression) uses an identical expression to the popup and the Attributes panel shows the correct format. Your popups display correctly? Hmm. Could it be a setting or system configuration for me?  I was able to construct a new expression using the new ConvertDirection function, however, it still excludes the single quote. You can see the default fabric expression followed by the ConvertDirection expression. Thank you for looking at this with me! -Paul Here is the full default fabric popup expression.   // Change the settings portion to configure direction format, rounding and abbreviations // This is an Arcade expression // SETTINGS var QuadrantBearingFormat = true; //set 'true' for quadrant bearing, 'false' for north azimuth var ShowDistance = true; //set as 'true' to show distance var ShowDirection = true; //set as 'true' to show direction var ShowRadius = true; //set as 'true' to show radius var ShowCurveParemater = true; //set as 'true' to show a curve parameter var CurveParameter = "ArcLength"; //set as 'ArcLength' or 'Chord' or 'Angle' for central angle. Case sensitive! var ErrorString = "COGO ERROR"; //set to display invalid COGO combinations var RadiusAbbr = 'R='; //radius abbreviation var Radius2Abbr = 'R2='; //radius2 abbreviation for spiral curves var ArclengthAbrr = 'L='; //arclength abbreviation var ChordAbbr = 'C='; //chord abbreviation var AngleAbbr = 'A='; //central Angle abbreviation var DistUnitRounding = 2; //number of decimal places for distance units: distance, radius, arclength & chord var NumberFormat = "#,###.00" //number format. In this example: thousands separator with padding of 2 zeros // VARIABLES var direction=$feature.Direction; var distance=$feature.Distance; var radius=$feature.Radius; var arclength=$feature.Arclength; var radius2=$feature.Radius2 var prefix; // quadrant bearing prefix var postfix; // quadrant bearing postfix var bearing; var quadbearing; var binaryDictionary; //binary dictionary to check COGO combinations var checksum=0; //initialize checksum var validValuesArray; //array of valid values for COGO combinations var partialValuesArray; //array of partial values for COGO var degrees; var minutes; var seconds; var DMS; var directionStr = ""; //direction string using for label var distanceStr = ""; //distance string using for label var radiusStr = ""; //radius string using for label var radius2Str = ""; //radius2 string using for labeling spiral curves var curveStr = ""; //curve parameter string using for label var angleRad; //curve angle in radians var COGOValidity; //COGO combinations validity. can be valid, partial or invalid. function NorthAzimuth2Quadbearing(azimuth){ if (azimuth<90 && azimuth>=0){ bearing=azimuth; prefix = "N"; postfix= "E";} else if (azimuth<180 && azimuth>=90){ bearing=180-azimuth; prefix = "S"; postfix= "E";} else if (azimuth<270 && azimuth>=180){ bearing=abs(180-azimuth); prefix = "S"; postfix= "W";} else if (azimuth<360 && azimuth>=270){ bearing=360-azimuth; prefix = "N"; postfix= "W";} degrees=floor(bearing); minutes=floor((bearing-degrees)*60) seconds=((bearing-degrees-minutes/60)*3600) if (seconds>=59.5){ seconds=0; minutes+=1; if (minutes==60){ minutes=0; degrees+=1;}} quadbearing=prefix+degrees+"°"+text(minutes,"00")+"'"+text(seconds,"00")+"''"+postfix; return quadbearing; } function DMS(bearing){ degrees=floor(bearing); minutes=floor((bearing-degrees)*60) seconds=((bearing-degrees-minutes/60)*3600) if (seconds>=59.5){ seconds=0; minutes+=1; if (minutes==60){ minutes=0; degrees+=1;}} DMS=degrees+"°"+text(minutes,"00")+"'"+text(seconds,"00")+"''"; return DMS; } function IsValidCOGO(direction, distance, radius, arclength, radius2) { binaryDictionary= Dictionary('dir', 1, 'dist',2, 'rad',4, 'arc',8, 'rad2',16) if (!IsEmpty(direction)) {checksum+=binaryDictionary.dir} if (!IsEmpty(distance)) {checksum+=binaryDictionary.dist} if (!IsEmpty(radius)) {checksum+=binaryDictionary.rad} if (!IsEmpty(arclength)) {checksum+=binaryDictionary.arc} if (!IsEmpty(radius2)) {checksum+=binaryDictionary.rad2} validValuesArray=[0,3,8,13,29]; //array of valid combinations: '0' for nothing, ... '13' for direction & radius & arclength ... partialValuesArray=[1,2,4,20,13,16,21,25,28]; //array of partial combinations: '1' for only direction, '2' for only distance... if (IndexOf(validValuesArray,checksum)>-1) { // a negative value is returned if checksum value is not in the a valid combination array return "valid"; } if (IndexOf(partialValuesArray,checksum)>-1){ return "partial"; } return "invalid"; } COGOValidity = IsValidCOGO(direction, distance, radius, arclength, radius2); if ( COGOValidity == "invalid") { //if invalid COGO return error string return ErrorString; } // Direction string if (ShowDirection) { if (IsEmpty(direction)==false) { if (QuadrantBearingFormat==true) { //using quadrant bearing format directionStr = NorthAzimuth2Quadbearing(direction); } else { //using north azimuth format directionStr = DMS(direction); } } } // Distance string if (ShowDistance) { if (IsEmpty(distance)==false) { distanceStr = text(round(distance,DistUnitRounding), NumberFormat); } } //Radius String if (ShowRadius) { if (!IsEmpty(radius)) { //it can be a curve or a spiral if (IsEmpty(radius2)) { //if radius2 is empty this is a curve radiusStr = RadiusAbbr + " " + text(round(radius, DistUnitRounding), NumberFormat); } else { // it is a spiral radiusStr = RadiusAbbr + " " + text(round(radius, DistUnitRounding),NumberFormat); radius2Str = Radius2Abbr + " " + text(round(radius2, DistUnitRounding),NumberFormat); if (radius == 0) { //substitute to infinity sign radiusStr = RadiusAbbr + " ∞ "; } if (radius2 == 0) { //substitute to infinity sign radius2Str = Radius2Abbr + " ∞ "; } } } } // Curve Parameter if (ShowCurveParemater) { if (!IsEmpty(arclength)) { if (CurveParameter == 'ArcLength') { curveStr = ArclengthAbrr + text(round(arclength, DistUnitRounding), NumberFormat); //return Arc length } angleRad = arclength/(abs(radius)) //calculate angle in radians if (CurveParameter == 'Angle') { curveStr = AngleAbbr + DMS(angleRad * 180 / pi); // convert radian to degrees and show as DMS } if (CurveParameter == 'Chord') { curveStr = ChordAbbr + text(round((2 * abs(radius) * Sin(angleRad/2)),DistUnitRounding), NumberFormat); //calculate chord length } } } // Assemble label string if (IsEmpty(radius)) { //if its empty it is not a curve return directionStr + " " + distanceStr } else { //it's a curve return radiusStr + " " + radius2Str + " " + curveStr; }     ... View more

Jeff, My fabric layers also show the warning icon and tell me that I am not running the latest version. I am on 2.8.2 and running version 4. The Upgrade Dataset tool tells me that I am already on the latest version. I also see this warning when running the Validate Parcel Fabric geoprocessing tool. It has been like this for as long as I can remember. I have just ignored it since it doesn't seem to be causing any issues.   -Paul ... View more

That sounds exciting! I think I will just abandon this until the new tool comes out.    Thank You! ... View more

Amir, thank you for the reply! I am glad to know that it's not just me. That makes sense since it's the geodatabase topology that is evaluating the rules and retired and current parcels are stored within the same feature class, but are displayed in two separate layers on the map. I was thinking that this may be causing my attribute rules to identify parcels as overlapping when they're not actually overlapping, but it appears that is not the case. So, how do I get the No Overlaps attribute rules to correctly identify overlaps? If the rule is correctly identifying overlaps, how do I find where this parcel is overlapping? I haven't been able to locate the offending vertices or areas of overlap. Using align tools doesn't usually solve the overlap for me.   I will see if I can get some screen shots or upload the offending data and I'll play around with this a bit more today to see if I can find the overlapping area.  ... View more

I opened a support case and we were able to overcome most of my performance issues by doing the following: In Windows Defender, add ArcGIS Pro as an exception. Clear Pro Display Cache regularly. Do not let this get above 1GB or so if you can help it. The larger the cache, the slower Pro gets. Lower display graphics settings in Pro Options. Also disable hardware antialiasing I am running Pro 2.6.2 and these steps greatly improved my performance on several workstations. I don't know why Esri doesn't make this more readily available in documentation. My issues were: General UI lag and lockups Traverse tool input lag 5 seconds or more lag when moving between cell blocks Turning layers on and off resulted in UI lock for 5-10 seconds *Data is FGDB on C:\   ... View more

This worked for me! I also cleared the display cache and will clear it regularly through Project/Options/Display This gives massive improvements in speed and so far UI hang-ups are minimal. ... View more

Anne, If you have a Standard or Advanced license, on ArcMap's COGO toolbar; COGO Report manually measures the direction and distance of your line Reporting COGO descriptions—Help | Documentation  COGO Area uses the COGO enabled feature's COGO dimensions to calculate the area, not the drawn dimensions Calculating COGO area—Help | Documentation  About calculating COGO area—Help | Documentation  This may also be of help; Calculating area, length, and other geometric properties—Help | ArcGIS Desktop  Hope this helps!! Paul ... View more

While I am able to get this method to work for attribute tables in WebMaps, these settings do not carry over into a WebApp attribute table that is created from the map.  ... View more

Chris, did you ever find a solution to this? ... View more

Dan, thank you sir. I will inquire over on GitHub. ... View more

As one idea, I conda upgraded arcgis to 1.8.0.  Still no go. ... View more