Latest Contributions by KateNewell1

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

Version 2.1.1 The parcel polygon feature class and the table are both within the same file geodatabase. They are joined on unique Parcel Code ID (text field) (inner join).  There are only about 300 records in the feature class. Not indexed. ... View more

Version 2.1.1 The parcel polygon feature class and the table are both within the same file geodatabase. They are joined on unique Parcel Code ID (text field) (inner join).  There are only about 300 records in the feature class. Not indexed. ... View more

Still having this issue when exporting jpgs over 300 dpi. Using ArcGIS Pro 2.1.3 ... View more

I am having same issue.  Using Arc Pro 2.1.3 ... View more

Also having issues with another portion of the storymap that is using an embedded image slider/carousel (created through Wowslider app).  In the "Infill Housing" section at the end of the story map, the image slide does not work in Chrome.  This is all specific to Chrome 67, but looks like not just specific to it's functionality with Tableau, but possibly any other embedded apps? Here is another story map with embedded apps (Infogram app) that is not functioning as expected in the side panel:  http://bluewatergis.maps.arcgis.com/apps/MapJournal/index.html?appid=5f1e62621fbb4241b1b58424f7040399 ... View more

Looks like other issues popping up with Chrome 67 and portal/geoevent manager: https://community.esri.com/thread/215947-geoevent-manager-not-coming-up-in-chrome  ... View more

Putting the tableau graph in an immersive section works slightly better.  Though when you navigate off the immersive section and go back to it, the functionality is lost again. This was true for the AWC section with Tableau graphic as well. Here is my test version of that:  https://bellingham.maps.arcgis.com/apps/Cascade/index.html?appid=1ba0bc4abeb44e2384856b50f46f9317  ... View more

Here is the latest update from Chrome. I am going to test putting the graph in an immersive section to see if that works, as other story maps with Tableau graphs in immersive sections seem to work. This amounts to a special case of the problem discussed in issue 647378. On MouseDown the browser locks input to the renderer process with content currently under the cursor, because of cases where you are dragging an iframe's scrollbar and the mouse leaves the iframe boundary, where we want the drag to continue uninterrupted. That logic is too coarse though, creating bugs like this, which we hadn't anticipated. Bug 647378 is not something we can address immediately. There is planned work on the Blink side to remove the notion of implicit mouse capture there, which would help a lot. A short term fix that might work would be to continue enabling capture on mousedown, but keep hit testing the original mouse down position on subsequent events. The capture would be immediately released if the original position results in targeting a different frame. There are going to be problems with that approach also but it at least could potentially resolve use cases that we know about until we can fix the problem more generally. ... View more

This story map uses tableau graphs in an immersive section and works for me on first load of the section in Chrome 67 https://awcnet.maps.arcgis.com/apps/Cascade/index.html?appid=c6ce694c116d44ddb2a40ab39e34b3ca  ... View more