Latest Contributions by TylerSchwartz2

You need to manually refresh by right clicking on the folder/geodatabase and hit refresh. And yes, you need to do this every time something changes in your .gdb (or any file/folder) outside of Pro or you wont see it. This is a known issue in Pro as it does not automatically update the catalog/folder tree as it does in most other Windows applications.  Not sure why this exists in Pro but I must imagine its a bug. The manual refresh needs to be done both in Catalog view and also when you are manually navigating to files (for instance if you were to hit "Add Data" and navigate to your .gdb those feature classes would not be shown until you hit "F5" to refresh the view, while you were inside the .gdb). I run into this issue frequently using Business Analyst Desktop (which must be run through ArcMap) where I am doing much of the analysis work, and then bringing those features into Pro for the cartographic outputs. Sure doesn't make sense to me, but at least there is a workaround...  Here is a topic I started on the same issue: Pro doesn't update folders or files "in real time" within GDB when modified outside of Pro  ... View more

How do we access the underlying .json style file, edit and repackage? I've played around with the .json styles on the ESRI vector tile basemap layers (human geography basemap) and know roughly how to edit and play around with those styles.  ... View more

Same issue here.  I am trying to make a vector tile package for a street map overlay and I am using offsets for my road labels (so they display offset from the road lines) and when creating the tile package, they are forced directly on top of the line, and not offset.  This is in Pro 2.0.1 There are also major issues with features not rendering at certain scales when converted to a Vector Tile Package (probably related to "[BUG-000103167 Error 001854 ....]").  Being able to author Vector Tile Packages is a pretty critical feature and would like to strongly encourage ESRI to focus on getting not only this bug, but the many critical bugs currently in Pro, addressed (please). ... View more

We are almost 1 year into this bug being logged, and I am also encountering this problem.  I cannot get my tile scheme to be accepted (getting the error 001854) even though I have my tile size set to 512x512 pixels @ 150dpi in the "Create Tiling Scheme" tool (still confused why we are talking pixels and dpi if its a vector tile package, but whatever...) Ok, so lets just forget a custom tiling scheme then and run the Create Vector Tile Package tool with the "Package for ArcGIS Online..." option checked.  Now we get large swaths that do not render at multiple different scales - as others have mentioned... As the final alternative, lets uncheck "Package for ArcGIS online" and use the default tiling scheme that is automatically filled in (in my case since my map is in WGS84 its "VTTS_4326_GCS_WGS_1984.xml").  Going this route seems to give me the best results although, I am getting some areas where features arent rendering at certain scales (but not nearly as bad as having the ArcGIS Online box checked). So where I am at, at this point, is that I have a less than perfect Vector Tile Package that mostly renders correctly (except at scales between 355k - 600k), and that is seemingly the best we can do at this point...  Really hoping that ESRI can get these (and multiple other bugs) fixed in Pro because at this point we lack critical functionality to create a basic vector basemap without rendering issues.  If anyone has some pointers on how to address the rendering issue(that I am perhaps missing) given the above workflow, or how to get a custom tiling scheme to work without the error 00184, that would be great. ... View more

The workaround that I found is to take the TPK file and Extract it using a program such as 7-Zip.  Within that extracted folder should be a folder "v101". If you navigate to that folder using "Add Data" in ArcGIS Pro, you should see a raster image within that "v101" folder.  Add that to your map and your tile package should now be visible.  This worked for me (your results may vary).  This is using ArcGIS Pro 2.1 Not sure why TPK files aren't supported in Pro (yet we have a tool available to create them) when there is such as simple workaround for it - youd think this would be supported! ... View more

Back when I first switched to Pro I was using all my .lyr files from ArcMap, but quickly re-exported them all out to .lyrx files. There are definitely bugs (which I have reported) still to be worked out in symbology (and for that matter, layer heirarchy in the ToC where one layer displays over another despite being below it in heirarchy).  Another example is that since 2.0, Pro crashes anytime I try to add an additional map to the project.  I have submitted countless crash reports on that issue alone, and still remains unresolved in the latest version 2.0.1 (the issue wasnt present in 1.4).  All these bugs create a perception that the software isnt "ready", it isn't fully optimized and tested - still a work in progress. But just overall, the delay and responsiveness of the UI is way behind ArcMap when it comes to doing tasks like editing an attribute table, running a calculate field, and applying a symbology.  ArcMap executes these tasks almost as fast as I can click and move my mouse - in Pro there is a lag and delay on almost everything.   I have a pretty beefy desktop so I *should* have the processing power, the GPU (Nvidia Quadro M4000), 16GB RAM and hard drive read/write (solid state Samsung NVME) to have fast, responsive framerates. However, Pro doesnt seem to be able to utilize the hardware to its fullest extent. For instance, I never see above 20% cpu usage with pro - is that normal? It seems like Pro should be able to use more... Ideally I feel like Pro should have the fast framerates that I see in ArcMap when performing the exact same tasks, given that it is 64-bit and apparently can utilize multiple cores... Again, with the numerous bugs still present in Pro my perception is that the software isnt optimized properly and there are still plenty of bugs remaining in the software which are/could be causing performance issues. ... View more

I would just like to add that simple tasks such as editing an attribute table or changing symbology, is painstakingly slow compared to ArcMap (although I do like the new way of editing, no need to go directly into edit mode).  And as the OP mentioned, 20 seconds here, 20 seconds there definitely add up. Overall it seems these simple tasks are slow, delayed, and much less "crisp" and responsive than in ArcMap.  I think I have a pretty powerful desktop machine but the constant spinning blue wheel, hangs, and crashes are really leaving me frustrated with Pro - which should be faster, better, stronger than ArcMap (and still retain the same functionality).  Although the difference for me is that I am not using ArcMap .lyr files - I have converted all of mine to .lyrx.   ... View more

I think there is an issue with Pro and multi-threading - as my assumption is that a 64 bit application (that claims to be able to take advantage of multi-threading) should run faster on my machine than a 32-bit ArcMap application. Like the OP, I am also seeing much slower performance with Pro vs ArcMap on my machine. Doing very simple things like calculate field, selecting features within an attribute table, doing edits, changing symbology all take substantially longer in Pro... As a side note, I am getting crashes when I try to Insert a new map into the project that appears to be in relation to Multi-Threading (but maybe I am wrong on that diagnosis).  Event Viewer shows the following: Application: ArcGISPro.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ArgumentException at ArcGIS.Desktop.Internal.DesktopService._IMapAuthoringService.CreateNewMap(Int32, System.String, ArcGIS.Core.CIM.MapViewingMode, ArcGIS.Core.CIM.MapType, ArcGIS.Desktop.Mapping.Basemap, Boolean) at ArcGIS.Desktop.Mapping.MappingModule+<>c__DisplayClass443_0.<CreateNewMapAsync>b__0() at System.Threading.Tasks.Task`1[[System.Int32, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].InnerInvoke() at System.Threading.Tasks.Task.Execute() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at ArcGIS.Desktop.Mapping.MappingModule+<InternalCreateNewMapAsync>d__1191.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task) at ArcGIS.Desktop.Mapping.MappingModule+<InternalOpenCreateNewMapAsync>d__1334.MoveNext() Exception Info: System.AggregateException at System.Threading.Tasks.TaskExceptionHolder.Finalize() My machine specs are as follows: All my data is local on a very fast 250GB Samsung NVME SSD (so read/write is not the issue here I am afraid). I am also running a NVIDIA Quadro M4000 GPU and ArcGIS Pro 2.0.1, but this issue first started occuring in 2.0.0 - I have submitted countless crash reports. Our organization has a maintenance subscription so if anyone from support can reach out on this issue, it would be greatly appreciated. ... View more

A pop-up stating that there are unsaved changes pending before the "edit field" interface even comes up would easily solve this problem. Having a button greyed out with no indication as to why is very frustrating and isnt the most intuitive from a UI design perspective. ... View more

Hi Joshua, Just like Kory mentioned, I have a "dummy" pro project setup (and a geodatabase) in a folder on my desktop (or wherever works) that I use for these types of quick data manipulation tasks, or if I need to export a quick and dirty map.  I reuse this project over and over and just delete the features from the last set of tasks once I reopen it May the Schwartz be with you ... View more

Hi Joshua, Thanks for your reply. Workflow is as follows: Pro (1.4.1): 1) Select features using Select tool  2) Right click on feature in "Contents" , Attribute Table 3) within attribute table, click button "show selected records", top right corner of table, "export" 4) this opens "CopyRows_management" GP tool pane 5) select output location, change file suffix to .csv hit "run" ArcMap (10.5): 1) Select feature using Select tool 2) right click feature in ToC, open attribute table 3) within attribute table, show selected records 4) click top left corner of attribute table dropdown, "export" 5) export dialogue, Export: selected records 6) save as text file .csv I am not using Copy Rows in ArcMap as you can see from my workflow, and if Copy Rows is the issue, then how can I replicate my ArcMap workflow within Pro to get the desired results? The two workflows are almost identical, although it appears in Pro they force you to use the CopyRows GP tool in order to do this. This is a very easy and routine process in ArcMap. ... View more

Thanks Curtis, thats some great insight into how Pro works and why I am seeing this behavior.  Sounds like this is a separate issue from the Project Folder bug outlined in my second post.  A workaround to the file tree refresh issue is to use the Project Element Pane, adding the folder where your GDB resides, right clicking your GDB, refresh, and then dragging and dropping your feature class into your map.  I'll have to avoid the "Add Data" button from now on.  Thats assuming of course, that the Project Folder isn't bugged - but I believe that issue resides with Project Folders added as part of a  Project Template.  I guess you can always delete the project folder and re-add it. ... View more