Latest Contributions by RickHollatz

My apologies @JasonCamerano  I've just tried a bunch of times and different things to reproduce it myself before packaging the data to send, and I can't reproduce it now. It is working correctly with the same input dataset. Sorry for the effort but on the positive I'm happy to confirm it's working fine regardless of the topology.  ... View more

Just an FYI. I tried the script on a COGO enabled line Feature Class that resides within a FGDB Feature Dataset, said Feature Class also being involved in a topology, and it resulted in error. The same Feature Class was exported to stand alone in a FGDB and the script worked great. (ArcGIS Pro version 3.1.3). I didn't test further to see if it was due to being inside a Feature Dataset or if the topology is the culprit. ... View more

Hi Kory. I'm in agreement with the original post by @christinebrooks that additional options at the time of  new project creation would be a game changer.  I don't find that to be Already Offered.  What is offered at the time of creation is the choice of creating a new folder or not, and what you want the name to be of ALL home items.  What would be nice in the 'Create a New Project' popup is if you could specify individually: Name of folder (if option to create new folder is checked) Name of .aprx file that will be created Name of the .gdb that will be created Name of the .atbx that will be created I can understand the rationale of using a matching name for all items as it may help a user see that they are related (Home items), however, that logic quickly falls apart if you use Save As on the .aprx to create an additional APRX in the same location.  The second aprx file will have the original Home items and will not match in name anyway. My preference at the time of new project creation would be to always name the created home .gdb and .atbx files something like "Default.gdb", "Scratch.gdb", "Scratch.atbx", "Data.gdb", etc. The workaround is to 1. Create the new project with the default names, 2. Create new GDB and Toolboxes in the Home folder using the names you want, 3. Set those as the new Default geodatabase and Toolboxes, 4. Delete the ones that were autogenerated. This is a hassle every time you want to start a new project. I want to provide one other reason the default behavior is problematic.  That is that exceeding 256 characters for total path length can be problematic in a variety of ways.  When the GDB assumes the same name as the project it is by default way too long. I may not want a GDB named: CityOfWhatever_RoadIntersectionAnalysis_Phase3.gdb (Matching the APRX name), when I really just want it to be Data.gdb.   I think the original post was suggesting more options at the time of creation, not workarounds.  And I second that! Thanks! ... View more

Just wanted to add another comment to this thread.  I was having a similar problem with Select By Location.  After some unsuccessful efforts to resolve it (e.g. replacing the Normal file) I realized it was specific to one dataset I obtained from an outside source, specifically because that polygon data had negative values in the SHAPE_AREA field.  In my case it was easy to just create a new polygon dataset (using Trace), which provided me with a non-corrupt version.  Selection tools worked properly after that.  In reading another post elsewhere there was a good suggestion that using the Repair Geometry geoprocessing tool may also resolve the problem and be a better alternative for fixing a more complicated dataset since a manual Trace is not a great solution.  Just wanted to share that the data may be the cause, rather than a bug in the software. ... View more

Likewise, I'd love to have the ability to quickly label only selected features and also quickly generate a label class from selected features.  I would envision it looking/working something like the items shown in the included images.     ... View more

I've also had the exact same problem but seem to have found a means to work around it.  I'm using Explorer build 1500. In my current case the failing layers are layer packages (.lpk) built in ArcGIS 10.  I've also watched it happen last week in shapefiles and FGDB feature classes.  Only two out of several layer packages are experiencing this issue in my current Explorer project.  They work fine for a while panning and zooming, but it seems that once the cache for these particular layers gets to a certain size of around 2mb they start to fail in the map (I've been watching the file sizes in the default cache directory C:\Documents and Settings\...username...\Local Settings\Temp\E3). My work around is to change the 'Refresh Options' for the particular problem layers.  Go to Layer Properties, Source Data, and choose the radio button for "At a specific time interval".  It doesn't seem to matter what time interval you set. I tried "1 hour" and also "1 minute" and both worked immediately to solve the problem.  You need to save the your project for the setting to take effect permanently. As a side note...It seems like the refresh option for "When the map is opened or the layer is added" would similarly solve the problem but it does not.  That option apparently has a bug.  See this forum http://forums.arcgis.com/threads/15362-Help-me-understand-caches-and-refresh-options?highlight=explorer+cache -Rick ... View more

I'd like to see a reverse searching functionality in ArcCatalog that would work something like this: You right click a feature class, raster, etc. in ArcCatalog and choose something like 'Search Projects that use this item'.  You could enter the file location you want to search through (ie.  all of the C: drive, just C:\projects, etc.).  You could also choose which types of files to search through (ie. Map Documents [.mxd's], ArcGIS Explorer documents [.nmf's], etc).  Then a dialog box would tell you all of the projects that are referencing this item. If no projects were found to be referencing the item, then you could feel secure in renaming it, deleting it, etc. ... View more