Latest Contributions by JakubSisak

Attribute Transfer with this tools is not working as described above by others.  ... View more

Excellent suggestion and makes sense. There seems to be a noticeable improvement in basic editing and overall performance. Thanks @TroyBum72  ... View more

Hi Mike. Looks good!  Any way to use a field value in the HTML to control the width? ... View more

It would be great if ESRI added an option to also store photos in the Photos app where they are easy to retreive.  ... View more

I find that a project gets increasingly slow the more maps and layouts are added whether these are open  in tabs or not.  My recent crude workaround around these issues (though no workarounds will make Pro as responsive as ArcMap) is to create a temporary project with only a simple single map with 1 or 2 layers in which I do all my editing and other work.  This includes things like clipping and splitting features. Not perfect but better.  ... View more

Fast forward to October 2021 and version 2.8.3 and what the OP mentioned still remains an issue "every single step causes the program to whir and think for about ten seconds"  There are so many mysterious processing delays constantly stalling simple processes and hindering productivity I still often resort to getting things done in ArcMap instead.  Also random rendering issues make it seem that processes did not complete correctly. With time I learnt to close and open map or the application to render results in maps correctly but it's really really frustrating...  ... View more

Calling this a solution is incorrect. It is well know that there are rendering issues in Pro that have not yet been solved and this is one of them. This problem is not specific to annotations but all selections; anyone working in actual production editing environment experiences this all the time as the map rendering hangs all the time, specifically when making frequent selections with the  "Selecting... Press Escape to cancel." message. This is one of the reasons why myself and others when needing to perform many edits and selections still prefer to do these tasks in ArcMap which is lighting fast in comparison.  I would like to urge the OP to uncheck this as "Solved" as it has not been solved. OPs solution of copying data to a new map and working in that map until it starts causing issues is the only workaround for this. Clearly there is a rendering or caching problem somewhere. Not even mentioning I need to re-open map all the time sometimes restart the entire project to make Pro render things on the map and none of the workarounds, solutions, suggestions, etc. provided to date in numerous forums work.  ... View more

Thank You!  What a weird implementation. I can confirm this answer works but needs to be setup exactly as specified in the answer. However, I am still getting the very unhelpful message warning " The process did not execute because the precondition is false." I whish there was an option to supress the warning in this instance because no matter what one or the other branch will not execute because the whole purpose is to execute one of 2 branches based on the condition. I initially tried to set the Is Value Is with Comparison Type: Automatic detection and Values set to the Boolean parameter (checkbox in the tool) but it was always evaluating to True never executing the False condition branch.          ... View more

Kory Kramer    I would like to elaborate on this; It would be extremally useful to understand the way in which symbols within a layer (multiple values) are drawn by default - the main reason is drawing performance!  Using the Symbol Layer Drawing introduces an EXTREME performance penalty. The drawing performance functionality is only useful in cartographic applications where drawing performance isn't an issue.  Where this becomes a problem is when publishing dynamic feature services to a Portal. The performance hit is so massive, the only known crude workaround is to split up the layer into multiple layers with definition queries and order them in the desired order within a layer group.  Unfortunately managing so many layers and potentially pop-ups becomes very cumbersome.  If we knew what order symbols are drawn in Pro (without turning on the drawing order) we could potentially control this behaviour by creating a SQL View with a coded column (prefixed with a drawing order value) and then by adding this to the map drawing default drawing order would place the "coded" values in a specific order. However after running some tests I concluded that symbols are drawn in a random order and it the value in the attribute field is ignored. Ideally, if the default drawing order was the same order in which symbols are loaded into symbol classes pane - they are sorted in there, that would be best. Unfortunately, to force the symbols to actually draw in this order you have to turn the "drawing order" on - which, as I mentioned,  introduces a significant performance hit and depending on the number of symbols can slow things down exponentially. (from seconds to minutes) ... View more

Kory Kramer    I would like to elaborate on this; It would be extremally useful to understand the way in which symbols within a layer (multiple values) are drawn by default - the main reason is drawing performance!  Using the Symbol Layer Drawing introduces an EXTREME performance penalty. The drawing performance functionality is only useful in cartographic applications where drawing performance isn't an issue.  Where this becomes a problem is when publishing dynamic feature services to a Portal. The performance hit is so massive, the only known crude workaround is to split up the layer into multiple layers with definition queries and order them in the desired order within a layer group.  Unfortunately managing so many layers and potentially pop-ups becomes very cumbersome.  If we knew what order symbols are drawn in Pro (without turning on the drawing order) we could potentially control this behaviour by creating a SQL View with a coded column (prefixed with a drawing order value) and then by adding this to the map drawing default drawing order would place the "coded" values in a specific order. However after running some tests I concluded that symbols are drawn in a random order and it the value in the attribute field is ignored. Ideally, if the default drawing order was the same order in which symbols are loaded into symbol classes pane - they are sorted in there, that would be best. Unfortunately, to force the symbols to actually draw in this order you have to turn the "drawing order" on - which, as I mentioned,  introduces a significant performance hit and depending on the number of symbols can slow things down exponentially. (from seconds to minutes) ... View more

Perhaps it was the road Ahead. Apologies ... View more

Thank you sir. Just did.  ... View more

Thanks Scott. I did. You still have to populate the values prior the creating the feature. If you do not remove the the values the next feature you create will inherit those same values. This is prone to error. The proven approach is: display a floating window with attributes (all blank unless you have a default value in specified in the schema) immediately after a new feature is created on the layer(s) specified. This allows the user to enter the corret values after the feature has been created thus QAQC it visually as well and ensuring only new correct values are entered.  ... View more

So yeah, this was unveiled as the new 2.6 feature at the UC in July. In August when 2.6 was release it was not included. Why? ... View more

 Oh my.... The first time I needed to use this feature in Pro. At first I didn't know what the OP meant by " modify the attributes first before creating a feature" but wow... Idea now here: https://community.esri.com/ideas/18840  ... View more