Latest Contributions by BranislavBlagojevic

Yes!  I  agree! ... View more

Kory, Many Thanks for answer. The essence of this problem is in the attribute-driven symbology/es assigned to features is not reflected in the legend information for the feature layer, when the Primary Symbology Method is Unique Values. In practical terms for the user this means that he must either manually or outside of ArcGIS Pro create a legend (!!!) even though he has predefined the symbology attribute with RGB, HEX or CMYK Code (extremely important when sharing only geodatabase as a repository - no layer, or publish this straight to AGOL). It’s a little absurd; the layer in the Map will show the colors that will be read directly from the attribute table, but the legend of the same layer(s) will show Unique Values ​​colored by the default ArcGIS Pro color scheme (!?!). With the implementation of Eyedropper (AGP, ver. 2.7) the situation (at least in my case) is partially simplified, because the user can take the color from the symbolized Feature(s) in the Map and re-colorize the item(s) in the legend, but ... only when the number of unique values ​​is small (eg <15), because the procedure must be repeated for each item. Thus, there is no possibility here for an infinite combination of successful/appropriate symbolization; it is pre-defined by the attribute(s), and ArcGIS Pro only needs to execute it completely - in Map and Legend. I have a small example (Project and same as zipped archive) that I used and am using for testing and that I have already sent through Beta testing (AGP ver. 2.6 or 2.7?). I will be happy to send it to you for testing and a better understanding of the problem, but there is no Attachment option here. Do you want me to send it directly from email? Maybe it could help solve and fix the problem. Regards.   ... View more

Kory, ArcGIS Pro BUG-000104316 related to 'attribute-driven color in symbology' was confirmed four years ago (April, 2017), but has not been fixed to date. The status of this Bug was changed earlier this year (?) From "In Current Product Plan" to "Not in Current Product Plan" (!) with info that has nothing to do with this serious problem https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEwNDMxNg== This is an elementary thing in the process of automated cartography (see more at Setting up the attribute-driven color in symbology... - Esri Community) and it's time to fix this at last! Thank you! Regards. ... View more

Thanks, Kory. My comment - the suggestion is related to ArcGIS Pro, primarily to the date/time of creation and modification of fgdB items (FD, FC, Tables and Relationship Classes). Editor Tracking is a great way to record/track dB modifications, but from a personal point of view, it seems more acceptable to egdB. Hence I think for fgdB ESRI should implement this possibility! Regards. ... View more

Yes. I guess the time has finally come for that, as well as for displaying the date and time of creating/modifying Feature Classes and Tables within the geodatabase. ... View more

Yes! That would be very good - clear and operationally efficient! ... View more

Try this: go to Clean uninstall of ArcGIS Pro - Esri BeLux and follow the steps for uninstallation and new CLEAN installation.   ... View more

Checked. 'Fields View' works without any problems (in Catalog and Map View). Try restarting your computer, but you'll probably need to do a 'Clean Install'.   ... View more

Open attribute table and select row(s) in which are your polygons! ... View more

It is obvious only that the programmer and the author of the help do not understand what they actually did (formula), i.e. wrote. A more detailed explanation in this regard has already been requested from users, but has not been provided by ESRI. ... View more

Yes! ... View more

With the introduction of bivarite colors symbology, the symbolization procedure described here is no longer applicable. Even after 4 years, ESRI did not solve the problem with the attribute-driven color in symbology, i.e. BUG-000104316 not fixed (!?!). But, during that time, regarding this, something still worked and that, of course, to the detriment of the users: the status of the bug from In current product plan changed to Not in Current Product Plan (!?!) https://support.esri.com/en/bugs/nimbus/QlVHLTAwMDEwNDMxNg== Commendable! And went a step further with "Additional Information: Duplicate of ENH-000135498: Better display of symbol preview or legend when conflicting visuals happens either through visual variables, scale based sizing, or attribute driven symbology ". I therefore ask the ESRI author who changed the status of the bug to explain what the ENH-000135498 has to do with the unresolved issue contained in BUG-000104316? What does the word "duplicate" mean in this context? How long do we have to wait to solve the problem of not reflecting the symbology assigned to features in the legend? ... View more

Nice! ... View more