Latest Contributions by alex_friant

Oh wow, "Today I Learned". Thanks for the insight on that and apologies for misspeaking. I'll try it out! ... View more

Looks like that site you posted is a "beta"?  Have you tried using this one? https://ago-assistant.esri.com/ ... View more

Almost 6 years later, using ArcGIS Pro 3.1.2, and this simple advice fixed an issue that sprang up the last few days which is Pro would lock up (windows says "Not Responding") when trying to close a map view, layout view, or even trying to just close Pro. You're the real MVP! ... View more

The Scene tab offers maps that do that. I'm thinking that's why they don't have North Arrows in the Maps tab because those maps don't rotate and North is always up. ... View more

Wow, you're right. There it is right there. They should add a tool tip when you hover over those options that state this so users aren't thinking it's buggy behavior. ... View more

It's the simple solutions I like. Thanks! This did the trick. ... View more

I couldn't figure a way out (using a FGDB to store annotation) to rename an annotation class either. Like you, if I renamed the subtypes the annotation class name stayed the same in the Annotation Feature Class Properties. I resorted to creating a new annotation class with the same properties and naming it how I liked. Then I had to select all the annotations using that class, change their Annotation Class ID using the Attributes pane, and change their Symbol class to match under the Annotation tab in Attributes. Seems like any label class, we should be able to simply rename the Annotation Class using the Feature Class Properties pane for the Annotation FC. ... View more

The date of when a feature is deleted is stored in the SQL table of the same name suffixed by "_H", under the field "GDB_TO_DATE". For example, if your feature class is called "schools" the archive table is called "schools_H". They really just need to add a field for deletions like "DELETED_BY" so you could have the "WHO" of the "WHEN by WHO?" question. ... View more

I got this answer from a "note" in this Esri technical article. In the Symbology pane of the layer, under the Properties tab, click Layers: Select the symbol layer to configure and expand Dash effect. For the At line ends property, select the desired option other than No constraint. I just did this and it worked. I flipped it from "No constraint" to "Full pattern" and now all dashed boundaries along adjacent polygons draws as dashed with no overlaps. ... View more

Now that I see the Filter option in the TOC which allows you to display only layers that have Active Definition Queries, I can work with that. That being said, I think a super simple, subtle way of indicating a layer has an Active DQ would be to just add a chip to far right of the TOC pane, like below. And if you hover over it could tell you what it means. Active DQ indicator chip   Hover pop-up gives context  The reason this is important is in a multi-user environment. You might have a colleague (or yourself 2 weeks ago!) that comes into a Map to do some work, adds a definition query, and you don't know that. You come back into the Map weeks later and decide Share it to some static output (e.g. Map File) assuming the layer is displayed in full. Without a chip or something indicating that a layer has a DQ applied to it, you wouldn't notice it until downstream (customer, client, colleague). Another option is to add the "Filter Applied" warning to every single output process (i.e. Layout Export to PDF, Share as Web Layer). But I feel this chip in the TOC would be a fair compromise without having to add the warning to a whole bunch of other tools. ... View more

From the video it's clear there is a bug with that type of complex SQL query. The bug being that when you open the DQ in Properties, it automatically disables itself.  I can't replicate it though. I had a similar SQL query (nested, but no joins) on a mobile geodatabase and it didn't bug out like this. I'm using Pro 3.0.3, btw. ... View more

@wayfaringrob  - Absolutely, having a single pane where it makes sense would be even better. Like Selectability, Visibility, Editability, Snapability are all things that are often used during editing and could line up as 4 separate check boxes next to the layer names.   ... View more

Great idea. Seems like an easy change to add the option be it an extra single entry field or even a toggle option. While I think it would be cool to have the default interpreter to be "smart" - aka: it attempts to parse the coords using some intelligent analysis, like Google does, I think it would be a bonus to have a "custom configuration" option that allows you to explicitly tell it how to interpret the coords you are entering in case the smart entry doesn't work. ... View more

This was an amazing tip. I've never heard of this tool in all my years of doing GIS. Thank you so much for sharing! ... View more

This is a very good idea. The behavior pattern is already implemented from the Catalog Pane/View to a map when you can drag/drop a feature class to a specific map. It would be great to be able to drag a layer/table to a already opened table and have that open the attribute table in that table view group. Bonus points to have the positional icons appear so you could choose to dock the table where ever you wanted. ... View more