Latest Contributions by LanceCole

Alex,  Does the tools work when you have just a single water main or a single fitting selected to be abandoned? ... View more

Allyson, The most recent version is available at Esri/local-government-desktop-addins ... View more

Paul, Thanks for the updated tools, they appear to be working. I did find one other sudo glitch. When you unabandon Water Hydrant Valves or Water System Valves they do not initially show. The “HYDRFLAG” comes back in as NULL and will not display because of the Definition Query on these two layers. I reset one layer to include “OR HYDRFLAG IS NULL” so it will at least display. ... View more

I received a phone call from ESRI Utilities Team regarding this question.  As Howard pointed out above there is not a one size fits all answer, however, the utilities team did have some excellent input.  The basis for separating the water data from the LGIM core is for future direction of utility networks.  With the proposed release of utility networks in the first quarter of 2018, there will be a need to eventually separate the data as the deployment continues to evolve over the next few years.  Our plan is to move our water, sewer and storm data onto a separate geodatabase and into geospatial networks.  This is the first major change to our LGDM schema in almost eight years and positions us to migrate to utility networks in the future once the new networks are well established.  ... View more

I just ran into this on the newest version (2/2017) as well, on both GBD and SDE enterprise databases.  After looking into the issue further found the python scripts AbandonFeatures.py and UnAbandonAssets.py were trying to modify the GlobalID fields which are not editable.  If your database is not utilizing Global id's the script works great.  To correct this three lines of code need to be modified to exclude modifying the GlobalID values.  In  AbandonFeatures.py lines 203 and 244 by appending code to exclude GlobalID. 202 for fieldName in fieldListLines: 203    if fldInfo.findFieldByName(fieldName) >= 0 and fieldName != "GlobalID": 204       arcpy.AddMessage("fieldName: " + fieldName) 205       newRow.setValue(fieldName, row.getValue(fieldName)) ... 243 for fieldName in fieldListPoints: 244    if fldInfo.findFieldByName(fieldName) >= 0 and fieldName != "GlobalID": 245       newRow.setValue(fieldName, row.getValue(fieldName)) ‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ And in line 205 of UnAbandonAssets.py the same. 204 for fieldName in fieldList: 205    if targetFldInfo.findFieldByName(fieldName) >= 0 and fieldName != "GlobalID": 206       newRow.setValue(fieldName, row.getValue(fieldName))‍‍‍‍‍‍‍‍‍ ... View more

George, Thanks for the quick reply.  The whitepaper "The Road Ahead for Network Management" is a great overview of what is forthcoming in network management. I am looking for information that goes a little deeper.  Currently we have a single SDE geodatabase that is roughly based upon a very early schema version of LGIM.  We are going to migrate this data over to the newest version of the LGIM as well as create networks for water, storm and sewer systems.  Should we continue to maintain this on a single SDE database, break the database into two or more databases such as - LGIM core data and a separate database(s) for networks, etc. Currently we are only utilizing the ArcGIS desktop environment with a single ArcGIS Server running an informational website but are planning on establishing an ArcGIS Portal and expanding into ArcGIS Pro using the numerous readily available resources.  ... View more

Kim, Yes, this use to work in previous versions of X-Ray.  I have not been able to get that far with the newest version.  There is an older video demonstrating making a modification to the XML via X-Ray the applying the modified schema to a blank GDB (link below).  To make changes to an existing GDB, I typically export out only the feature class I want to modify to the XML, make the changes using x-ray/excel then apply the revised schema to an existing database using the "Import Using Geoprocessing..." option under the X-Ray menu. X-Ray is a great tool for working with large or unfamiliar databases.  The new version has a few bugs and hopefully ESRI will quickly get a revision out. Video link: Introduction-to-X-Ray-for-ArcCatalog Lance ... View more

Yes, That error is received when I select "Import XML Workspace to Selected GDB"  Please note if you open the XML and directly click Import to the geodatabase there is not an issue.  However, if you open the XML, Press Save, and then click Import to the GDB you will receive the error.  Watching the XML, it changes from 11,592 KB to 7,845 KB when the saved button is clicked. ... View more

- What version of Windows are you using?       Windows 7 Professional, SP1 - Is the windows version a 32-bit or 64-bit machine?       64-bit - What version of Microsoft Office is installed?       Office Professional 2013 – 15.0.4885.1001 - Did you have any older version of x-ray on your machine?          Yes, but they were removed prior to installing the new add-on - Is the XML schema you are starting with Schema Only?       Yes, it is the LocalGovernment.xml directly downloaded from ESRI and dated 6/13/2016 Lance ... View more

Use ​'Bld%06d' %Bld_ID rather than 'Bld' + str(Bld_ID) ... View more

We place our mosaic image GDBs on a share and have the users copy the file to their local drive.  This provides multi user access and a slight performance gain.  One caveat is the users either have to use the same drive mapped to where the actual images are shared (ie the "I" drive) that the mosaic was created from.  Another option is to create the mosaic data set using a ​UNC network path and provide user read access.  The original images and overview files are stored on our systems SAN or NAS. ... View more

Have you tried x-ray for arcCatalog? http://www.arcgis.com/home/item.html?id=9ea218ff575f4a5195e01a2cae03a0ae ... View more