Latest Contributions by AngelaDeegan

‎04-22-2021

Our current GIS deployment is not Z-enabled and we were thinking of applying Z values to our features as we migrate them to Utility Network. Can you advise us please on how to accomplish that? We’d love to hear what other users are doing in that regard. I’m guessing that shape_operations.py which is provided by ESRI - as one of two scripts in the migration package - could be leveraged to do this. But I searched and didn’t find any documentation on the intended use of this script. Also, note that our business process involves sometimes having Proposed status features coincident with To Be Abandoned status features of the same feature class. We have devised a draft plan to resolve this by ensuring they have different Z values. Our plan involves doing this initially in the process of migrating our features to UN.

‎04-09-2021

Table to Domain fails to import records from Excel that have integers in the code column when the destination domain has a code datatype of short integer. This is the case even when the integers are within the range of short integers (-32,768 to 32,767). We are working on migration to Utility Network. In doing so, we need to duplicate some of our existing domains in UN. However we need many of them to have data type "short" in UN - instead of data type "text" which they currently have. To do this we have tried the following: Create the new domain in WaterDistribution_AssetPackage_Change.gdb - making sure to classify the code attribute as data type short integer. Create a copy of the existing domain in Excel using Domain to Table making sure all the codes are integers that qualify as short integers. (Note that this Excel spreadsheet does double-duty because we can also paste its contents into the relevant domain sheet in the DataMapping spreadsheet for mapping the old text codes to the new integer codes. These DataMapping spreadsheets have names such as Main-WaterLine_Water Main.xlsx) Run Table to Domain to import the code and description from the Excel Spreadsheet into the new domain. Step 3 fails with Error 000307 The input field type does not match the field type of the existing domain. In the attachment, you can see that after the tool failed, I verified that the codes were true numbers (see cell D2 in the Excel file). I had also previous tested manually entering one of the codes and its corresponding description into the new domain and that was successful. I had submitted this as a bug (#02779308) and was informed that the error is due to the values in Excel being classifed as data type double, not short and that it would require a work-around involved multiple additional steps to get this to work. Rather than have to use the work-around, this idea is that the Table to Domain tool gets enhanced so that it attempts to coerce input codes to the datatype of the domain code. With this enhancement, I would expect an input code of datatype double should successfully migrate to a domain code datatype of short integer, provided that the input codes are in the form of whole numbers that are within the range -32,768 to 32,767.

‎01-26-2021

@JohnAlsup For fields that are re-used, and which therefore have multiple aliases, is the order in which the aliases are listed inconsequential?

‎01-26-2021

@JohnAlsup I would think that field re-use would make scripting (and potentially even tasks using the GUI) very challenging. I say that because we wouldn't be able to rely on the generic internal field name to know what the data in that field represents. Is that a valid concern?

‎01-14-2021

At my workplace, we use replication for creating test environments. We have many attribute rules. I just realized today that the attribute rules don't get replicated. It's very disappointing as it means we can't be confident that results in our production database will mirror results of testing in our test database. Please add replication of attribute rules.

‎12-29-2020

I'm not clear why you're buffering the parcel. And by using a negative number I think you may be "shrinking" the parcel by that footage. That could cause a problem if a parcel is less than 25 feet wide in places. Also, looking at the documentation, it appears that the arguments for Intersection must be either a geometry or feature. It doesn't appear to allow a featureset as an argument. You are passing in 'gensoils' (a featureset) as an argument. I'm guessing you'd need to run Intersection on any geometry in gensoils recursively.

‎12-29-2020

I think you may need to use the https://developers.arcgis.com/arcade/function-reference/geometry_functions/#intersection function in addition to the https://developers.arcgis.com/arcade/function-reference/geometry_functions/#intersects function. I can't see the layers you're working with, but unless they have coincident boundaries, seems like you'd need to "cut" the soils layer using the parcels layer and looks like the intersection function would do that for you. Also, you might want to use the https://developers.arcgis.com/arcade/function-reference/geometry_functions/#area function on the $feature to set the sum_area. Seems like that would be more straightforward.

‎12-03-2020

I'm afraid I didn't. Ended up doing it manually. It was a pain. And when I deleted the empty feature datasets, the layers corresponding to feature classes that had been in those feature datasets stopped displaying in the web map that had been published. So we had to re-publish the services. Hope that helps. This was a couple of months back, so it's getting fuzzy already!

‎10-29-2020

Do you know if anyone has submitted a support ticket regarding this issue? It looks like that's what it's going to take to get it addressed.

‎10-08-2020

I'm finding this really frustrating too. I regularly get the "Indexing is in Progress" message when I search the Catalog Pane. Recently I needed to do a search for Feature Class source paths that needed to be updated - due to the Feature Classes having been moved out of the Feature Dataset that they used to be in. It doesn't work because, no matter how long I wait, I get the "Indexing is in Progress. Please wait or search again later." This is despite the fact that I have indexing set up to index every hour and to re-index once a day.

‎09-16-2020

I just now emailed it to you, Drew.

‎09-16-2020

I was able to export a feature class to file geodatabase. When should I upload it for you?

‎09-16-2020

The feature classes we've tried this with are in our enterprise geodatabase (on Postgres 10.12 on Linux). My colleague confirmed he's having the issue too. Our feature classes do have attributes rules on them, by the way, so I'm not sure if that's a factor. How should I share the data with you? I guess I'd need to export them to file geodatabase?

‎09-15-2020

I'm having a problem with Table to Table in Pro 2.6 also. It's only working for tables - not for Feature Classes, even though Table to Table is the tool that's automatically used when you choose to Export a feature class. I went to Pro 2.6.1 thinking that might solve the problem but it didn't. I don't have an expression defined in my Table to Table run, but I keep getting 'Error 160912: Failed to evaluate Arcade expression'. I guess I'll try re-installing to see if that fixes this issue.

‎09-03-2020

Thank you very much for checking into this and letting me know your findings. I'm currently looking to see if there's a programmatic way to do this by leveraging getDefinition on Layer. So far I have only been able to display the feature dataset for layers in a map, but not change it. I think really what I need to be able to do is remove the featureDataset attribute for the layer. def updateFDstToRoot(prj, mp): ##Script to display any FCs that still indicate they are in the 'gis.sde.WaterDistributionRelated' feature dataset - though all feature classes were moved (dragged/dropped) from it to 'root; import arcpy, sys aprx = arcpy.mp.ArcGISProject(r'C:\Users\angela\Documents\ArcGIS\Projects\DEVwork\{}.aprx'.format(prj)) #Get list of all the maps in the project mps = aprx.listMaps() print(r"There are {} maps in project {}".format(len(mps), prj)) #print(mps) mnames = [] for m in mps: mnames.append(m.name) print(len(mnames)) #Get the index of the map we want to work on map_pos = mnames.index(mp) print(r'{} is in position {}'.format(mp, map_pos)) #Get a handle on the map m = mps[map_pos] print(m.name) lyrs = m.listLayers() print(len(lyrs)) for l in lyrs: lCIM = l.getDefinition('V2') try: dc = lCIM.featureTable.dataConnection except Exception as Ex: print('******Failed: {}\nLine: {}\n'.format(Ex, sys.exc_info()[-1].tb_lineno)) else: if hasattr(dc, 'featureDataset'): if dc.featureDataset == 'gis.sde.WaterDistributionRelated': print("**** {} needs updating".format(l.name)) else: print("{} DOES NOT NEED updating".format(l.name)) #aprx.save() del aprx updateFDstToRoot('DEVwork', r'EngineeringViewer-DevDB')

Online Status	Offline
Date Last Visited	‎05-05-2021 12:49 PM

My Ideas

Latest Contributions by AngelaDeegan

What's the best practise for assigning Z values when migrating to Utility Network?

Enhance Table To Domain tool to coerce datatype of incoming code to datatype of the Domain Code

Re: Best Practices for Attribute Data Modeling in UN

Re: Best Practices for Attribute Data Modeling in UN

Re: Support Geodatabase Replication with the Attribute Rules

Re: Using Arcade to calculate percent coverage

Re: Using Arcade to calculate percent coverage

Re: Move feature classes out of feature dataset

Re: Indexing in an ArcPro Project

Re: Indexing in an ArcPro Project

Re: ArcGIS Pro 2.6 - Table to Table tool issue

Re: ArcGIS Pro 2.6 - Table to Table tool issue

Re: ArcGIS Pro 2.6 - Table to Table tool issue

Re: ArcGIS Pro 2.6 - Table to Table tool issue

Re: Move feature classes out of feature dataset

Re: Indexing in an ArcPro Project

Re: Indexing in an ArcPro Project

What's the best practise for assigning Z values wh...

Enhance Table To Domain tool to coerce datatype of...

Re: Using Arcade to calculate percent coverage