Latest Contributions by AZendel

It does! Thanks. I had scoured the Properties dialog, but didn't see that one line that adds a leader. But when you click an out-of-the-box text symbol that shows a leader and then add it to a layout, someone could argue that the leader should be present automatically. Perhaps this should be a suggested enhancement. ... View more

Is there any way to do this with a graphic text (not map annotation nor database annotation) on a layout?  If I select the out-of-the-box "callout" symbol from the Text subpanel on the Insert panel and then drag a box, I don't get a leader.  How do you put text graphics with a callout on a map layout?  I'm using Pro 2.5 (just released last week) ... View more

Thanks for the follow-up. In this particular case, graphic designers later place the map into larger kiosk layouts. They asked me to keep things vector as much as possible. Also, all of the colors in the map accord to the CMYK color scheme that they developed. If I export to PNG or JPEG, I can't set the destination colorspace to CMYK . The colors in the exported image are way off.  We'll just keep using ArcMap until this gets resolved, hopefully soon. I enjoy using Pro much more than ArcMap, especially since ArcMap doesn't use any type of anti-aliasing and I have to export to a PDF to see my layout it in a crisper view.  ... View more

Unfortunately, I just downloaded ArcGIS Pro 2.5 and the grids are still showing up in exported PDFs.  ... View more

In my situation, I can't access the .loc file. The locators that myself and many others in the county use is served via ArcGIS server (currently 10.5.1); I can only access it via REST services. When I geocode a table of addresses in ArcMap, the form allows me to change the settings (screenshot in my original post). So adjusting the settings via the client side is possible. But it looks like you can't do this via Pro. Much needed ... View more

Any updates? While I can connect to and edit a "Personal ArcSDE" geodatabase (one rung down from a "Workgroup" database) that I created in ArcCatalog, I cannot create new databases via Pro.  I'm on the most current version: 2.4.3. ... View more

I think I'm experiencing a similar problem with a join in Pro. I have a 'stand alone table' (no geometry) and a polygon feature class in a single file geodatabase. I'm trying to find 'missing polygons', that is records that are in the stand alone table at are not in the polygon feature class. So I joined the polygons to the stand alone table on a single common field (our case number). However, very few records show a case number in the joined field, suggesting that we have > 2000 missing polygons (that is, case number on the polygon featureclass is null). When I do the same join in ArcMap, we only have 292 missing polygons. I've redone the join in Pro several times and but I always get the erroneous join results.  ... View more

I recently tried to "fake out" or circumvent this issue by creating a transparent DEM over a hillshade layer in ArcMap and then exporting them as a georeferenced jpg file. Then I dropped the jpeg into Pro, but I still saw lines/grid when I exported the PDF from Pro. I'm not sure if this unusual workflow created other issues with respect to the grids showing up. But this attempted approach was a dead-end for me.  ... View more

UPDATE. This checkbox is available in both the Add Join tool and as an environment variable for the entire geoprocessing model. Initially, I only unchecked this setting on the Add Join too. But after I unchecked this setting in the model environment, the field names were no longer fully qualified - i.e., it worked as intended. ESRI staff.  Please consider adding some text to the Add Join help page explaining that this setting needs to be set on the model level as well as the tool level. Thanks! ... View more

This happening to me in 2.4.0 when using Add Join --> Copy Features in model builder. Initially, the join table was a CSV file. But I tried using the Table to Table tool to import it into a FGDB and then do the join. But the fields were still named table_field. I believe I had this problem in ArcMap as well.  ... View more

Did you mean, I guess my confusion is when I edit in ArcMap this behavior does not happen. I concur. I've been splitting lines and polygons in ArcMap for over a decade. I'm pretty certain that the fields that had domains never got set to null (I just tested it - no changes to the attributes after a split). This new behavior in Pro is an unwelcomed hassle, especially on feature classes that have numerous coded value domains. Also, having to change most of our domains from 'default' to 'duplicate' is not a fun task to think about. Remi's script will definitely be a time saver for many people (thanks, Remi!), but I'm typically hesitant to unleash scripts of that nature on our SDE database - and I probably couldn't do it anyway because I don't 'own' the domains. Then we also have a hefty number of file geodatabases with domains at various locations on our file server.  ESRI, I think the default setting for domains should be 'duplicate' and not 'default'. I think most people expect the behavior of the 'duplicate' setting, especially when splitting lines and polygons in feature classes that have multiple domains. And, out of curiosity, why have you only started enforcing this at Pro 2.3 (or 2.4, whichever new version implemented this change)? Also, I think changes of this nature need to be communicated to your users. Was this announced anywhere (blog, release notes, etc)? Below is a consequence of this change. I recently split features in our greenways and trails feature class since they are being reconfigured/moved. Fields that control the display of those features were set to null during the split (Status = 'Open', Typology = 'Shared Use'). So those trails weren't displayed in our various tile caches, like the missing segment shown in blue below.  ... View more

Hello, Did you ever create a 'look up' table for the MUTCD codes?  One column as the code (R7-2E) and the other has a description ("No Parking")?  I could really use that right now! Thanks, Alex  ... View more

Thanks for the suggestion. I've looked into using SQLite in the past. The big hitch is that you can't edit SQLite data in ArcGIS (ArcMap or Pro). I tried Pro 2.3.2 last week. The database that I tried to edit was a geopackage created in Pro, so I doubt there were any compatibility issues with potentially unsupported versions of SQLite. In this thread, ESRI staff more than hinted that SQLite editing support is coming. But it seems like it's been repeatedly moved down the priority list.  I tried using the open source ODBC driver for SQLite in Access (Thank you, Christian!). Overall, it worked very nicely.....until I tried to update a row with a date field in it. Or a geometry field. But there's a good chance that I didn't configure something correctly. Those are pretty small issues that I can mostly work around. Access functionality is pretty important because you can easily create reports and forms.  So it'd be nice to have geodatabases natively supported in Access, but I would definitely be stoked to have SQLite access to our geo-data as well.  ... View more

Thomas Colson wrote: To ESRI's credit, in the same document, "It isn’t an update to ArcMap, but a totally new application...", but most customers aren't looking at it that way. We really don't have the luxury of running two desktop GIS platforms side by side for more than a few months.  I agree that most customers don't look at it that way as well. We still need to get our work done .... and we need to do it safely. I myself am very receptive to changes in workflow and which buttons to push in which order. And there are numerous improvements that Pro brings - features that I love. But when we can't do our job without worrying about the safety of our data, then I really wish ESRI would listen to us and make Pro work like ArcMap in these respects. I don't understand their resistance. If this isn't the way that Pro is going to work out of the box, then please give us the option to enable out requested functionality.  Related content about Pro editing concerns: https://community.esri.com/ideas/14454-arcgis-pro-provide-an-option-that-requires-all-edit-sessions-to-be-manually-started https://community.esri.com/ideas/13988-improved-save-edits-by-allowing-to-deselect-an-fc?commentID=69616#comment-69616 https://community.esri.com/ideas/14075-arcgis-pro-edit-session https://www.esri.com/arcgis-blog/products/arcgis-pro/data-management/dont-fret-it-just-edit/ And I agree: this is a bug. Additionally, these workflows work in ArcMap, so they can be implemented in Pro. This is not a database issue. If only they would listen..... ... View more