Latest Contributions by DeanAnderson2

‎04-05-2022

Been using 2.8 for a bit and have had no problem clearing definition queries with the following code. If TurnQueryOn is true it sets the definition query. If it is false it sets definition query to None. if TurnQueryOn: RecordWhereClause = "CreatedByRecord = " + "'" + RecordNumber + "'" for FilterLayer in FilterLayers: mapFilterLyr = Map.listLayers(FilterLayer)[0] if mapFilterLyr.isFeatureLayer: mapFilterLyr.definitionQuery = RecordWhereClause else: for FilterLayer in FilterLayers: mapFilterLyr = Map.listLayers(FilterLayer)[0] if mapFilterLyr.isFeatureLayer: mapFilterLyr.definitionQuery = None I just upgraded to 2.9 (I still have a machine 2.83 so was able to double check). But the definition queries are no longer being deleted but just turns them to "inactive". Is there something I am doing wrong? (I have seen other posts for this in the past and they appear to operate the same as mine does in 2.83.)

‎02-15-2022

Thanks Tim.

‎02-14-2022

Final Test - Created a new geodatabase, Created a new line feature class, ran Enable CoGo tool. Entered a four sided box (1000,1000,1000,999). Closed it. All looks good. Divided the north line (1000 foot) as follows: Exhibits same behavior as before. Second COGO line has no distance as follows: When I use the percentage option, or equal parts option in works fine (of course). I continue to be confused.

‎02-14-2022

Doing more checking. My COGO lines appear to be OK. When I do a line intersection and do not "Recalculate COGO Attributes" the tool calculates the cogo attributes correctly from the parent. In the following attribute list the intersecting line is non-cogo. It is intersecting with a COGO line that has a distance of 199 ft. The two distances total to 199 feet after the intersection (as a further test this was a closed line with a one foot error. It all operated as expected.

‎02-14-2022

First - thanks so much for help on the duplicate domain issue. That fixed the problem. On my second issue. I was concerned about the line so I created a NEW line with the traverse tool (just a simple 200 foot long straight line as illustrated above). Attribute for cogo enabled was "entered" so not sure what is going on. Glad it works as expected for you. At least that means I understand how it is supposed to work. Now just have to figure out what is wrong. I am not sure what a "true COGO-Enabled Line" is. I have replicated my problem using my converted taxlotline COGO data from ArcMap (non-fabric) and also from newly created lines. We have been testing and using other commands such as Traverse on this dataset for months and it has been operating correctly (as expected). I have also replicated my problem on a non-fabric COGO feature class that has had the "Enable COGO tool" run. I assume this makes a COGO line? So I think I am using COGO enabled lines. I there some setting I missed?

‎02-14-2022

Had not used that for domains before. That fixes the domain attribute. As to the CoGo Attributes I am not sure what is up. I just entered one line using traverse. (n44-00-00e 200 feet long) as below. I then use the divide tool and divided the line from start of line 100 feet and the results are: What I expect to have happen (and based on your response) would be two lines both with a length of 100. Instead my second line (while retaining the direction) has a NULL distance. Is this the correct behavior? I am not getting something.

‎02-14-2022

I am working with the Divide Line tool. My line feature class has several key attributes. When I divide the line (ie. 200 feet from beginning). The tool creates the two new lines correctly. The parent has the retired by record field assigned correctly making the parent line historic. So Far all is good. Unfortunately, I have a number of attributes (such as LineType) that are not replicated in the children while others (cogo attributes and a field called source) are. Is this the expected behavior ? (Also I am using 2.8.3). The documentation is pretty clear that it should keep the attributes. I am just not sure why my linetype is not kept (it has a domain) and why I lost my cogo distance on the remainder. Please let me know Thanks

‎12-17-2021

Thanks for letting me know! I was not able to find it anywhere.

‎12-16-2021

At this time, when a task is complete the contents (display, select set, edit set) are set as they were when the task was run. It would be great to have an option that would set the environment (display, select set, edit set) back to what existed before the task was started. 1. User environment exists 2. Task runs and contents sets the environment to be what is needed during the task 3. Based on an option the environment is reset to what is was before the task started (Step 1: User environment exists).

‎12-16-2021

Good thought, I tried that with a couple of test tasks for the cartographers. The problem is that they come at the "short cut" tasks from a number of different business processes so that there is not a specific contents set that will work. I thought if I created some tasks that represent "edit environments" that this would be more flexible and transparent. Also... I was thinking I would let users change & customize these environment setting tasks to fit their way of doing business. Whereas, I do not want them messing with "production tasks".

‎12-16-2021

That is too bad. This would be very helpful. As it is now I am creating a series of tasks that do nothing but set a particular edit environment (what's visible, selectable, and editable) which is not a great work around. Should I submit this need in the ideas section? ]

‎12-16-2021

We are starting to use tasks. We are using tasks as an aid to complete multi-step processes consistently and to provide "shortcuts" to get specific tasks done. Within tasks using contents to set was is visible, selectable, and editable is great! However, is there a way when the task is completed that what is visible, selectable, and editable will be returned to what they were before the task was started?

‎12-07-2021

At the suggestion of Amir, I am reposting this question here. In my parcel fabric design I have created additional feature classes that I want a field type to be "GUID" for a specific field (such as "created by record") and use these fields in my editing process. The fields function as all other fields do except when I go to use the "Set Default Attribute Tool". Unfortunately, the Set Default Attribute Tool appears to not allow this. Is there some reason why? The tools works as expected for all other field types. When using the "Assign Default to Field" interactively the field with a type of GUID does not appear (see below) and when I try to run the tool as a python script it errors. out. The work around I am using is to set the field type to be a Textfield but that is kind of annoying and its just not right.

‎12-04-2021

In my parcel fabric design I have created additional feature classes that I want a field type to be "GUID" for a specific field (such as "created by record") and use these fields in my editing process. The fields function as all other fields do except when I go to use the "Set Default Attribute Tool". Unfortunately, the Set Default Attribute Tool appears to not allow this. Is there some reason why? The tools works as expected for all other field types. When using the "Assign Default to Field" interactively the field with a type of GUID does not appear (see below) and when I try to run the tool as a python script it errors. out. The work around I am using is to set the field type to be a Textfield but that is kind of annoying and its just not right.

‎11-16-2021

Tried to use the attribute rules. Users will need to be able to assigned related feature with a plan but this does not happen All the time and unfortunately, with enterprise attribute rules can not be turned off an on (unless this recently changed). My current work around is to get the globalid from the current activerecord and use the arcpy.AssignDefaultToField_management tool to set the default value for each feature that is participating. Once it is turned on all features added after that time will have the global id updated. Once it is turned off this will not happen.

Online Status	Offline
Date Last Visited	‎08-29-2024 07:10 PM

My Ideas

Latest Contributions by DeanAnderson2

Delete definitionQuery different from 2.83 to 2.9

Re: It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

Re: It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

Re: It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

Re: It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

Re: It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

It appears that Divide Lines does not have a way to keep the parent line attributes. Is this correct?

Re: ArcGIS Pro Tasks and Returning to Starting Point

Have an option to reset the task contents upon completion of a task to what they were before the task started.

Re: Can you reset task contents so selection and edits are returned to what was set before you ran the task

Re: Can you reset task contents so selection and edits are returned to what was set before you ran the task

Can you reset task contents so selection and edits are returned to what was set before you ran the task

Assign Default Field with DataType GUID

Assign Default Field with DataType GUID

Re: Add ability to associate cartographic feature classes to record types in the fabric.

Re: Exporting a feature class with a related table...

Re: Exporting a feature class with a related table...

Exporting a feature class with a related table not...

Problem using scripts to calculate fields in ArcPr...

Re: Validation problem with checking domains compl...

Web AppBuilder Custom Widgets