Latest Contributions by JakubSisak

Should be fine for occasional work. 4K monitor will consume a lot of GPU power and connecting it to external monitors especially if they are 2 or 4K is not going to cut it without a better GPU.  As for ArgGIS PRO performance, you will be disappointed no matter what because PRO is slow. period. (especially when you have a lot of layers, complex symbology, annotations, lots of graphic elements in the layout, etc.) I have higher specs in my 17" 4K laptop and although Pro runs fine it's still underwhelming.  ... View more

Thanks for the response. I subsribed to watch the bug status. Also, I just tried saving the .xlsx as CSV and running Make XY Event Layer again and it succeeded but I further cleaned up data and ensured data in X and Y columns were in fact numeric and valid. ... View more

I am experiencing all of the above and more myself.  In my experience the selecting/drawing/rendering issues are most noticeable when working with annotations and graphics in layouts.  While working Pro is constantly rendering and drawing for so long  that I spend a lot more time waiting for things to finish refreshing than actually doing anything.  Because I can't upload large video files here, I am preparing a set of video captures and uploading them to my YouTube channel and will include some links when those are done.  Here is an example of one showing how slow selecting and refreshing of graphic elements in layout is: https://www.youtube.com/watch?v=fwStNdL-S6Q&t=32s Note WRT the video capture - there is no map frame or data in the layout. just graphic elements and text. It takes several seconds for Pro to even acknowledge a selection has occurred as it "sits still" (often ~ 10 seconds). then as it commences to refresh and render, the refresh indicator spins for a long time each time.  My machine is older but the specs are as follows: Intel Xeon E2-2667 @ 2.9 GHz (2 processors = 24 cores), 32 GB Ram, Windows 10 Enterprise 64 bit,  NVIDEA 1070 ti,  OSDrive is a recent solid state HDD, etc.  Also I am running OpenGL @ LOW rendering quality UPDATE: I've tried a few things on a few machines and I think I am onto something. At least with graphic elements in the layout the issue "SLOW REFRESH / RENDER" seems to be directly related to the amount of graphics in the layout; a few graphics will refresh reasonably fast, 200+ graphics which is average for a typical static legend refreshes MUCH slower. Create a copy of the legend in the same layout (What I would often do in ArcMap as a backup of the legend) and the selection/render/drawing will slow down accordingly with the increased amount of graphic elements.  There is some very inefficient looping going on behind the scenes coupled with the curious fact that ALL graphic elements have a corresponding item in the TOC. Yes. I understand the intentions of being able to order things like layers in Adobe but having 100s of graphics constantly updating on screen and in the TOC is causing some issues. Adobe doesn't seem to have this issue. I didn't even get into re-doing some really complex geology maps with 1000s of graphics yet. Not looking forward to it.  I will take a video capture documenting this observation and post.   ... View more

Could be an issue with the TINs. Can you post a screen capture of the surfaces?  There should be 2.5D TINs or surfaces - non self intersecting, not enclosing a volume.  Can you perform CUT/FILL and get a volume number as a result? ... View more

As of April 18, 2019 ArcGIS Pro version 2.3.2 there is still no undo/redo when editing web feature services in desktop applications.  ... View more

Hi Tom,  That is in fact the issue.  Switching it to Arial offsets the labels correctly to the same distance.  We use designer fonts such as Myriad Pro, Frutiger, Optima and Cisilpin and other Adobe and drafting fonts such as Conduit ITC.  Every one of those fonts exhibits the incorrect offset issue. I also tried the default Microsoft Calibri font and it also has this issue.  I also tried Currier New, Tahoma, Corbel and others and all of those have the problem. Courier New is interesting because it is a typewriter font and often used by programmers because spacing between letters and font height is guaranteed to be consistent.  Of the few fonts I tried that do work correctly are Arial, Times New Roman, Garamond and Helvetica.   ArcMap offsets ALL fonts correctly so must be using a different method rather than the edge of the bounding box. If I may suggest offsetting the label using the center of the bounding box rather than the edge may be a better solution.   For now we will use the few fonts that do work for the grids or use 2 grids with different offsets for designer fonts.  Thanks for your help.  Using Arial font - no issue: Using Calibri font - font is offset differently along top (North) and vertical (East) edge: ... View more

Thanks Kory. Any way of being able to track bug status without having to contact tech support? there is a number of them i would like to monitor.  ... View more

HI Tom,  Thanks for your reply. Doesn't work for me. You can't probably notice it when you offset to an inch.  We need to nudge these offset values by MUCH smaller numbers to fit them inside of double and triple neat-lines for precise cartographic placement.  Here is a screenshot. Made a simple layout, added a random map zoomed in and adjusted the offset to 0.03 positive value for outside of the map frame, then in the second screen shot -0.1 negative value to place these inside the line. You can clearly see that the distance from the map frame is NOT the same for the NORTH and vertical EAST labels. (North and West labels have a different actual offest in the layout than East and South labels even though the offset value for both is the same as it controls the offset for all labels) Adjusting offset value of tics works correctly.  When using positive offset value: When using negative offset value: ... View more

As of v 2.3.2 this (panning with the mouse wheel), like many things in Pro, is half baked. Still feels like some kind of Alpha release. The behaviour is inconsistent and flaky. Sometimes it works, other times the middle button is not responsive until the explore tool is clicked.  We are almost entirely migrated to pro and forcing ourselves to use Pro for everything (90% of the time) but when doing heavy duty editing, clipping, merging copying and pasting of features between layers, the experience is one of constant frustration with so many bugs and glitchy and strange behaviour. Only going to ArcMap when necessary but it is very much still necessary. Whenever I go back to ArcMap it amazes me ho fast and reliable it is. It may be old, it may be 32 bit and on a single thread but when it comes to editing, Arc Map is still the king.  Designing the entire editing process in Pro should not be left entirely to programmers and people that do not actually spend days and weeks editing complex geometries.  ... View more

It doesn't matter whether I am logged in or not - the button is disabled. ... View more

I have this issue with my personal ArcGIS i use at home. The statement in the Info Box is incorrect: I am logged in into my ArcGIS online account and  the button is disabled. Somehow i don't have this problem at work with my work software (different account)  ... View more

This is marked as ANSWERED but I disagree as the problem of not being able to correctly offset labels on a grid is still present in version 2.3.2. The current workaround is to have 2 of the same grids and offset north and west labels to a different value then east and south labels provided you are aware you must force focus away from the offset text box every time you change and apply value as there appears to be an issue with that as well.  ... View more

@Kory - it may have been resolved in 2.1 but the bug has been reintroduced in 2.3. I am on 2.3.2. Offset value offsets labels on the north and west differently then east and south.  This is especially apparent when east and west labels have a vertical orientation and north and south labels have a horizontal orientation. there is also something wrong with the offset value text box - it must loose focus to accept a new value otherwise the value entered offsets labels to incorrect value.  The only workaround that works is to have 2 grids; 1 with north and west labels the other with east and south labels.    ... View more