Latest Contributions by AZendel

‎12-19-2023

This strikes me as pretty crazy as well. I think the functionality should allow you to create the feature, then set the attributes (including the required domain(s)), then save edits. If the attributes don't meet the validation rules, then Pro should refuse saving the edit until the needed value is supplied. You can't change the attributes before the feature is created! If you have multiple domains on multiple fields, then your editing template would have to be very long to accommodate every possible option. Maybe I'm missing something or misunderstanding the problem, but pigeonholing us into this situation doesn't make sense. In my case, the feature class is stored in SDE (Enterprise Geodatabase) and has map services pointed at it. So I can't change the schema to allow nulls or set a default value without disabling the map service. The link to the help file that @CarsonG suggested did allow me to disable the validation. I wish that this setting was available at the project level (allow this on some Pro projects, not the others) or at the feature class level within a project. This validation could be helpful on feature classes with only one domain.

‎09-22-2023

Thanks for all of the follow ups!

‎09-21-2023

Thanks for the reply, Scott. My steps are 1) click the Edges "tab" on the reshape edge tool 2) activate the "select one or more edges" tool 3) select the edge 4) click the "Reshape" button 5) start my cut/sketch. If I zoom in or out, I lose the sketch about 85% of the time. Sometimes it doesn't happen. My co-worker is experiencing the same while we are simultaneously editing the same versioned feature class that hosted on Oracle enterprise geodatabase. Did you run your tests against an Enterprise GDB? Specifically Oracle?

‎09-18-2023

Also, I sometimes run into the 'reshape failed' message after I've completed my sketch when using the Reshape Topology Edge tool - while editing a Topology. I typically understand why the sketch failed in most circumstances. But it would be nice to have the option to continue the sketch to fix the failed edit - a lot like how the 'split polygon' tool works. When a split fails, Pro asks the user if they want to continue or discard their sketch. The reshape tool should do this too.

‎09-18-2023

It looks like this has been implemented in Pro 3.x when using the cut tool. Thank you, ESRI. But it seems like this has NOT been implemented when using the reshape tool. Please add that, ESRI!

‎09-18-2023

Yes please. Maybe allow the user to specify the transparency as well.

‎05-23-2023

Yes, please! It sounds like this hasn't been implemented yet? Somebody tell me that I'm wrong. Has anyone built a custom widget that they can share?

‎04-03-2023

I'm seeing this on an Oracle EGDB as well. I'm still using Pro 3.0.3, but 3.1.0 is available. But based on the bug report, I don't think this this has been fixed. @Robert_LeClair, it may not hurt to let the staff that are addressing the bug know that I've run into the issue on an Oracle SDE instance as well. It's happening on the SHAPE.Area field and a separate double precision field that has nothing to do with the geometry. I'm glad that the statistics that it was reporting were so out of the park that something was blatantly wrong. Otherwise, I could have reported some bad numbers and that should never be considered acceptable. I think this bug warrants faster action than it appears to have received so far.

‎03-21-2023

Thanks for the excellent explanation, Shannon. And for confirming that the SQL Server documentation that I quoted applies to Oracle and the other Enterprise GDBs (though I imagine each DBMS may have some of its own particular details/idiosyncrasies regarding area and length calculations). I can stop scratching my head now...... Thanks again. While we're on the topic of SHAPE.AREA, it be really nice to be able to specify the units that are displayed in these fields. As you saw above, I almost exclusively use TN State Plan HARN NAD83. The X/Y units are in feet so the SHAPE.AREA fields display square feet. Square feet is a easy to digest when you're at the building or lot level, but once you get up into dozens of acres, it's almost meaningless, like 4,535,588.22548 sq ft. I'd much rather see acres in feature classes with larger polygons. You mentioned attribute rules, but it sounds like you'd need to create a new field to store the calculate area? That could get inefficient on larger datasets. I also realize that Query Layers allow you to specify SQL that can handle this conversion, but then you can't edit the FC. It'd also be nice to have dynamic field that makes calculations beyond geometry (summing several columns of different races reported in census data). QGIS has 'virtual fields' that do just that.

‎03-17-2023

After coming across this post, I think the discrepancy comes down to how Oracle and ArcGIS are handling curves when calculating area. That post is for SQL Server, but I imagine that something similar is happening with Oracle.

‎03-17-2023

Thanks for the quick response. I believe I ran across that page in the documentation, but it's hard to remember all that I read before I decided to post here. That page starts with "The Esri ST_Geometry spatial data type.....", which implies that ESRI created it. That makes me think that ST_Geometry is used in File GDB's, but I could not confirm that after extensive web searches . Good suggestion on looking for curves in the source geometry. There are some (below). But shouldn't those transfer from Oracle to FGDB the same?

‎03-17-2023

I exported some simple polygons stored in the ST_Geometry format from an Enterprise Oracle database to File GDB (FGDB) and the shape_area field for one polygon lost 76 sqft. That 'loss' is based on the Shape.Area field in Oracle and the SHAPE_Area field in the FGDB. This happens when I use the Copy Features tool in a geoprocessing model and using Data --> Export Features in Pro. I've looked at the feature class properties of both and they have the exact same: Coordinate system: SRID 2915 (TN State Plane NAD83 HARN). The "Geographic Coordinate System" that the layer properties dialog box that Pro displays lists the same WKID: 4152 Spatial resolution: 0.000328083333333333 US Survey Feet No Z value storage, no M Value storage Simple Feature type Vertical units (Foot_US) -- this is probably moot since neither store Z values No Errors or Warnings are shown in the geoprocessing history for the copy features More notes/questions Does the FGDB use also ST_Geometry? Or something slightly different? If the latter, I suppose this could account for the difference I ran the Check Geometry tool on the FGDB feature class and none were reported. It is not possible to run the tool on Oracle feature classes because, as the tool document states, the geometry is reportedly validate when inserted Does the shape_area or Shape.Area sometimes fail to update? This discrepancy was only detected in 2 of 190 exported polygons (one discrepancy was ~76 sqft, the other 18 sqft) This is fairly concerning because we often list polygon areas on documents that have legal ramifications The calculate geometry tool doesn't match the SHAPE_Area field of the output FGDB feature class, which is shown below (calculated area with us survey feet as the input). The Shape.Area field of the Oracle feature is 651063.678772 Thanks in advance for any insight you can provide.

‎03-02-2023

Yes, please! I would love to be able to specify 'overwrite outputs' at the individual model level. Can this be added to a model's 'environment' settings? I also execute a number of geoprocessing models via ArcPy stand alone scripts. So the setting in the Pro interface as shown here is not effective in these situations because the scripts are executed 100% outside of the Pro environment.

‎03-02-2023

If I'm interpreting these posts correctly, there is no way to specify that a particular/individual geoprocessing model should overwrite its outputs. The only option is to set this in the Pro options tab as shown in the first post. Is this still the case? I'm calling a lot of geoprocessing models from ArcPy and I want to allow some of the models to overwrite existing outputs. This setting in the Pro user interface is likely ignored when running a completely standalone ArcPy script. Please confirm when you can. And ESRI, if you're reading this, please allow this option to be set within individual models.

‎01-05-2023

Is this still the case with ArcGIS Pro 3.0? I have a stand alone vb.net exe that executes geoprocessing models using libraries/assemblies from ArcMap 10.8.1. Windows Task Scheduler wakes it up every hour and it also performs a lot of SQL tasks via native SQL Server client libraries. It also calls a geoprocessing model that geocode addresses and later calls another geoprocessing model that appends those features to a feature class. Since ArcMap will not exist in the future, I'm trying to migrate it to rely on libraries from Pro. Here's the VB.net / ArcObjects code: Dim parameters As ESRI.ArcGIS.esriSystem.IVariantArray = New ESRI.ArcGIS.esriSystem.VarArray Dim GP As esri.ArcGIS.Geoprocessing.IGeoProcessor2 = New esri.arcgis.Geoprocessing.Geoprocessor() 'Add the BestPath toolbox. GP.AddToolbox("C:\path\to\my\toolbox.tbx") parameters.Add(sGDBPath & "\databasename.DBO.myfeatureclass") 'Execute the model tool by name. GP.Execute("DeleteCountyStatusPermits", parameters, Nothing) There's no way to do this on machines that have Pro and not ArcMap? It would be nice to not have to 'wrap' these models in python scripts - that adds too much complexity to maintaining my project. Thanks for your time, Alex

Online Status	Offline
Date Last Visited	Friday

My Ideas

Latest Contributions by AZendel

Re: I cant create features due to :Value doesn't fall within Domain : XName

Re: Allow users to continue sketch when reshape fails while using the Reshape Topology Edge tool.

Re: When using the reshape tool: 1) allow users to zoom, 2) allow users to continue sketch when the reshape fails

Allow users to continue sketch when reshape fails while using the Reshape Topology Edge tool.

Re: Save sketch after a failed "Reshape Feature" or "Cut Polygon" operation.

Re: Reduce topology selection width when using Reshape

Re: Add Location Tracking Widget to Experience Builder Map Container

Re: ArcPro not honoring selection for attribute statistics

Re: Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB?

Re: Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB?

Re: Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB?

Why did a polygon lose 76 sqft (Shape.Area) when exporting from Oracle ST_Geometery to File GDB?

Re: ArcGIS Pro 2.5: An option to overwrite the outputs of the model builder,

Re: ArcGIS Pro 2.5: How to overwrite outputs of geoprocessing tools when run in a model builder?

Re: ArcGIS.Desktop.Core.Geoprocessing in standalone ArcGIS Pro SDK app

Re: Editing Geodatabase Annotation in layout mode?...

Re: I cant create features due to :Value doesn't ...

Re: Size of a feature class

Allow users to continue sketch when reshape fails ...

Re: ArcPro not honoring selection for attribute st...